if you enable nat mode on the registrations it will lock the ip:port
make an acl that matches the ip of the client  and add the param
apply-nat-acl with the name of the acl you created to your sofia profile
then all calls from that ip will be known to be nat and the port locking code will activate.



On Fri, Nov 28, 2008 at 8:20 AM, x y <fs_ask_sy@citromail.hu> wrote:
Hy!

There are two different FS behind the same NAT, and there were Reigstration Failures about one or to times a day. The gateway status turned down, then I got 503 error codes. Then I set up the ext-ip to STUN, as the wiki requests it.
Now I facing the next problem:
Start the call, all goes right, INVITE goes to port 1352, then after 183 Session progress from port 1352, the PRACK package goes to 5060 instead of 1352, wich messes up the call procedure. Is there anyway to force PRACK to the port to the INVITE has been sent before?

Cheers,
Viktor



Hirdetés (x)
Váltson most olcsóbb kötelezőre a biztosítás-hu-val. www.biztositas.hu - a kötelező biztosítások kiindulópontja!
_______________________________________________
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/

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400