[asterisk-bugs] [JIRA] (ASTERISK-22532) Fix chan_pjsip two party alice initiated test failures

[Mark Michelson (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210383#comment-210383 ] 

Mark Michelson commented on ASTERISK-22532:
-------------------------------------------

Looking at the logs from build 86, the two-party tests are failing due to a TCP binding issue. The "bob" instance of Asterisk is unable to bind to TCP port 5062.

Prior to the two-party tests, the following three SIP tests run:

channels/SIP/sip_attended_transfer
channels/pjsip/basic_calls/outgoing/nominal/echo
channels/pjsip/basic_calls/outgoing/off-nominal/bob_does_not_answer

sip_attended_transfer does not use TCP at all.
echo binds an instance of Asterisk to port 5062.
bob_does_not_answer attempts to bind a SIPp instance to TCP port 5062. I cannot tell from the test logs whether this binding succeeds. However, I can tell that the attempted calls from Asterisk to TCP port 5062 result in ECONNREFUSED, leading to the test failures seen in that test.

The best I can deduce at the moment is that either the echo or the bob_does_not_answer test are leaving TCP port 5062 occupied. As a result, future tests, such as the two-party alice-initiated tests, are essentially non-starters since they cannot bind to the required port.

If I could see the SIPp output in more detail from the bob_does_not_answer test, I could narrow down the offender in this case. My guess, since SIPp is exiting with error code 97 (meaning a failure on an internal operation), the echo test is the culprit here. Fixing the echo test may result in other tests passing properly.

I'll have a look at other test runs to see if the results are consistent with build 86.
                
> Fix chan_pjsip two party alice initiated test failures
> ------------------------------------------------------
>
>                 Key: ASTERISK-22532
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22532
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Tests/testsuite
>    Affects Versions: 12.0.0-alpha1
>            Reporter: Matt Jordan
>            Assignee: Mark Michelson
>
> Well, this is a bit odd:
> * [https://bamboo.asterisk.org/bamboo/browse/AST-ATTSCD-C632TE-81/test/case/1415281]
> * [https://bamboo.asterisk.org/bamboo/browse/AST-ATTSCD-C632TE-81/test/case/1415282]
> The fact that the hangup cause mappings themselves are wrong indicates that this is more than just a TCP binding issue (or something along those lines)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira