[Freeswitch-dev] Call to registered phone behind NAT
khovayko at gmail.com
Mon May 24 13:24:59 PDT 2010
Brian West wrote:
> You shouldn't have to turn on aggressive nat detection. in the end your busted sipdroid should learn to overcome nat on its own.
Maybe.. but, when I turn ON, I see fs_path-es for outer clients. If it
is OFF, I never see fs_pathes.
Can you suggest, how to enforce "fs_path-es without
Also, I see another problem:
My friend in the Ukraine, uses phone behind NAT, too (situation like to
Sipdroid - he also behind NAT).
There is his registration record:
Call-ID: c4e76211 at 192.168.10.103
User: 1012 at 192.168.1.5
<sip:1012 at 192.168.1.136:1024;fs_nat=yes;fs_path=sip%3A1012%4091.207.244.1%3A1024>
Status: Registered(UDP-NAT)(unknown) EXP(2010-05-24 17:49:15)
MWI-Account: 1012 at 192.168.1.5
When he calls me, everything is OK, we can talk each to other.
But, when I call him (from LAN), he receives RING signal, pick up
handset -- and we both heard nothing.
Can you suggest, where to search?
> On May 24, 2010, at 2:20 PM, Oleg Khovayko wrote:
>> Hi, Michael
>> After some personal investigation, I've found param
>> aggressive-nat-detection, and uncommented it in the profile internal:
>> ./sip_profiles/internal.xml:<param name="aggressive-nat-detection"
>> After this step, I can see fs_path for remote sipdroid phone:
>> Call-ID: 845794751536 at 126.96.36.199
>> User: 1019 at 192.168.1.5
>> Contact: "user"
>> <sip:1019 at 188.8.131.52:43305;transport=udp;fs_nat=yes;fs_path=sip%3A1019%40184.108.40.206%3A16146%3Btransport%3Dudp>
>> Agent: Sipdroid/1.4.6 beta/T-Mobile G1
>> Status: Registered(UDP-NAT)(unknown) EXP(2010-05-24 17:13:49)
>> Host: olegh.ath.cx
>> IP: 220.127.116.11
>> Port: 16146
>> Auth-User: 1019
>> Auth-Realm: olegh.ath.cx
>> MWI-Account: 1019 at 192.168.1.5
>> Call goes OK, phone works!
>> Thank you for help,
>> FreeSWITCH-dev mailing list
>> FreeSWITCH-dev at lists.freeswitch.org
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev at lists.freeswitch.org
More information about the FreeSWITCH-dev