[Home]

Summary:ASTERISK-09474: T.38 Fax Outbound (revision of bug 9356)
Reporter:Giovanni (mindthegap)Labels:
Date Opened:2007-05-19 06:12:19Date Closed:2011-06-07 14:00:30
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/T.38
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) Full.zip
Description:When placing outbound Fax call with ATA to Asterisk to SIP Provider (with T.38 support) to a landline fax only first page gets sent and call is hung up and sending fax reports "Fax Failure" (this even if fax is only one page).


****** ADDITIONAL INFORMATION ******

Environment behind NAT
ATA: IP 172.16.1.14, Wellgate 3701b, T.38 enabled, Extension 401
Asterisk: IP 172.16.1.15, SVN trunk 65201
SIP Provider: Eutelia, Registration IP: 83.211.227.21

Two tests done (see Full.WithReInvite e Full.WithNoReinvite), with
debug level 5
verbose level 5
sip debug
udptl debug

In one case (Full.WithReInvite), in sip_additional.conf extension 401 is configured as follows:

type=friend
secret=********
record_out=Adhoc
record_in=Adhoc
qualify=no
port=5060
nat=yes
mailbox=401@device
host=dynamic
dtmfmode=rfc2833
dial=SIP/401
context=from-internal
canreinvite=yes
callerid=device <401>
t38pt_udptl=yes


In the second case, (NoReinvite) is configured as follows:

type=friend
secret=Password1
record_out=Adhoc
record_in=Adhoc
qualify=no
port=5060
nat=yes
mailbox=401@device
host=dynamic
dtmfmode=rfc2833
dial=SIP/401
context=from-internal
canreinvite=no
callerid=device <401>
t38pt_udptl=yes

Tried both with nat=never and nat=yes in both configurations.
Comments:By: Giovanni (mindthegap) 2007-05-19 06:13:51

Supplied log files are clean: asterisk startup, one extension, one call attempt, asterisk shutdown so not too much crap in them

Ata is Welltech 3701B with latest Firmware


By: Joshua C. Colp (jcolp) 2008-02-25 11:52:00.000-0600

This actually looks at an issue with the Cisco. It sends a reinvite to go back to RTP after the T38 invite, presumably before the fax has completed. Quite curious.
By: Joshua C. Colp (jcolp) 2008-03-11 15:16:56

After looking at this again I am convinced it is a Cisco issue.