[asterisk-bugs] [Asterisk 0015522]: Can not using T.38 origination with app_fax/spandsp

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15522 
====================================================================== 
Reported By:                huangtx2009
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15522
Category:                   Applications/app_fax
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-17 12:36 CDT
Last Modified:              2009-07-20 14:53 CDT
====================================================================== 
Summary:                    Can not using T.38 origination with app_fax/spandsp
Description: 
I tried to send a Fax from the first Asterisk (Asterisk1) to the second
Asterisk (Asterisk2). When Asterisk1 initiates an INVITE with CODEC G.711.
Asterisk2 accepts this INVITE. Immediately, Asterisk2 sends a RE-INVITE
with T.38 SDP. However Asterisk1 responds it with "488 not acceptable
here". 

So, Asterisk1 sends a Fax with G.711 instead of T.38.

====================================================================== 

---------------------------------------------------------------------- 
 (0107988) mmichelson (administrator) - 2009-07-20 14:53
 https://issues.asterisk.org/view.php?id=15522#c107988 
---------------------------------------------------------------------- 
The problem appears to be that app_fax in both 1.6.0.9 and 1.6.0.10 do not
properly handle the reception of AST_CONTROL_T38 frames of type
T38_REQUEST_NEGOTIATE. As a result, the SIP channel driver sends that 488
response after five seconds since it has not received an indication that
things are proceeding from app_fax.

This problem appears to have been corrected in the tip of the 1.6.0
branch. If you can, could you please try using a checkout of the current
1.6.0 branch and see if the same problem occurs? If it appears to be
working correctly, then you can be sure that 1.6.0.11 will have the problem
fixed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-20 14:53 mmichelson     Note Added: 0107988                          
======================================================================