on internal profile you’ll need to open ports otherwise UA can’t register.
on external profile you only need to open ports when you get inbound calls without an active register (ip auth calls).
2. Is this always a good idea to enable in sip_profiles/internal.xml?
<param name="nat-options-ping" value="true“/>
if you have UA on the internal profile which are behind NAT themselves it is a good idea to keep the pinhole open in the customers firewall.
3. Is it necessary/recommended to have STUN enabled in vars.xml AND setup the nat-options-ping?
if you mean STUN for registering with external gateways it depends on your firewall config
4. my sip_profile/internal.xml has this:
<param name="ext-rtp-ip" value="auto-nat"/>
<param name="ext-sip-ip" value="auto-nat"/>
Is this an improvement over what's in confluence of:
<param name="ext-rtp-ip" value="$${external_rtp_ip}“/>
with auto-nat FS checks your IP and if it is RFC1918 range than it enables nat helper features.
5. If the endpoints are configured to connect using TCP, does any of this change what's above?
thanks!
no changes here...
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com
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