[asterisk-bugs] [Asterisk 0015586]: [patch] Failure to negotiate T.38
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Oct 5 17:03:16 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15586
======================================================================
Reported By: globalnetinc
Assigned To: kpfleming
======================================================================
Project: Asterisk
Issue ID: 15586
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Target Version: 1.6.2.0
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-07-26 15:57 CDT
Last Modified: 2009-10-05 17:03 CDT
======================================================================
Summary: [patch] Failure to negotiate T.38
Description:
To implement T.38 on most ATAs their is a reinvite required. In the
process of gatewaying the T.38 negotiations the Asterisk server is not
doing this correctly. On versions past 1.6.0.10 it does not even send the
same ports on the RTP streams to both parties.
Every version past 1.6.0.10 fails
1.6.0.11
1.6.1.0
1.6.1.1
1.6.2.0-rc
This also includes the new T.38 stack that is is being introduced. in the
SVN tree of 1.6.1.1 and 1.6.2.0
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0015886 T38 udptl.c bufferoverflow
======================================================================
----------------------------------------------------------------------
(0111881) globalnetinc (reporter) - 2009-10-05 17:03
https://issues.asterisk.org/view.php?id=15586#c111881
----------------------------------------------------------------------
unless it is hard set in the sip.conf the udptl code treats them all as
T.38 support : Yes
T.38 EC mode : FEC
T.38 MaxDtgrm: -1
it does not read the info from the sip/sdp header. If you set them all
then the fax goes through. I have now tried 6 different sip providers/fax
servers. The all work if they are set by hand.
Issue History
Date Modified Username Field Change
======================================================================
2009-10-05 17:03 globalnetinc Note Added: 0111881
======================================================================
More information about the asterisk-bugs
mailing list