[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-11 11:56 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0099911) gerd1000 (reporter) - 2009-02-11 11:56
 http://bugs.digium.com/view.php?id=13050#c99911 
---------------------------------------------------------------------- 
@schern: try other firmware, 5.2.3, 5.1.12 or 5.1.10. I did not check since
6 months if there is newer firmware available and haven't checked if this
model is still available or replaced by some other model from cisco.

Changing the value of LOCAL_FAX_MAX_DATAGRAM was a quick hack which worked
for me. It seems that there are several enhancements now available
(unlicensed patch and the one from 2009-02-11 10:07). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-11 11:56 gerd1000       Note Added: 0099911                          
======================================================================