[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-12 13:57 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0100039) gerd1000 (reporter) - 2009-02-12 13:57
 http://bugs.digium.com/view.php?id=13050#c100039 
---------------------------------------------------------------------- 
I don't think that this a is problem of udptl.c but a problem of one of the
media gateways (either linksys and/or carrier side) or FAX G3 itself. So,
from my point of view, this bug could be closed as it seems to be an
interoperability problem.

Try national call (B. said to me that the network in Germany is more
recent).
You may try different settings of error correction, although I dont
believe it helps.