[asterisk-bugs] [JIRA] (ASTERISK-21047) asterisk crashes during an attended transfer SIP -> SIP -> DAHDI

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-21047:
-----------------------------------------

So it sounds like following the compilation changes for reference count debugging results in you being unable to load chan_sip. I'm not sure why that is happening.

Have you tried re-extracting Asterisk from a fresh tarball before attempting the refrence count debugging customizations and compilation ?

Hopefully someone will be able to investigate without the reference count debug if you can't set it up.
                
> asterisk crashes during an attended transfer SIP -> SIP -> DAHDI
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-21047
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21047
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi, Channels/chan_sip/Transfers, Resources/res_rtp_asterisk
>    Affects Versions: 11.2.0, 11.2.1
>         Environment: debian 5.0.10, opensips v.1.8.2, digium te420B, PBX Aastra MD110
>            Reporter: piero ferraresso
>            Assignee: Rusty Newton
>            Severity: Critical
>         Attachments: backtrace.txt, chan_dahdi.conf, messages-sip-debug-on.txt, messages.txt, sip.conf
>
>
> I'm trying to make an attended transfer.
> Sip hardphone A call sip hardphone B (both Polycom SPIP 450);
> B press the 'transfer' softkey and compose the number of legacy hardphone C (PBX Aastra connected to asterisk with a Qsig trunk using a digium te420B card).
> After legacy hardphone C answered,  B press again the 'transfer' softkey to transfer the call to phone A. At this point asterisk crashes.
> Ps The some scenario using asterisk 1.4 works

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