[asterisk-users] UDPTL T38 via NAT
Remco Bressers
rbressers at signet.nl
Tue Jun 22 09:52:44 CDT 2010
On 06/22/2010 04:35 PM, Johann Steinwendtner wrote:
> On 2010-06-22 15:16, Remco Bressers wrote:
>> On 06/22/2010 02:51 PM, Johann Steinwendtner wrote:
>>> On 2010-06-22 12:36, Remco Bressers wrote:
>>>> Dear list,
>>>>
>>>> I've got the following setup :
>>>>
>>>> [FAX-ATA]--[PBX LAN]--[Firewall]--[PBX WAN]-----[upstream SIP]
>>>>
>>>> On the PBX's we run Asterisk 1.4.33 with t38pt_udptl=yes in [general].
>>>> The FAX ATA is a Teles VoIPBox with T.38 support (that works). On the
>>>> PBX WAN, i see the following in udptl debug :
>>>>
>>>> Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 184, len 32)
>>>> Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 32)
>>>> Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 185, len 32)
>>>> Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 32)
>>>> Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 186, len 32)
>>>> Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 29)
>>>>
>>>> This means my outgoing udptl traffic is correctly translated, but
>>>> somehow i'm sending 172.16.0.156 instead of my public IP address on the
>>>> firewall.
>>>>
>>>
>>>
>>> Did you try t38pt_usertpsource=yes ?
>>>
>>
>> Hi,
>>
>> Yes, i tried adding that to the SIP peer configuration for the FAX ATA.
>> Should i put it on the PBX trunk configuration also??
>>
>> Remco
>>
> Yes.
>
This results in the very same problem :
Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 101, len 32)
Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 32)
Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 102, len 32)
Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 32)
Sent UDPTL packet to 172.16.0.156:4460 (type 0, seq 103, len 32)
Got UDPTL packet from 62.180.xx.xx:36170 (type 0, seq 0, len 29)
--
Kind regards,
Signet bv
Remco Bressers
T 040 - 707 4 907
F 040 - 707 4 909
E rbressers at signet.nl
More information about the asterisk-users
mailing list