NAT

From FreeSWITCH Wiki

Jump to: navigation, search

Many people suffer from NAT issues which come from a misunderstanding of how SIP, RTP and FreeSWITCH work. The topic comes up frequently in the IRC chat room. Please see the following links to aid you in your endeavours.

  • External profile - this covers the topic of what makes the external profile so NAT traversal friendly in regards to SIP and RTP protocols. Also, this roughly covers the concept of copying from the external profile and creating a new profile that will enable you to cleanly traverse your NAT/firewall situation.
  • NAT Traversal - General information regarding NAT and devices.

NAT just works!

For sip you can set your SIP IP to a stun server like "stun:stun.fwdnet.net" or to your external non-NAT IP. For RTP you set the value to "auto".

<param name="sip-ip" value="1.2.3.4"/> <param name="rtp-ip" value="auto"/>

If FreeSWITCH discovers that the registered endpoint is behind NAT, it will send SIP OPTIONS packets every 30 seconds to the endpoint to keep NAT alive. It is recommended though, that every endpoint be configured to send NAT keepalives itself.

For user NAT traversal, see NAT Traversal

Retrieved from "http://wiki.freeswitch.org/wiki/NAT"
Personal tools
Community