28 Feb
2012
28 Feb
'12
3:08 a.m.
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