Michael Jerris wrote:
It's not ignoring the fs_path, it doesn't have one. šCheck your nat related settings in your sip profile, specifically your ext-sip-ip, nat-acl and localnet-acl settings. šYou would see the fspath in the contact and nat in the status if this was set correctly.
Everything exactly as same as in default configuration, everywhere is auto-nat:

[root@olegh /usr/local/freeswitch/conf/sip_profiles]# grep ext-sip-ip internal.xml
ššš <param name="ext-sip-ip" value="auto-nat"/>

[root@olegh /usr/local/freeswitch/conf/sip_profiles]# grep t-acl internal.xml
ššš <param name="apply-nat-acl" value="nat.auto"/>

and you see, no localnet-acl settings in there.

////////////////////////////////////////////////////////////////////////////////


There is output of "sofia status profile internal", external Ext-RTP-IP/Ext-SIP-IP both correct:

Nameššššššššššššššššššš internal
Domain Namešššššššššššš N/A
Auto-NATššššššššššššššš true
DBNameššššššššššššššššš sofia_reg_internal
Pres Hosts
Dialplanššššššššššššššš XML
Contextšššššššššššššššš public
Challenge Realmšššššššš auto_from
RTP-IPššššššššššššššššš 192.168.1.5
Ext-RTP-IPššššššššššššš 173.73.120.93
SIP-IPššššššššššššššššš 192.168.1.5
Ext-SIP-IPššššššššššššš 173.73.120.93
URLšššššššššššššššššššš sip:mod_sofia@192.168.1.5:5060
BIND-URLššššššššššššššš sip:mod_sofia@192.168.1.5:5060
HOLD-MUSICššššššššššššš local_stream://moh
OUTBOUND-PROXYššššššššš N/A
CODECS INšššššššššššššš G7221@32000h,G7221@16000h,G722,PCMU,PCMA,GSM
CODECS OUTššššššššššššš G7221@32000h,G7221@16000h,G722,PCMU,PCMA,GSM
TEL-EVENTšššššššššššššš 101
DTMF-MODEšššššššššššššš rfc2833
CNGšššššššššššššššššššš 13
SESSION-TOššššššššššššš 0
MAX-DIALOGššššššššššššš 0
NOMEDIAšššššššššššššššš false
LATE-NEGššššššššššššššš false
PROXY-MEDIAšššššššššššš false
AGGRESSIVENATšššššššššš false
STUN-ENABLEDššššššššššš true
STUN-AUTO-DISABLEšššššš false
CALLS-INššššššššššššššš 168
FAILED-CALLS-INšššššššš 32
CALLS-OUTšššššššššššššš 98
FAILED-CALLS-OUTššššššš 59


/////////////////////////////////////////////////

freeswitch@internal> sofia status

šššššššššššššššš internalšššššš profilešššššššššššš sip:mod_sofia@192.168.1.5:5060ššššš RUNNING (0)
ššššššššššššš 192.168.1.5šššššššš aliasšššššššššššššššššššššššššššššššššš internalššššš ALIASED


Really, with debug print, I see debug messages for Originarot's phone during call:

2010-05-23 18:55:57.399958 [DEBUG] sofia.c:5847 IP 192.168.1.130 Rejected by acl "domains". Falling back to Digest auth.
2010-05-23 18:55:57.501841 [DEBUG] sofia.c:5847 IP 192.168.1.130 Rejected by acl "domains". Falling back to Digest auth.

But, it works OK no LAN, despite these messages.


And, you right, after upgrade FS to 1.0.6, all fs_path-es gone.
How to restore it?


Thanks,

Oleg





Mike

On May 23, 2010, at 1:01 PM, Oleg Khovayko wrote:

Brian West wrote:


I really find that one hard to believe. š

Hard to believe, but this is true:


I have made PURE experiment.
My friend has registered SIP-phone behind NAT in Ukraine.
His registration:

Call-ID:ššššššš 4a978b30@192.168.10.103
User:šššššššššš 1012@192.168.1.5
Contact:ššššššš "user" <sip:1012@192.168.1.136:1024>
Agent:ššššššššš AcctonVoIP/2.5
Status:šššššššš Registered(UDP)(unknown) EXP(2010-05-23 14:27:20)
Host:šššššššššš olegh.ath.cx
IP:šššššššššššš 91.207.244.1
Port:šššššššššš 1024
Auth-User:ššššš 1012
Auth-Realm:šššš olegh.ath.cx
MWI-Account:ššš 1012@192.168.1.5


I tried call 1001 -> 1012, fs_cli prints:


2010-05-23 12:37:01.593320 [NOTICE] switch_channel.c:669 New Channel sofia/internal/sip:1012@192.168.1.136:1024 [2b79d969-8966-df11-ac63-005004c3cb7e]

I sniffed network traffic, FS tries connect to his LAN address from "Contact", not his real address:

olegh# tcpdump host'(192.168.1.136 or 91.207.244.1)'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on xl0, link-type EN10MB (Ethernet), capture size 96 bytes
12:40:55.044208 arp who-has 192.168.1.136 tell deskpro.khovayko.com
12:40:55.544711 arp who-has 192.168.1.136 tell deskpro.khovayko.com
12:40:56.545145 arp who-has 192.168.1.136 tell deskpro.khovayko.com
12:40:58.546827 arp who-has 192.168.1.136 tell deskpro.khovayko.com


sofia profile xxx siptrace on

I will be you its NOT ignoring the fs_path you just can't see the packet leaving and since its TCP the far side nat I suspect has closed the nat translation thus you'll need to register more often or enable keep alives on the device.

/b


I tried to do this -- results as same as with tcpdump.
My local phone has number 1001, IP=192.168.1.130, try to call 1012 (behind NAT, see registration above):



_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org