Unexpected Termination Of The Call When Pick Up (res_pjsip)

Home » Asterisk Users » Unexpected Termination Of The Call When Pick Up (res_pjsip)
Asterisk Users 5 Comments

Please help find the cause of strange behavior res_pjsip.

Making outgoint call to other sip server (CommuniGatePro), my asterisk suddenly sends BYE after picking up!
Partial log of an outgoing call with full debug is attached and on web:
http://pastebin.com/tLNCpx4d

No diagnostic messages why asterisk suddenly decided to hangup i don’t found 🙁

There are suggestions or strong belief about the reasons of such behavior?

Thanks.

Dmitriy.

5 thoughts on - Unexpected Termination Of The Call When Pick Up (res_pjsip)

  • How are you initiating the call out to that server? Are you dialing from an internal phone or doing it from the CLI? It looks like it is from an internal extension, if I were guessing, but that side of the call isn’t in your log.

    If it is from an internal extension, I think a SIP trace on that side would help.

  • The call initiated from internal extension.

    I have made two test call:
    Successful call from device on res_pjsip via endpoint on chan_sip:
    http://pastebin.com/LWeDYstj Unsuccessful call from device on res_pjsip via endpoint on res_pjsip:
    http://pastebin.com/hepVb6Nu

    And ones again i don’t see anything that would make asterisk send BYE.

    I would be grateful for any ideas.

    11.02.2016 1:47, Trey Hilyard пишет:

  • I am stumped so far. What is most interesting to me is that Asterisk is actually sending two BYE transactions for the same dialog, at basically the same time. I am still going through your traces again, but maybe someone else has suggestions on how to add more debug to the res_pjsip logging that would prove useful.

  • Dmitriy Serov wrote:

    Kia ora,

    I have a feeling it may be an off-nominal SDP negotiation issue, causing two paths to get triggered which both send a BYE. I’d suggest filing an issue[1] with the traces you’ve provided. We can potentially use them to construct a sipp scenario that reproduces the issue. The configuration would also be needed.

    You can also try to narrow it down slightly by disabling the video codecs and seeing if that changes things. If it does then it’s with video involved.

    [1] https://issues.asterisk.org/jira