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