Hi Brian, that didn't helped. I already had that param in my configuration, but even when specifying the exact public IP, FreeSWICTCH still uses the private one on WebSocket. I even tried with agressive-nat-detection, but that didn't worked either. Here is the output of "sofia status profile internal" which shows the public IP in Ext-RTP-IP and Ext-SIP-IP: Dialplan XML Context public Challenge Realm auto_from RTP-IP 172.XX.0.3 Ext-RTP-IP 8X.XX.XX.XX SIP-IP 172.XX.0.3 Ext-SIP-IP 8X.XX.XX.XX URL sip:mod_sofia@8X.XX.XX.XX:5060 BIND-URL sip:mod_sofia@8X.XX.XX.XX:5060;maddr=172.XX.0.3;transport=udp,tcp WS-BIND-URL sip:mod_sofia@172.XX.0.3:5066;transport=ws HOLD-MUSIC local_stream://moh OUTBOUND-PROXY N/A Can someone please confirm, that the WS-BIND-URL looks correctly? Thanks Bernhard Am 22.06.2014 22:05, schrieb Brian West:
Use ext-rtp-ip to fix that
Sent from my iPhone
On Jun 21, 2014, at 4:42 PM, Bernhard Wendel <bernhard@zeppelindesk.com> wrote:
<param name="ext-sip-ip" value="$${external_rtp_ip}"/>
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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