[asterisk-bugs] [JIRA] (ASTERISK-22061) crash - Dialing chan_gulp/pjsip with explicit SIP URI results in segfault in ast_sip_session_send_request_with_cb at res_sip_session.c

[Mark Michelson (JIRA)]

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

Mark Michelson commented on ASTERISK-22061:
-------------------------------------------

The reason for the crash is pretty clear. Looks like we're calling ast_sip_session_send_request() with a NULL pointer (i.e. no actual request). The simple reason for why that's happening is that the call to create the request is failing and we aren't checking for failure. What's more important is why the call to create the request is failing. I believe the code you're hitting was put there with reinvites in mind rather than the initial INVITE. I believe that if I were to add an additional check to make sure that we aren't dealing with the initial INVITE, then things will work as expected. I'll prepare a patch!
                
> crash - Dialing chan_gulp/pjsip with explicit SIP URI results in segfault in ast_sip_session_send_request_with_cb at res_sip_session.c
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22061
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22061
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_sip
>    Affects Versions: SVN
>         Environment: SVN-trunk-r393816
>            Reporter: Rusty Newton
>         Attachments: backtrace.txt, full.txt, res_sip.txt
>
>
> Dialing from trunk/res_sip to 1.8/chan_sip
> Dialing like:
> {noformat}
> exten => _9NXXNXXXXXX,1,Dial(GULP/rustytel/sip:${EXTEN:1}@10.24.18.124:5060)
> {noformat}
> Results in the attached trace and debug.

--
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