[asterisk-bugs] [Asterisk 0016179]: Asterisk Crash after SIP Transfer

Fri Dec 4 00:05:35 CST 2009

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16179 
====================================================================== 
Reported By:                xinyer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16179
Category:                   Channels/chan_sip/Transfers
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26.2 
JIRA:                       SWP-383 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-04 02:31 CST
Last Modified:              2009-12-04 00:05 CST
====================================================================== 
Summary:                    Asterisk Crash after SIP Transfer
Description: 
Asterisk crashes without any error, the last two lines of log before crash
are: 
VERBOSE[2998] logger.c:     -- SIP/8083-08e16f60 is ringing
DEBUG[1891] chan_sip.c: SIP transfer: Succeeded to masquerade channels.

Similar error was reported in the following thread:
https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=13256#93893

but it is closed. This happened to me twice today, but it works fine for
the last one week. I couldn't reproduce the crash.
====================================================================== 

---------------------------------------------------------------------- 
 (0114712) xinyer (reporter) - 2009-12-04 00:05
 https://issues.asterisk.org/view.php?id=16179#c114712 
---------------------------------------------------------------------- 
I'm sorry, I couldn't reproduce the crash. There was about 70 users when
the problem happened, but now the server is taken to the lab, just not able
to trigger the error anymore. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-04 00:05 xinyer         Note Added: 0114712                          
======================================================================