I need in one of your boxs... there is no way this is doing this unless you are putting stun:stun.freeswitch.org into the ext-rtp-ip or sip ip... which could make it trigger the ipv6 check since its just looking for : in the ip address. And stun: has that.. so you're triggering it... tar up your entire conf folder and mail it to me ASAP. /b On Jun 17, 2009, at 8:01 PM, Jason White wrote:
Raul Fragoso <raul@etellicom.com> wrote:
I can confirm the same issue, but it happens even with all the IPv6 stuff removed.
Thank you for the corroboration.
It only happens to me if I have the following in my external.xml profile: <param name="local-network-acl" value="localnet.auto"/>
Note that I need the above line for nat traversal; if I leave it out, FreeSWITCH uses a private IPv4 address in outgoing invites, and can't establish a call.
_______________________________________________ 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