Yup, that was how I plan to fix it using LUA to figure out where to route the call (possibly proxying it via the other FS server). Just wanted to check I wasn't re-inventing the wheel before I go ahead and do it as it seems like the sort of issue other people would have dealt with. On Mon, Aug 2, 2010 at 5:10 PM, Steven Ayre <steveayre@gmail.com> wrote:
I haven't tried this myself, but routing the call via the FS server they registered too might work since it'll be the IP the NAT router is expecting traffic from.
-Steve
On 2 August 2010 16:10, Dan Lane <null@invalid.name> wrote:
Hi Guys,
I have a cluster of FS boxes all sharing SIP registrations using ODBC and under certain circumstances I can register Client-A on FS-A and Client-B on FS-B and make calls between Client-A and Client-B without issue as the relevant FS box knows how to get a call to the client from the shared registrations table.
However when the callee client is behind NAT (or using a SIP client configured to only allow calls from a server it has registered with) the call gets dropped by the NAT router (or client)
I can fix this easily with some LUA but before I do I wanted to check if there was an advisable or recognised FreeSWITCH way to work around this. ro Has anyone else solved this issue already?
Regards, Dan
_______________________________________________ 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
_______________________________________________ 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