<p>That function is <em>exactly</em> what I want! :)</p>
<p>Also, it makes it possible to prefer tls always, because even if sips uri scheme takes care of tls, the RFC there <em>requires</em> every step to be tls, which might not always be possible.</p>
<p>There should be nothing in the way of always preferring the secure route if its available.</p>
<p>For now we can just use the force_send_socket() function for stuff that needs to exit over tcp.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/issues/420#issuecomment-77534748">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFOciUwCxjczlgov5GSUYJJT_dNf73seks5nyXLvgaJpZM4Dn7ta.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
<link itemprop="url" href="https://github.com/OpenSIPS/opensips/issues/420#issuecomment-77534748"></link>
<meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>