TLS-NAT issue arises due to the fact that it tries to contact on other port (TCP session) as far as my understanding. Changing contact header can sort this issue and i have done it setting up <variable name="sip-force-contact" value="NDLB-tls-connectile-dysfunction"/> for each directory (user). This helped and worked :) I suppose you should also have "ext-rtp-ip and "ext-sip-ip" = "nat-auto" in SIP profile. Cheeers! -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/FS-with-SSL-TLS-issues-tp7587736p7588069.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