[asterisk-bugs] [Asterisk 0015649]: T38 Faxing failing on 1.6.1 svn

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15649 
====================================================================== 
Reported By:                dazza76
Assigned To:                kpfleming
====================================================================== 
Project:                    Asterisk
Issue ID:                   15649
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.1.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 209900 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-04 06:28 CDT
Last Modified:              2009-08-12 07:56 CDT
====================================================================== 
Summary:                    T38 Faxing failing on 1.6.1 svn
Description: 
I am attempting to send faxes via t.38 through 2 asterisk servers
i.e
patton -> asterisk 1.6.1 -> asterisk 1.6.1 -> carrier 
what i have noticed is the fax negotiates but no data seems to make it,

when watching the console the below lines appear 
this does not happen on 1.6.1.1 or 1.6.1.2 but does happen on the svn rev
209900
 
the reason for the upgrade is the due to a segfault of ulaw fallback  on 1
carrier i.e issue 15290
Please let me know what log files are required.
====================================================================== 

---------------------------------------------------------------------- 
 (0108939) kpfleming (administrator) - 2009-08-12 07:56
 https://issues.asterisk.org/view.php?id=15649#c108939 
---------------------------------------------------------------------- 
On Linux (like many other platforms), using VLANs means you have virtual
interfaces on top of the real interface, and the virtual interfaces are
where the IP addresses live and the packet captures are normally done. In
any case, this packet capture does seem to be complete.

I can see one small bug in this capture which we can fix, although I don't
believe it is the source of the problem. I'll continue looking into it this
morning when I get to the office. In the meantime, you should also contact
the CallWeaver folks and tell them they have a bug; Asterisk sent a T.38
reINVITE to CallWeaver with "T38FaxUdpEC:t38UDPFEC" and CallWeaver
responded with "T38FaxUdpEC:t38UDPRedundancy", which is a protocol
violation (according to the T.38 recommendation, it must respond with
t3UDPFEC if that's what we offered or no EC mode at all). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-12 07:56 kpfleming      Note Added: 0108939                          
======================================================================