Hi all, I cannot find such information on wiki/docs. I've a SIP device in my NAT'd LAN connecting to a SIP server outside the LAN. Today the server is an asterisk one, and I put nat=yes to my device's enry in sip.conf I tried to connect to a FS sever in the same scenario, and FS tries to answer to the 192.168 private IP of device. Is there a way to make FS acting in the same nat=<val> way asterisk acts? I cannot put a bridging SIP proxy on my LAN in a easy way, device does not support NAT traversal and IAX. thanks, cosimo. -- Cosimo Alfarano <kalfa@bononia.it>
Consider using openser + rtpproxy in front of your media boxes ( be they asterisk or freeswitch ). -Chris On May 8, 2007, at 10:28 AM, Cosimo Alfarano wrote:
Hi all,
I cannot find such information on wiki/docs.
I've a SIP device in my NAT'd LAN connecting to a SIP server outside the LAN.
Today the server is an asterisk one, and I put nat=yes to my device's enry in sip.conf
I tried to connect to a FS sever in the same scenario, and FS tries to answer to the 192.168 private IP of device.
Is there a way to make FS acting in the same nat=<val> way asterisk acts?
I cannot put a bridging SIP proxy on my LAN in a easy way, device does not support NAT traversal and IAX.
thanks, cosimo.
-- Cosimo Alfarano <kalfa@bononia.it>
-- \\\|||/// \ Chris Parker - Segmentation Fault ( core dumped ) \ ~ ~ / \ | @ @ | \ http://www.segv.org | cparker@segv.org oOo (_) oOo \ ------------------------------------------------------------------------ # OS's are nothing more than device drivers! #
On 8 May 2007, at 17:35, Chris Parker wrote:
Consider using openser + rtpproxy in front of your media boxes ( be they asterisk or freeswitch ).
Sure, that's a way to obtain it right now. And probably I will. Is it, asterisk-like nat=<val> or similar approach, intended to be developed in future? thanks, cosimo.
On May 11, 2007, at 5:28 AM, Cosimo Alfarano wrote:
On 8 May 2007, at 17:35, Chris Parker wrote:
Consider using openser + rtpproxy in front of your media boxes ( be they asterisk or freeswitch ).
Sure, that's a way to obtain it right now. And probably I will.
Is it, asterisk-like nat=<val> or similar approach, intended to be developed in future?
Yes, from what I understand that's one of the areas still being worked on. For now, the NAT traversal capabilities of openser are stable and well developed. As always, patches/suggestions are welcome. :) -Chris -- \\\|||/// \ Chris Parker - Segmentation Fault ( core dumped ) \ ~ ~ / \ | @ @ | \ http://www.segv.org | cparker@segv.org oOo (_) oOo \ ------------------------------------------------------------------------ # OS's are nothing more than device drivers! #
Just a little FYI. The nat traversal stuff in FreeSWITCH is semi transparent and just works. Read the default sofia.conf.xml /b On May 11, 2007, at 8:35 AM, Chris Parker wrote:
Yes, from what I understand that's one of the areas still being worked on. For now, the NAT traversal capabilities of openser are stable and well developed.
As always, patches/suggestions are welcome. :)
participants (3)
-
Brian West
-
Chris Parker
-
Cosimo Alfarano