Maybe better solution is
also to enable rport on the device, this will likely fix the problem for
you.
Mike
Mike
_________________________________________________________________________
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
--
This message has been scanned for viruses and dangerous content, and is believed to be clean.
Hello list,
We are having some problems with customer behind nat, where freeswitch
is responding to the contact headers address, which fails as the client
is using its internal IP and port information.
We tried setting the NDLB-connectile-dysfunction=true in the dialplan,
but it doesnt seem to work.
Which leg should we set it on? And any reason why it wouldnt work?
Kind Regards
Jon Sch?pzinsky
We are having some problems with customer behind nat, where freeswitch
is responding to the contact headers address, which fails as the client
is using its internal IP and port information.
We tried setting the NDLB-connectile-dysfunction=true in the dialplan,
but it doesnt seem to work.
Which leg should we set it on? And any reason why it wouldnt work?
Kind Regards
Jon Sch?pzinsky