[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=210388#comment-210388 ] 

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

I looked at build 85. The results are similar, yet different.

Again, the two party tests are failing due to "bob" being unable to bind to TCP port 5062. However, the prior conditions are slightly different. The following SIP tests fail prior to the two-party tests:

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

What's interesting here is that the echo test still fails, but this time the bob_does_not_answer test succeeds. This would imply that the echo test failure is not what is causing the port to remain occupied. It's worth noting, though, that in this particular test run, it's plain as day that the bob_does_not_exist test fails because SIPp is unable to bind to a specific port (the error output does not say which port the trouble occurred on).

This, unfortunately, adds a bit of randomness to the mix.

In build 86, if bob_does_not_answer could not bind to TCP port 5062, then we should have seen a SIPp error stating so in the logs, as evidenced by the logs for bob_does_not_exist in build 85. However, such a log message is not there, so it may be reasonable to assume that the test failed for a different reason entirely. Unfortunately, it is not clear from log output why it would be.

In build 85, the bob_does_not_exist test clearly fails due to the inability to bind to a port. However, the bob_does_not_answer test succeeded, and did so *after* the bob_does_not_exist test ran.

The only way to resolve this is to dig a bit deeper. The only constant so far is that the two-party tests are always failing for the same reason. The lead-up to those test failures varies, though.
                
> 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