[asterisk-bugs] [Asterisk 0013050]: Memory segmentation fault on T.38 pass through
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Feb 9 14:24:02 CST 2009
The following issue requires your FEEDBACK.
======================================================================
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-09 14:24 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.
======================================================================
----------------------------------------------------------------------
(0099734) Corydon76 (administrator) - 2009-02-09 14:24
http://bugs.digium.com/view.php?id=13050#c99734
----------------------------------------------------------------------
I believe this is already fixed. Please upgrade to an SVN 1.4 checkout
which exceeds revision number 168603 and try again.
Issue History
Date Modified Username Field Change
======================================================================
2009-02-09 14:24 Corydon76 Note Added: 0099734
2009-02-09 14:24 Corydon76 Status acknowledged =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list