[asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
Michael Maier
m1278468 at mailbox.org
Sun Jun 4 08:40:36 CDT 2017
On 06/04/2017 at 01:41 PM Telium Technical Support wrote:
> Just a guess (without knowing about your network), but are the two ends
> points on public networks and visible to one another? If not the reinvite
> may be passing an internal (nat'ed) address to the other and the connection
> will fail...just a though
t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen
udp\$127.0.0.1:6060 --ptty +/dev/ttyT380,+/dev/ttyT381 --route
'modem:.*=sip:<dn>@127.0.0.1:5061' --route 'sip:.*=modem:<dn>'
--sip-register 91 at 127.0.0.1:5061,password
I tried it with a global IP (instead of 127.0.0.1) - same behavior.
The point is, that the receiving part, which initiates the t.38 switch,
doesn't sent the switch to the ISP. It is blocked / ignored by asterisk
at all - don't know why it isn't sent to the ISP.
The extension is a normal pjsip extension with these additional options:
t38_udptl : true
t38_udptl_ec : redundancy
t38_udptl_ipv6 : false
t38_udptl_maxdatagram : 400
t38_udptl_nat : no (or yes - doesn't matter)
The trunk looks exactly the same:
t38_udptl : true
t38_udptl_ec : redundancy
t38_udptl_ipv6 : false
t38_udptl_maxdatagram : 400
t38_udptl_nat : no (or yes - doesn't matter)
Thanks,
Michael
More information about the asterisk-users
mailing list