Thanks Phil. I'll try again, but my rtp-ip and sip-ip (the internal) are already correctly set (ie 192.168.1.200). The problem is that if the phone registered has belongs to a different (but still local) subnet (ie 192.168.2.143), then FS uses the external IP (ie 85.43.25.64) And no audio at all Any more suggestion? giuliano On Tuesday 24 July 2012 15:18:35 Phil Quesinberry wrote:
Set rtp-ip and sip-ip to your internal IP address. I believe that you should also be able to set it to: $${local_ip_v4} or $${bind_server_ip} as well.
- Phil
---------- VirteX g.d.monnezza at tiscali.it <mailto:freeswitch-users%40lists.freeswitch.org?Subject=%5BFreeswitch-users% 5D%20%20AutoNAT%20-%20Local%20Networks%20not%20excluded&In-Reply-To=> Tue Jul 24 16:12:08 MSD 2012
Hi guys. I appreciate so much the Auto-NAT for uPnP capable firewalls. But I'm experiencing an issue. I have a FreeSwitch server behind a NAT, but I can't find a way to avoid FreeSwitch using external IP (for SIP and RTP) for local networks (i.e. 192.168.0.0/16). In my sip profiles for various interfaces I have NOT set the . Anyway, the sofia status for all interfaces shows the EXT-RTP-IP and EXT-SIP-IP set (with my public gateway IP). That's ok, even if I didn' declard it with My SIP phones register from a network different from the server one, but still a local network. Then, SIP phones receive (from the server) the rtp and sip signalling with its external IP. This prevent any communication. How it is possible to tell FreeSwitch to NOT use ext IP for particular networks? Thanks to anyone who will point me in the right direction. g