<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The problem that I have seen is the client says one port in the contact but uses a different one. <div><br></div><div>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.</div><div><br></div><div>/b</div><div><br><div><div>On Feb 27, 2012, at 7:51 PM, Mitch Capper wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I have no problem running freeswitch in TLS only mode, if you are<br>experiencing the ability to make calls but not receive them it could<br>be a NAT issue. Freeswitch needs the ability to connect back with a<br>new TCP connection to the client for incoming calls to work with TLS<br>registration. If there is a firewall or nat between the client and<br>FS this could cause problems.<br><br><br>~Mitch<br></span></blockquote></div><br></div></body></html>