[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:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13050
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
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-01-22 14:48 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0098487) blitzrage (administrator) - 2009-01-22 14:48
 http://bugs.digium.com/view.php?id=13050#c98487 
---------------------------------------------------------------------- 
schern:  if you can reproduce, could you get us the valgrind output so that
we could move this issue forward?

See the doc/valgrind.txt file in your asterisk source for how to get that.
Once you can reproduce it, then upload the file to this bug. Note that
asterisk may not crash while running in valgrind, so just do as you would
normally do to reproduce the bug, then stop the valgrind process and upload
the output, as it may still be useful even if it prevents a crash.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-22 14:48 blitzrage      Note Added: 0098487                          
======================================================================