<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">What was so wrong with adding ;transport=tls to the URI :P<div><br></div><div>/b</div><div><br><div><div>On May 30, 2011, at 1:05 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-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; ">You may want to check out my tls patch at:<br><br>it features the option for tls_only forcing only the encrypted port to<br>be open:<span class="Apple-converted-space"> </span><a href="http://jira.freeswitch.org/browse/FS-3071">http://jira.freeswitch.org/browse/FS-3071</a><span class="Apple-converted-space"> </span> in your dialplan<br>for calls you can set sip_secure_media to true to force it to SRTP.<br><br>~Mitch<br></span></blockquote></div><br></div></body></html>