On 18/04/2012 6:39 AM, Kevin P. Fleming wrote:
On 04/17/2012 06:17 AM, Larry Moore wrote:
The send log you have posted does not show any outgoing T.38 packets
from your system.
I set up a test build of 1.8.11.0 using the patch recently released, I
have difficulties sending T.38 with this patch, in fact I cannot send
successfully however I can receive. I did however observe some outgoing
T.38 packets. The analogue fax modem I was dialling into is under my
control hence the log files showed there was no signalling coming from
my ITSP,
The T.38 session on my Asterisk server show the CRP's which were sent
from the analogue fax device during the negotiation.
The patch I have used for a while seems to give me outgoing
functionality as well as incoming.
I can't reproduce your scenario whereby your T.38 session is
communicating with a different gateway to the SIP server you use hence
can only speculate that Asterisk has difficulty wanting to send T.38 SDP
traffic when it is a different device than the SIP server it negotiates
with.
We know for a fact that Asterisk has no trouble with the signaling and
media going to different addresses/ports. Honestly, I just don't
understand why all of this effort is being put into trying to use an
old (and clearly broken) patch for adding T.38 gateway support to
Asterisk 1.8.
You guys know that it works in Asterisk 10, but you say you can't use
Asterisk 10 for some reason that I don't understand.
I have downloaded asterisk 10.3.0 and compiled on a Centos 6 system I
setup to compare behaviour on OpenBSD with a Linux version of asterisk
based upon the OpenBSD port.
Unfortunately the T.38 Gateway functionality in my build of 10.3.0
doesn't appear to work. Looking at the upgrade documentation from 1.8
there doesn't appear to be any considerations applicable to my setup.
As an excercise in futility I downloaded the Asterisk 1.8.11.0 source
and compiled using the version of T.38 patch I have maintained and
tested by sending a fax via an IAX channel out through my SIP provider,
the fax was sent successfully.
I then removed and recreated the asterisk 1.8.11.0 directory and applied
the back-port patch and observed the same problem when attempting to
send through the T.38 gateway as was observed in Asterisk 10.
Console output of Asterisk 1.8.11.0 with Asterisk 10 backport patch:
asterisk-dev*CLI>
-- Accepting AUTHENTICATED call from 192.168.54.12:
> requested format = slin,
> requested prefs = (),
> actual format = slin,
> host prefs = (slin|alaw|ulaw),
> priority = mine
-- Executing [NNNNNNNN@FAX-T30:1] Set("IAX2/iaxmodem1-4445",
"FAXOPT(t38gateway)=yes") in new stack
-- Executing [NNNNNNNN@FAX-T30:2] Dial("IAX2/iaxmodem1-4445",
"SIP/NNNNNNNN@itsp-fax,55") in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
-- Called SIP/NNNNNNNN@itsp-fax
-- SIP/itsp-fax-00000004 is making progress passing it to
IAX2/iaxmodem1-4445
-- SIP/itsp-fax-00000004 answered IAX2/iaxmodem1-4445
[Apr 23 21:14:11] NOTICE[14165]: channel.c:4152 __ast_read: Dropping
incompatible voice frame on SIP/itsp-fax-00000004 of format slin since
our native format has changed to 0x8 (alaw)
== Using UDPTL TOS bits 184
== Using UDPTL CoS mark 5
[Apr 23 21:14:12] ERROR[14165]: astobj2.c:110 INTERNAL_OBJ: user_data is
NULL
[Apr 23 21:14:23] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
[Apr 23 21:14:24] WARNING[14165]: res_rtp_asterisk.c:2135 ast_rtp_read:
RTP Read too short
Console output of Asterisk 10.3.0:
Connected to Asterisk 10.3.0 currently running on asterisk-dev (pid = 14798)
Verbosity is at least 3
Core debug is at least 3
-- Accepting AUTHENTICATED call from 192.168.54.12:
> requested format = slin,
> requested prefs = (),
> actual format = slin,
> host prefs = (slin|alaw|ulaw),
> priority = mine
-- Executing [NNNNNNNN@FAX-T30:1] Set("IAX2/iaxmodem1-863",
"FAXOPT(t38gateway)=yes") in new stack
-- Executing [NNNNNNNN@FAX-T30:2] Dial("IAX2/iaxmodem1-863",
"SIP/NNNNNNNN@itsp-fax,55") in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
-- Called SIP/NNNNNNNN@itsp-fax
-- SIP/itsp-fax-00000000 is making progress passing it to
IAX2/iaxmodem1-863
-- SIP/itsp-fax-00000000 answered IAX2/iaxmodem1-863
== Using UDPTL TOS bits 184
== Using UDPTL CoS mark 5
[Apr 23 21:25:15] ERROR[14983]: astobj2.c:110 INTERNAL_OBJ: user_data is
NULL
[Apr 23 21:25:26] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:26] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:26] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:26] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:27] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:27] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:27] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:27] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
.
.
.
[Apr 23 21:25:49] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
[Apr 23 21:25:49] WARNING[14983]: res_rtp_asterisk.c:2138 ast_rtp_read:
RTP Read too short
-- Executing [h@FAX-T30:1] NoOp("IAX2/iaxmodem1-863", "Call/Fax
Ended 2012-04-23 21:25:57 +0800") in new stack
== Spawn extension (FAX-T30, NNNNNNNN, 2) exited non-zero on
'IAX2/iaxmodem1-863'
-- Hungup 'IAX2/iaxmodem1-863'
A packet capture reveals T.38 invite coming from my ITSP but none
originating from asterisk to my ITSP.
I don't intend pursuing this further however I am awaiting the asterisk
10.x port on OpenBSD.
My five-cents worth!
Larry.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
