[asterisk-bugs] [Asterisk 0013050]: Memory segmentation fault on T.38 pass through

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13050 
====================================================================== 
Reported By:                schern
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13050
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.24
Asterisk Version:           1.4.21 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-07-10 08:17 CDT
Last Modified:              2009-02-10 13:27 CST
====================================================================== 
Summary:                    Memory segmentation fault on T.38 pass through
Description: 
I tried to use the chan_sip with T.38 pass through. An Fax is coming via
T.38 from
the Carrier an should go to a Linksys SPA2102 (T.38 enabled).
Short after starting UDPL traffic I got a segmentation fault.
The crash is 100% reproducible.
Outbound T.38 is no problem at all.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013600 [patch] Crash in decode_length - udptl....
====================================================================== 

---------------------------------------------------------------------- 
 (0099830) Corydon76 (administrator) - 2009-02-10 13:27
 http://bugs.digium.com/view.php?id=13050#c99830 
---------------------------------------------------------------------- 
Okay, you can stop posting valgrind output for the time being.  Please
patch your system with the uploaded patch, and reproduce the crash, if
possible.  If it doesn't crash, please upload the 5 minutes from the logs
when you attempted to get it to crash and it didn't.  If it does crash,
please run gdb and get the output of the command "p last_function".

Due to the stack corruption, all other gdb and valgrind output are
useless, at this point. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-10 13:27 Corydon76      Note Added: 0099830                          
======================================================================