[asterisk-bugs] [Asterisk 0016692]: [patch] Missing fallback to audio fax feature when T.38 re-INVITE failed for 1.4
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jun 1 09:54:11 CDT 2010
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=16692
======================================================================
Reported By: vrban
Assigned To: pabelanger
======================================================================
Project: Asterisk
Issue ID: 16692
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
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:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2010-01-25 07:21 CST
Last Modified: 2010-06-01 09:54 CDT
======================================================================
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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0008677 Asterisk does not reinvite peer for G.7...
related to 0016795 1.4 does not send any SIP messages afte...
related to 0016792 [patch] 606 Not Acceptable is also a va...
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-06-01 09:54 svnbot Status assigned => resolved
2010-06-01 09:54 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list