Yes, that's correct. Sorry, I didn't think about the fact that I hadn't
explained that when I tried your suggestion. Setting both rtp-ip and
ext-rtp-ip explicitly solves the problem. That part of the mystery is
solved... THANK YOU.
Interestingly though, the previous settings for these values were:
param name="rtp-ip" value="$${bind_server_ip}"/
param name="ext-rtp-ip" value="$${external_rtp_ip}"/
(Nabble won't let me put the syntax markers '<' and '>' in)
And these worked just fine before. Any idea why they might have suddenly
stopped working? Can you use host:host.server.com to do a DNS lookup like
you can for the other SIP profiles?
Thanks again,
- Phil
--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Problems-with-GV-mod-dingaling-on-latest-stable-version-tp7583499p7583938.html
Sent from the freeswitch-users mailing list archive at Nabble.com.
_________________________________________________________________________
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