also you can set sip_sticky_contact=true channel var which will make that session turn on nat lock in the b leg so they can't change the contact to a nat addr add it in {} to your dial string like {sip_sticky_contact=true}sofia/internal/foo@bar.com On Wed, Jan 27, 2010 at 11:50 AM, Brian West <brian@freeswitch.org> wrote:
update to trunk. and don't use agressive-nat, set local-network-acl, set the ext-rtp-ip and ext-sip-ip to autonat:x.x.x.x or if you're behind a natpmp or upnp router set it to auto-nat.
It should just work. Again you have no real way to know if the far end client never lies to you. Which it should never do anyway. Endpoints should know how to traverse their own nat and not leave it up to the registrar to figure it out.
/b
On Jan 27, 2010, at 11:31 AM, Bill W wrote:
Thoughts? Suggestions?
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900