<HTML>
<HEAD>
<TITLE>Re: [Freeswitch-users] Clustering FreeSWITCH</TITLE>
</HEAD>
<BODY>
<FONT SIZE="4"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>I had this same prblem, so the solution was to re-route the traffic with the info in the sip_registration database via the server the nat’d client had registered to... This solves the NAT issue... Of couse if we didn’t have to deal with NAT things would be much easier heh<BR>
<BR>
<BR>
<BR>
<B>From: </B>Marc Lewis <marc@avvatel.com><BR>
<B>Organization: </B>Avvatel Corporation<BR>
<B>Reply-To: </B><freeswitch-users@lists.freeswitch.org><BR>
<B>Date: </B>Wed, 29 Oct 2008 19:10:32 -0700<BR>
<B>To: </B><freeswitch-users@lists.freeswitch.org><BR>
<B>Subject: </B>Re: [Freeswitch-users] Clustering FreeSWITCH<BR>
<BR>
I actually spent a big chunk of today doing various tests. Freeswitch is doing all the right things in this scenario. The problem actually turns out to be my router/firewall that I'm testing behind. When the phones register, it only opens up the port back from the IP address of the server it registers to, so when the secondary server tries to send the invite, the router blocks it. In case anyone is curious, the router/firewall is a Linux box running Arno's Firewall. I'll be doing more tests with different routers to see which ones work and which ones don't. I'll post my results on the wiki page that I'll be creating that covers the setup I've got.<BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>