[asterisk-bugs] [Asterisk 0015770]: [patch] faxing with T.38 fails

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15770 
====================================================================== 
Reported By:                Had
Assigned To:                kpfleming
====================================================================== 
Project:                    Asterisk
Issue ID:                   15770
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-24 12:10 CDT
Last Modified:              2009-08-25 16:28 CDT
====================================================================== 
Summary:                    [patch] faxing with T.38 fails
Description: 
I have asterisk 1.4.26.1 setup with T.38 passthrough. I have linksys 2102
ATA and my provider use Cisco gateway with T.38 support enabled. Everytime
I send fax this fail with no apparent reason. 
In sip debug logs it looks that T.38 negotiation was successfull, later I
receive SIP BYE packet from provider and the call si hangup but no fax is
sent.
====================================================================== 

---------------------------------------------------------------------- 
 (0109640) kpfleming (administrator) - 2009-08-25 16:28
 https://issues.asterisk.org/view.php?id=15770#c109640 
---------------------------------------------------------------------- 
I'm working on it, but it's complicated because your carrier's system is
switching from audio to T.38 mode without changing UDP port numbers, which
Asterisk is not yet prepared to handle properly. I'll try to post an
updated patch today. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-25 16:28 kpfleming      Note Added: 0109640                          
======================================================================