NDLB-connectile-dysfunction=true with a non directory user
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
Are you sure you can't fix it on the client, eg by enabling STUN? If not, try this in dialplan: <action application="set" data="sip-force-contact=NDLB-connectile-dysfunction"/> However it may be that the variable needs to be set on the call before it hits the dialplan, if so this won't help. Test it and see. -Steve On 11 April 2014 14:38, Jon Schøpzinsky <jos@firstcom.dk> wrote:
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
_________________________________________________________________________ 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
Maybe better solution is also to enable rport on the device, this will likely fix the problem for you. Mike On Apr 11, 2014, at 9:38 AM, Jon Schøpzinsky <jos@firstcom.dk> wrote:
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
Our problem is a very reluctant customer, that wont change anything on their side, and dont really know how their system works, but I will try setting the variable from the dialplan. Thank you :)
Michael Jerris <mailto:mike@jerris.com> 14 Apr 2014 14:36 Maybe better solution is also to enable rport on the device, this will likely fix the problem for you.
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.
Jon Schøpzinsky <mailto:jos@firstcom.dk> 11 Apr 2014 15:38 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
participants (3)
-
Jon Schøpzinsky
-
Michael Jerris
-
Steven Ayre