[asterisk-bugs] [Asterisk 0017993]: Asterisk crash when bridging and masquerading channels

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17993 
====================================================================== 
Reported By:                andrel
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17993
Category:                   Core/Channels
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.12-rc1 
JIRA:                       SWP-2243 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-14 17:12 CDT
Last Modified:              2011-03-30 11:36 CDT
====================================================================== 
Summary:                    Asterisk crash when bridging and masquerading
channels
Description: 
Asterisk Seems to crash when trying to bridge and masquerade the channel
sometimes
check full debug log for information(end of lines shows errors) and
backtrace via gdb.
====================================================================== 

---------------------------------------------------------------------- 
 (0133178) nmower (reporter) - 2011-03-30 11:36
 https://issues.asterisk.org/view.php?id=17993#c133178 
---------------------------------------------------------------------- 
We have upgraded to Asterisk 1.6.2.17.2, and the issue appears to be
resolved for us.  We left the source code unmodified -- none of our former
patches were applied to it.

I believe the ATXFER_NULL_TECH change on 20-Jan-2011 was the solution to
our particular problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-30 11:36 nmower         Note Added: 0133178                          
======================================================================