[Freeswitch-users] NAT issue with registration responses going to the wrong port

[Alex Kinch]

I thought that may be the case, which is why last week I wiped my dev  
box and started again :)

Aggressive nat detection is in the internal.xml profile, as is apply- 
nat-acl. the relevent section of acl.conf.xml is:

<list name="rfc1918" default="deny">
       <node type="allow" cidr="10.0.0.0/8"/>
       <node type="allow" cidr="172.16.0.0/12"/>
       <node type="allow" cidr="192.168.0.0/16"/>
     </list>


So it's all like it should be. What I can't figure out is how come FS  
manages to get the reply to one of the registers through to the right  
port but the second one goes completely wrong? Incidently if I map  
5060 on the external IP through to port 5060 on the device's internal  
IP it works fine, but that's not quite the point :)

Alex

On 7 Jul 2008, at 15:10, Brian West wrote:

> Looks like you're running some older configs..
>
> Make sure you have these options on your sip profile:
>
>     <param name="apply-nat-acl" value="rfc1918"/>
>     <param name="aggressive-nat-detection" value="true"/>
>
> And the latest acl.conf.xml installed.
>
> Rinse and repeat!
>
> /b
>
>
> On Jul 7, 2008, at 8:58 AM, Alex Kinch wrote:
>
>> Certainly.. Here's one I made earlier. Can do a more up to date and
>> in depth one if you want more.
>
> Brian West
> sip:brian at freeswitch.org
>
>
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org