[asterisk-bugs] [JIRA] (ASTERISK-21737) [patch] - Crash during transfer from DAHDI/SIP to SIP/SIP in ast_format_cap_append called from remote bridge loop

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-21737:
----------------------------------------

Wow. There's a number of interesting things going on here.
* The two SIP channels are entering into a remote bridge loop and this blows out while we're looking at the glue callbacks to determine if they're compatible
* Somehow, the following line resulted in a NULL pointer:
{noformat}
ast_format_cap_append(result, ast_format_cap_is_empty(p->peercaps) ? p->caps : p->peercaps);
{noformat}
The freaky part there is that the SIP pvt is always supposed to have something in its {{caps}} pointer - if we don't allocate something in it, we fail creation of the {{sip_pvt}}. I'm not sure how that ended up with NULL.
                
> [patch] - Crash during transfer from DAHDI/SIP to SIP/SIP in ast_format_cap_append called from remote bridge loop
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21737
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21737
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Transfers, Core/Bridging
>         Environment: Asterisk SVN-branch-11-r385594 
>            Reporter: Alec Davis
>         Attachments: bug_apr30.diff.txt, gdb-apr30.txt
>
>
> DAHDI call into queue.
> SIP agent answers, then transfer to SIP0007.
>  
> Crashed just after/during a transfer.

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