I played with the ACLs but it didn't have any effect on the contact header. So I went into the code and after some investigation I stepped on the * sip-force-contact* variable. When this guy is set to * NDLB-connectile-dysfunction*, freeswitch overwrites the contact header with the IP/PORT it received the IP packet on, regardless of the actual nat state. Hynek On Wed, Nov 2, 2011 at 6:42 PM, Hynek Cihlar <hynek.cihlar@gmail.com> wrote:
Brad, Brian, thanks for your replies
Actually, the switch is not used in the standard setup, where the external profile is used as a gateway and the internal (default) profile for directly connected sip clients.
In my case, the switch has two profiles. The so called external is connected to another switch, just passing calls. The connection is routed. The second profile (internal) which is giving me troubles, is used for registering SIP clients. The SIP clients are usually behind their own NAT routers.
SIP-IP and EXT-SIP-IP are both the same public IP, since the router is publicly visible on the internal profile. On the external profile, they are assigned to a private internal IP. The switch is sitting on two subnets.
Now, the local-network-acl is set to localnet.auto on both profiles. I was assuming ACLs are used solely for security!
Hynek
On Wed, Nov 2, 2011 at 6:16 PM, Brian West <brian@freeswitch.org> wrote:
You also have to put in local-network-acl so it knows when to lie and when not to lie in the contact.
/b
On Nov 2, 2011, at 11:54 AM, Brad Mina wrote:
RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y
Let's take a look at what 'ext' might be! Keep in mind you'll need to change it on your external profile as well.
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org