[asterisk-bugs] [Asterisk 0016692]: [patch] Missing fallback to audio fax feature when T.38 re-INVITE failed for 1.4

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16692 
====================================================================== 
Reported By:                vrban
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16692
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.29 
JIRA:                       SWP-795 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-25 07:21 CST
Last Modified:              2010-01-29 15:30 CST
====================================================================== 
Summary:                    [patch] Missing fallback to audio fax feature when
T.38 re-INVITE failed for 1.4
Description: 
When a  T.38 re-INVITE failed with an 488 or 606 answer, we should fallback
to audio fax by send a re-re-INVITE without T.38. The function is
backported from 1.6 asterisk. Some people say this is a feature, other say
that it is a bug that 1.4 does not fallback to audio. Here is the patch.
====================================================================== 

---------------------------------------------------------------------- 
 (0117393) lmadsen (administrator) - 2010-01-29 15:30
 https://issues.asterisk.org/view.php?id=16692#c117393 
---------------------------------------------------------------------- 
Russell has agreed this is a bug, so I'm moving this up to Ready for
Testing 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-29 15:30 lmadsen        Note Added: 0117393                          
2010-01-29 15:30 lmadsen        Status                   confirmed => ready for
testing
======================================================================