So this is the root cause of FS-3877? (Reuse TCP connection for both directions) It is not a FS issue? - Silvije On 2/28/12 04:08 AM, Brian West wrote:
The problem that I have seen is the client says one port in the contact but uses a different one.
So if the client wouldn't lie we would always reuse the same connection. Right now Polycom is broken you'll see it auto-nat-2.0 by default if I recall.
/b
On Feb 27, 2012, at 7:51 PM, Mitch Capper wrote:
I have no problem running freeswitch in TLS only mode, if you are experiencing the ability to make calls but not receive them it could be a NAT issue. Freeswitch needs the ability to connect back with a new TCP connection to the client for incoming calls to work with TLS registration. If there is a firewall or nat between the client and FS this could cause problems.
~Mitch
_________________________________________________________________________ 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