[asterisk-bugs] [Asterisk 0015586]: [patch] Failure to negotiate T.38

[Asterisk Bug Tracker]

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 18:11 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
====================================================================== 

---------------------------------------------------------------------- 
 (0111887) kpfleming (administrator) - 2009-10-05 18:11
 https://issues.asterisk.org/view.php?id=15586#c111887 
---------------------------------------------------------------------- 
Just another comment, if you look at these lines from your log:

[Oct  5 14:56:41] DEBUG[32247] chan_sip.c: Overriding T38FaxMaxDatagram
'72' with '400'
[Oct  5 14:56:41] DEBUG[32247] chan_sip.c: FaxMaxDatagram: 400

You can see exactly how the override works; the peer sent you a re-INVITE
with 'T38FaxMaxDatagram: 72', but because you've configured an override to
'400', the value was overridden and processing continued as if the peer had
sent '400' in their re-INVITE. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-05 18:11 kpfleming      Note Added: 0111887                          
======================================================================