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

[Asterisk Bug Tracker]

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:                        
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-11-09 15:15 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0113459) lmadsen (administrator) - 2009-11-09 15:15
 https://issues.asterisk.org/view.php?id=16179#c113459 
---------------------------------------------------------------------- 
No, as 1.4.26.2 is a security release only, as is clearly stated in the
release announcement, and by reviewing the ChangeLog.

Bug fixes are currently being evaluated in a release candidate as
1.4.27-rc2, released today. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-09 15:15 lmadsen        Note Added: 0113459                          
======================================================================