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

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Jul 20 11:49:06 CDT 2009


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 11:49 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.

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

---------------------------------------------------------------------- 
 (0107974) huangtx2009 (reporter) - 2009-07-20 11:49
 https://issues.asterisk.org/view.php?id=15522#c107974 
---------------------------------------------------------------------- 
I tested spansdp0.0.6 and spansdp0.0.5 and asterisk1.6.0.10. There is the
same problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-20 11:49 huangtx2009    Note Added: 0107974                          
======================================================================




More information about the asterisk-bugs mailing list