[asterisk-bugs] [Asterisk 0013956]: Asterisk crashes when transfering call multiple times.

Asterisk Bug Tracker noreply at bugs.digium.com
Sun Dec 7 14:12:44 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13956 
====================================================================== 
Reported By:                chris-mac
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   13956
Category:                   Channels/chan_sip/Transfers
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 158757 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-23 15:58 CST
Last Modified:              2008-12-07 14:12 CST
====================================================================== 
Summary:                    Asterisk crashes when transfering call multiple
times.
Description: 
My scenarios is as follows:
1. A makes calls B.
2. A transfers B to C.
3. C transfers B to A.
4. A transfers B to C.
5. C transfers B to D.
6. asterisk crashes :-(

Number of transfers before asterisk crashes vary. But in general is always
more than 4-5. Managed to capture two console outputs and respective core
dumps.

transfer1.txt:
Packet2Packet bridging SIP/Voicetrading-Std-08234bb0 and
SIP/78.105.1.128:5060-084dff20
[Nov 23 21:28:33] WARNING[12008]: rtp.c:4251 ast_rtp_bridge: Got hangup
while attempting to bridge 'SIP/dev-sip.tele500.com-084cf6c0<ZOMBIE>' and
'SIP/78.105.1.128:5060-08235450'
    -- Native bridging SIP/dev-sip.tele500.com-084cf6c0<ZOMBIE> and
SIP/78.105.1.128:5060-08235450 ended
Segmentation fault (core dumped)

transfer2.txt:
chan_sip.c:19423 handle_request_do: We could NOT get the channel lock for
SIP/78.105.1.128:5060-084cf788! 
chan_sip.c:19424 handle_request_do: SIP transaction failed:
60920c9d029a6434482566b46c8ce5ae at 78.105.1.129 
chan_sip.c:19423 handle_request_do: We could NOT get the channel lock for
SIP/78.105.1.128:5060-084cf788! 
chan_sip.c:19424 handle_request_do: SIP transaction failed:
60920c9d029a6434482566b46c8ce5ae at 78.105.1.129 
chan_sip.c:19423 handle_request_do: We could NOT get the channel lock for
SIP/78.105.1.128:5060-084cd820! 
chan_sip.c:19424 handle_request_do: SIP transaction failed:
585383936f1a5d260cc52e1b0895ac3a at 78.105.1.129 
chan_sip.c:19423 handle_request_do: We could NOT get the channel lock for
SIP/78.105.1.128:5060-084cd820! 
chan_sip.c:19424 handle_request_do: SIP transaction failed:
585383936f1a5d260cc52e1b0895ac3a at 78.105.1.129 
Segmentation fault (core dumped)

Regards,
Chris

====================================================================== 

---------------------------------------------------------------------- 
 (0095938) chris-mac (reporter) - 2008-12-07 14:12
 http://bugs.digium.com/view.php?id=13956#c95938 
---------------------------------------------------------------------- 
I haven't noticed other problems or strange console output.

I can still see:
[Dec  7 19:44:03] ERROR[5555]: chan_sip.c:19423 handle_request_do: We
could NOT get the channel lock for SIP/Trunk-Std-092efc98! 
[Dec  7 19:44:03] ERROR[5555]: chan_sip.c:19424 handle_request_do: SIP
transaction failed: 5c0b411d6b6613730d428ce5054fcc02 at 78.105.1.129 

from time to time, but not when transferring calls, so this is probably
not related to bug13956-1.diff patch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-07 14:12 chris-mac      Note Added: 0095938                          
======================================================================




More information about the asterisk-bugs mailing list