[asterisk-bugs] [Asterisk 0016756]: app_fax doesn't receive fax with T.38

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16756 
====================================================================== 
Reported By:                viniciusfontes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16756
Category:                   Applications/app_fax
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                       SWP-845 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-02 13:56 CST
Last Modified:              2010-02-03 16:53 CST
====================================================================== 
Summary:                    app_fax doesn't receive fax with T.38
Description: 
When I try to receive a fax from a provider that supports T.38 using
ReceiveFAX() provided by app_fax.so, the fax transmission ends prematurely
with an error.

What happens (according to Kevin Fleming) is this:

"In this call, Asterisk sent a re-INVITE to T.38 mode
from audio mode, the provider accepted it, and then Asterisk
acknowledged it. Immediately afterwards, Asterisk sent a re-INVITE
*back* to audio mode, which the provider accepted (and included T.38
capabilities in their response). Because of this, the FAX reception
process failed since the T.38 session was destroyed."

For reference, here is a link to the original mailing list thread: 
http://lists.digium.com/pipermail/asterisk-users/2010-February/244136.html
====================================================================== 

---------------------------------------------------------------------- 
 (0117675) viniciusfontes (reporter) - 2010-02-03 16:53
 https://issues.asterisk.org/view.php?id=16756#c117675 
---------------------------------------------------------------------- 
Funny thing is, it is already set at 400! I'm pretty sure that's another
bug on Asterisk.

Here's the relevant section on my sip.conf:

[voxip]
username=5421047000
nat=no
type=peer
secret=5421047000
port=5060
canreinvite=no
insecure=port,invite
host=10.150.65.16
fromuser=5421047000
fromdomain=gvt.com.br
dtmfmode=rfc2833
context=entrada-e1
disallow=all
allow=g729,alaw
qualify=no
;t38pt_udptl=yes
t38pt_udptl = yes,maxdatagram=400 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-03 16:53 viniciusfontes Note Added: 0117675                          
======================================================================