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
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