[asterisk-bugs] [Asterisk 0017301]: [patch] [regression] asterisk 1.4.31 crashes (segmentation fault) on sip to sip call via iax2 trunk

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=17301 
====================================================================== 
Reported By:                vieri
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   17301
Category:                   Channels/chan_iax2
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.31 
JIRA:                       SWP-1422 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-05-06 13:05 CDT
Last Modified:              2010-05-20 09:47 CDT
====================================================================== 
Summary:                    [patch] [regression] asterisk 1.4.31 crashes
(segmentation fault) on sip to sip call via iax2 trunk
Description: 
Attaching 2 core dump traces when Asterisk 1.4.31 crashed while calling
from sip extension to sip provider via a LAN IAX2 trunk between 2 asterisk
servers.

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

---------------------------------------------------------------------- 
 (0122209) dvossel (administrator) - 2010-05-20 09:47
 https://issues.asterisk.org/view.php?id=17301#c122209 
---------------------------------------------------------------------- 
Based on the backtraces, this issue does not look possible without some
sort of memory corruption, and it is impossible to know how that occurred
with the current information.

Given the information provided, this issue can not be moved further.  If
it occurs again and you are able to provide some new information (valgrind
report) please re-open this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-20 09:47 dvossel        Note Added: 0122209                          
2010-05-20 09:47 dvossel        Status                   assigned => closed  
======================================================================