[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 08:05 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0108940) kpfleming (administrator) - 2009-08-12 08:05
 https://issues.asterisk.org/view.php?id=15649#c108940 
---------------------------------------------------------------------- 
OK, we're getting closer to understanding the cause of this problem, but
I'll need one more packet capture; use the tcpdump method I posted here,
but don't filter it to just port 5060, because we'll need to see the UDPTL
traffic as well.

# tcpdump -i any -n -s 0 -w ~/t38-1.6.pcap udp

That should do the trick. Thanks for your quick responses and patience...
we'll get this figured out! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-12 08:05 kpfleming      Note Added: 0108940                          
======================================================================