<div dir="ltr"><p class="MsoNormal">Is there any way to specify the full contact header in a UA
profile that the SIP stack will use when formulating messages?
Specifically, have it use "sips" instead of "sip" as
the protocol scheme? </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I'm trying to establish an INVITE dialog between 2
FreeSWITCH servers using a client authenticated TLS handshake.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To accomplish this, I've created 2 UA profiles on both
servers - one to fulfill the role of the UAC (i.e. tls-uac.xml) and one to
implement the UAS (i.e. tls-uas.xml). Here are the relevant parameters
from both profiles:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">tls-uac.xml:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="sip-port" value="5081"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls" value="true"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-only" value="true"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-sip-port" value="5082"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-cert-dir" value="$${base_dir}/conf/tls/uac"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">tls-uas.xml:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="sip-port" value="5081"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls" value="true"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-only" value="true"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-sip-port" value="5081"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> <param
name="tls-cert-dir" value="$${base_dir}/conf/tls/uas"/></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The problem already starts when "tls-uac" sends a
non-secure SIP URI in the contact header of its initial INVITE request (i.e. <a href="http://sip:mod_sofia@10.191.210.150:5081">sip:mod_sofia@10.191.210.150:5081</a>).
But the more immediate issue is that "tls-uas" also responds
with a non-secure SIP URI in the contact header of its final response (i.e. <a href="sip:14086805675@10.191.210.151:5081;transport=udp">sip:14086805675@10.191.210.151:5081;transport=udp</a>).
This causes "tls-uac" to send its ACK to the right port number
(i.e. 5081) but on the wrong transport (i.e. UDP instead of TCP/TLS).</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I've seen in the FS documentation that there are ways to
manipulate the contact header through the dial plan, but I'd really prefer not
to do it this way. Any suggestions?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks</p><p class="MsoNormal">JP</p></div>