[asterisk-bugs] [Asterisk 0014807]: SendFax and T38 issues
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jun 9 09:00:07 CDT 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=14807
======================================================================
Reported By: moliveras
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14807
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.0-beta1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-04-01 16:06 CDT
Last Modified: 2009-06-09 09:00 CDT
======================================================================
Summary: SendFax and T38 issues
Description:
I am trying to get SendFax to work using a call file.
I initially tried it with asterisk-1.6.0.3 (spandsp-0.0.5pre4).
When I sent a call to a local spa2102 TA, the far end sent a re-invite to
switch over to T38, and the call went through as T38.
asterisk1.6.0.3 --> SBC --> ast1.4 --> spa2102
When I sent the call out to a land line via a carrier (SIP trunk),
asterisk receives the T38 reinvite, however the 200 OK that it sends back
only has g711 as a codec choice, and not udptl t38. As a result, the fax
failes.
asterisk1.6.0.3 --> SBC --> SIP trunk
I then tried upgrading to asterisk-1.6.2.0-beta1 (spandsp-0.0.6pre7).
Now when I make the call to the land line over the SIP trunk the behavior
is the same, however when I call the spa2102 line, ast1.6.2.0-beta1 rejects
the SIP reinvite with a 488, and the fax completes inband.
Also, the 1.6.2.0-beta1 spits out these errors while the fax in in
progress:
[Apr 1 13:53:41] ERROR[10228]: channel.c:2539 __ast_read: ast_read()
called with no recorded file descriptor.
I will attach packet captures for these scenarios momentarily. I can
reproduce this behavior consistently and can provide whatever info/debug is
needed.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-06-09 09:00 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list