[asterisk-bugs] [Asterisk 0016591]: res_fax-1.6.1.5_1.1.6 doesn't trigger T.38 reinvites on fax send (receive works)
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 13 09:17:19 CST 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16591
======================================================================
Reported By: zalex1953
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16591
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.12
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-12 16:24 CST
Last Modified: 2010-01-13 09:17 CST
======================================================================
Summary: res_fax-1.6.1.5_1.1.6 doesn't trigger T.38 reinvites
on fax send (receive works)
Description:
Older (pre-1.6.1.5) versions of res_fax.so would send T.38 reinvites if
option 'z' was provided for SendFAX (per FFA admin manual, revisions B2 and
C)
The latest version of res_fax.so fails to do that, message
notice NOTICE[24818]: res_fax.c:717 in generic_fax_exec: Waiting for T.38
negotiation for send on SIP/a.b.c.d:5060-00000000
is displayed and SendFAX eventually terminates without starting fax
negotiations.
======================================================================
----------------------------------------------------------------------
(0116585) lmadsen (administrator) - 2010-01-13 09:17
https://issues.asterisk.org/view.php?id=16591#c116585
----------------------------------------------------------------------
You will likely have to provide SIP traces along with console output with
the debugging information enabled. Also, if you are a commercial support
customer (i.e. you purchased licenses) this may be an issue you should
report to Digium directly, and not via the open source issue tracker.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-13 09:17 lmadsen Note Added: 0116585
2010-01-13 09:17 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list