<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hi Ben,<br>
<br>
As I mentioned in different thread, TH is not compatible with the
RR mechanism. If you do TH, your OpenSIPS will act as and end
point (from SIP perspective), so there will be no Route/RR headers
at all. So no need to do loose_route or so. You just do TH
matching for the sequential requests and nothing more.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 22.07.2016 16:48, Newlin, Ben wrote:<br>
</div>
<blockquote cite="mid:99A0B3CF-E6DF-46B3-BB9F-D953F0D043B3@inin.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
        {font-family:Arial;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:Calibri;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:Calibri;
        color:windowtext;}
span.msoIns
        {mso-style-type:export-only;
        mso-style-name:"";
        text-decoration:underline;
        color:teal;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:Calibri;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I am using
the Dialog module with topology_hiding() in my server and I
have a need to Record-Route the call on my server as I am
advertising a different address than I am listening on. I
have found what I believe is an inconsistency in the
handling of Record-Route within the Dialog topology_hiding
functionality. The topology_hiding isn’t a true B2BUA, but
it does set up different parameters for the incoming UAC and
outgoing UAS sides of the call for the Via headers,
Record-Route and Route headers, and the Contact header(s).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The problem
is that the record_route() and loose_route() functions
operate on different sides of the call. The record_route()
function will only add a Record-Route header to the outgoing
UAS side of the call. And since the record_route() function
cannot be called from onreply_route, but is no way to add a
Record-Route header to the UAC side of the call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">On the other
hand, the loose_route() function only operates on the
incoming UAC side of the call and there is no way to perform
loose_route() on the UAS side of the call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">So there is
a situation where Record-Route headers can only be added on
the outgoing UAS side, but the associated Route headers can
only be removed on the incoming UAC side (where they won’t
exist since they can’t be added) and any added headers on
the UAS side cannot be processed properly due to the lack of
loose_route.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I can
provide further information if this is unclear. It should be
easily reproducible by attempting to use record_route in a
topology_hiding scenario. The route is added to the outbound
leg, but is not removed by loose_route so the message is
looped back every time.<o:p></o:p></span></p>
<div>
<p class="MsoNormal"
style="line-height:16.8pt;background:white"><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="line-height:16.8pt;background:white"><b><span
style="font-size:10.0pt;font-family:Arial;color:#155570">Ben
Newlin</span></b><b><span
style="font-size:10.0pt;font-family:Arial;color:#666666"> </span></b><span
style="font-size:10.0pt;font-family:Arial;color:#666666">|
Sr Voice Network Engineer, PureCloud</span><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="line-height:16.8pt;background:white"><span
style="font-size:10.0pt;font-family:Arial;color:#666666">phone
& fax +1.317.957.1009 | </span><span
style="font-size:10.0pt;font-family:Arial;color:#0585A7"><a class="moz-txt-link-abbreviated" href="mailto:ben.newlin@inin.com">ben.newlin@inin.com</a> </span><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="line-height:16.8pt;background:white"><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><img
moz-do-not-send="true" id="_x0000_i1025"
src="http://cdn.inin.com/baseimages/ININ_Logo_Signature.png"
height="21" width="196"></span><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="line-height:12.0pt;background:white"><span
style="font-size:10.0pt;font-family:Arial;color:#0585A7"><a
moz-do-not-send="true" href="http://www.inin.com/"><span
style="color:#0585A7;text-decoration:none"><a class="moz-txt-link-abbreviated" href="http://www.inin.com">www.inin.com</a></span></a></span><span
style="font-size:9.0pt;font-family:Arial;color:#666666"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>