[asterisk-bugs] [Asterisk 0009759]: T.38 Fax Outbound (revision of bug 9356)

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9759 
====================================================================== 
Reported By:                mindthegap
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   9759
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0-beta4 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 65201 
Disclaimer on File?:        No 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             05-19-2007 06:12 CDT
Last Modified:              03-11-2008 15:16 CDT
====================================================================== 
Summary:                    T.38 Fax Outbound (revision of bug 9356)
Description: 
When placing outbound Fax call with ATA to Asterisk to SIP Provider (with
T.38 support) to a landline fax only first page gets sent and call is hung
up and sending fax reports "Fax Failure" (this even if fax is only one
page).

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0009356 T38 outbound
====================================================================== 

---------------------------------------------------------------------- 
 file - 03-11-08 15:16  
---------------------------------------------------------------------- 
After looking at this again I am convinced it is a Cisco issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-11-08 15:16  file           Status                   acknowledged => resolved
03-11-08 15:16  file           Resolution               open => no change
required
03-11-08 15:16  file           Note Added: 0083759                          
======================================================================