<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Bogdan,<br><br>i see in the opensips Docs the definition of loose_route() function: <br><br>" The function performs routing of SIP requests which contain a route
set. The name is a little bit confusing, as <b>this function also routes
requests which are in the “<span class="yiv1001852899quote">strict router</span>” format.
"</b><br><br>so Does this function do the strict routing also ? according to which chapter in RFC this routing belong ?<br><br>regards<br><br>--- On <b>Tue, 8/28/12, Bogdan-Andrei Iancu <i><bogdan@opensips.org></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Bogdan-Andrei Iancu <bogdan@opensips.org><br>Subject: Re: [OpenSIPS-Users] [Re: Routing problem with Record-Route]<br>To: "OpenSIPS users mailling list" <users@lists.opensips.org><br>Cc: "Binan AL Halabi" <binanalhalabi@yahoo.com><br>Date: Tuesday, August 28, 2012, 7:29 AM<br><br><div id="yiv320135327">
<div>
<tt>Hi,<br>
<br>
That is not true - OpenSIPS acts all the time as a loose router.
The param you mentioned simply changes on how the "loose router"
label should be advertised : (1) "lr" or (2) "lr=on" - but both do
mean a loose router.<br>
<br>
Regards,<br>
</tt>
<pre class="yiv320135327moz-signature">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a rel="nofollow" class="yiv320135327moz-txt-link-freetext" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 08/28/2012 03:46 PM, Binan AL Halabi wrote:
<blockquote type="cite">
<table cellpadding="0" cellspacing="0" border="0">
<tbody>
<tr>
<td style="font:inherit;" valign="top">Hi , <br>
the statment *modparam("rr", "enable_full_lr", 1)* in the
script lets opensips uses lr=on instead of just ;lr to
work as loose router, so it behaves as strict router where
it should be loose router in fail case, since it detects
only ;lr in messages. <br>
<br>
<br>
--- On <b>Mon, 8/27/12, Bogdan-Andrei Iancu <i><a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E" ymailto="mailto:bogdan@opensips.org" target="_blank" href="/mc/compose?to=bogdan@opensips.org"><bogdan@opensips.org></a></i></b>
wrote:<br>
<blockquote style="border-left:2px solid rgb(16, 16,
255);margin-left:5px;padding-left:5px;"><br>
From: Bogdan-Andrei Iancu <a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E" ymailto="mailto:bogdan@opensips.org" target="_blank" href="/mc/compose?to=bogdan@opensips.org"><bogdan@opensips.org></a><br>
Subject: Re: [OpenSIPS-Users] [Re: Routing problem with
Record-Route]<br>
To: <a rel="nofollow" class="yiv320135327moz-txt-link-abbreviated" ymailto="mailto:mickael@winlux.fr" target="_blank" href="/mc/compose?to=mickael@winlux.fr">mickael@winlux.fr</a><br>
Cc: "OpenSIPS users mailling list"
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E" ymailto="mailto:users@lists.opensips.org" target="_blank" href="/mc/compose?to=users@lists.opensips.org"><users@lists.opensips.org></a><br>
Date: Monday, August 27, 2012, 8:48 AM<br>
<br>
<div class="yiv320135327plainMail">As the next destination should be
6.6.6.6, some stupid questions:<br>
<br>
1) is 6.6.6.6 configured in domain module or as
"alias" ?<br>
<br>
2) have you check to loopback interface ? maybe the
ACK is spiraling <br>
over there.<br>
<br>
Also, try to reproduce the ACK case, but enable full
debug in script for <br>
the loose_route() function:<br>
if (is_method=="ACK") setdebug(6);<br>
<br>
And post the output of opensips - this will give some
clue on what it is <br>
doing.<br>
<br>
Regards,<br>
<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br>
<br>
<br>
On 08/27/2012 06:41 PM, <a rel="nofollow">mickael@winlux.fr</a>
wrote:<br>
> 7.7.7.7 and 8.8.8.8 are both from the same
instance of opensips (same<br>
> server 2 IPs interfaces).<br>
><br>
> in opensips log, no error, just no forwarding to
customer IPBX.<br>
> but tomorrow I'll test with other debug option.<br>
><br>
> Thanks<br>
><br>
>> The 7.7.7.7 and 8.8.8.8 IPs are both from the
same instance of opensips<br>
>> (doing interface exchange) or there are 2
different SIP entities ?<br>
>><br>
>> Also, do you see any errors in the logs when
the ACK is handled ?<br>
>><br>
>> regards,<br>
>><br>
>> Bogdan-Andrei Iancu<br>
>> OpenSIPS Founder and Developer<br>
>> <a rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br>
>><br>
>><br>
>> On 08/27/2012 05:58 PM, <a rel="nofollow">mickael@winlux.fr</a>
wrote:<br>
>>> Hi<br>
>>> in attachement call flow and ACK from
provider (this ACK is not resend<br>
>>> by<br>
>>> opensips to customer IPBX).<br>
>>><br>
>>> Thanks<br>
>>><br>
>>>> Hi,<br>
>>>><br>
>>>> Please post the ACK message your
opensips proxy gets, and also the<br>
>>>> outbound ACK request (leaving your
opensips) - Include also the net<br>
>>>> layer info (like src ip and port) -
feel free to masquerade the IPs,<br>
>>>> but<br>
>>>> do it consistently,<br>
>>>><br>
>>>> Regards,<br>
>>>><br>
>>>> Bogdan-Andrei Iancu<br>
>>>> OpenSIPS Founder and Developer<br>
>>>> <a rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br>
>>>><br>
>>>><br>
>>>> On 08/27/2012 09:17 AM, <a rel="nofollow">mickael@winlux.fr</a>
wrote:<br>
>>>>> Hi,<br>
>>>>> do you think this may be the
cause of my routing ACK problem ?<br>
>>>>><br>
>>>>>> Hi,<br>
>>>>>> loose route parameter lr ,
which can be present in sip or sips<br>
>>>>>> Record-Route and Route URIs
to indicate that the proxy server<br>
>>>>>> identified<br>
>>>>>> by the URI supports loose
routing.<br>
>>>>>><br>
>>>>>><br>
>>>>>> RFC 3261 explains the "lr"
parameter as just ";lr", not lr=on. This<br>
>>>>>> brokes<br>
>>>>>> some UAs which add =on to the
"lr". opensips adds=on to be<br>
>>>>>> compatible<br>
>>>>>> with these UAs<br>
>>>>>><br>
>>>>>><br>
>>>>>> //Binan.<br>
>>>>>><br>
>>>>>><br>
>>>>>> --- On Fri, 8/24/12, <a rel="nofollow">mickael@winlux.fr</a><<a rel="nofollow">mickael@winlux.fr</a>>
wrote:<br>
>>>>>><br>
>>>>>> From: <a rel="nofollow">mickael@winlux.fr</a><<a rel="nofollow">mickael@winlux.fr</a>><br>
>>>>>> Subject: Re: [OpenSIPS-Users]
[Re: Routing problem with<br>
>>>>>> Record-Route]<br>
>>>>>> To: "OpenSIPS users mailling
list"<<a rel="nofollow">users@lists.opensips.org</a>><br>
>>>>>> Date: Friday, August 24,
2012, 5:08 AM<br>
>>>>>><br>
>>>>>> Exactly Opensips add lr=on
and callee device transform it into<br>
>>>>>> lr;r2=on.<br>
>>>>>><br>
>>>>>> my other devices (asterisk,
avaya, etc ...) do not transform lr...<br>
>>>>>><br>
>>>>>> My Opensips version is
version: opensips 1.6.4-2-tls (i386/freebsd)<br>
>>>>>><br>
>>>>>> what is the difference
between lr=on and lr;r2=on ?<br>
>>>>>><br>
>>>>>>> So OpenSIPS adds "lr=on"
but the callee device transform it into a<br>
>>>>>>> "lr".....<br>
>>>>>>><br>
>>>>>>> What version of opensips
are you<br>
>>>>>> using?<br>
>>>>>>> Regards,<br>
>>>>>>><br>
>>>>>>> Bogdan-Andrei Iancu<br>
>>>>>>> OpenSIPS Founder and
Developer<br>
>>>>>>> <a rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On 08/24/2012 02:27 PM, <a rel="nofollow">mickael@winlux.fr</a>
wrote:<br>
>>>>>>>> Hi Bogdan-Andrei,<br>
>>>>>>>> Thank you for your
response.<br>
>>>>>>>><br>
>>>>>>>> Yes I confirm in
INVITE I have 2 RR with lr=on:<br>
>>>>>>>><br>
>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>><br>
>>>>>>>> and in 200OK I have 1
RR with just lr:<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a>,<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>> and in ACK I have 2
Route with lr:<br>
>>>>>>>><br>
>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>>> Hi Mickael,<br>
>>>>>>>>><br>
>>>>>>>>> Can you confirm
(for the failed call) that OpenSIPS added in<br>
>>>>>>>>> INVITE<br>
>>>>>>>>> RR<br>
>>>>>>>>> hdrs with "lr=on"
param and in the 200 OK or ACK you get only "lr"<br>
>>>>>>>>> param<br>
>>>>>>>>> (with no value) ?<br>
>>>>>>>>><br>
>>>>>>>>> Regards,<br>
>>>>>>>>><br>
>>>>>>>>> Bogdan-Andrei
Iancu<br>
>>>>>>>>> OpenSIPS Founder
and Developer<br>
>>>>>>>>> <a rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> On 08/24/2012
11:09 AM, <a rel="nofollow">mickael@winlux.fr</a>
wrote:<br>
>>>>>>>>>> Hi list,<br>
>>>>>>>>>> I have a
routing problem with my Opensips<br>
>>>>>>>>>> version:
opensips 1.6.4-2-tls (i386/freebsd)<br>
>>>>>>>>>><br>
>>>>>>>>>> Indeed
Opensips is unable to route ACK packet to final<br>
>>>>>>>>>> destination<br>
>>>>>>>>>> (look<br>
>>>>>>>>>> attachement
.txt).<br>
>>>>>>>>>><br>
>>>>>>>>>> The only
difference with a normal call (Call OK), it's<br>
>>>>>>>>>> Record-Route<br>
>>>>>>>>>> formating.
Customer's device send 200OK with differents fields:<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> Test device
with the problem (call NOT OK):<br>
>>>>>>>>>> Ex: problem
call = 1 field for 2 routes<br>
>>>>>>>>>> Extract from
the customer<br>
>>>>>> 200OK<br>
>>>>>>>>>> Record-Route:<br>
>>>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a>,<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:9.9.9.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> Test with
another device (call OK)<br>
>>>>>>>>>> Ex: normal
call = 2 fields for 2 routes<br>
>>>>>>>>>> Extract from
the Customer 200OK<br>
>>>>>>>>>><br>
>>>>>>>>>> Record-Route:<br>
>>>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>>>> Record-Route:<br>
>>>>>>>>>>
<a rel="nofollow" class="yiv320135327moz-txt-link-rfc2396E"><sip:9.9.9.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4></a><br>
>>>>>>>>>><br>
>>>>>>>>>> My question
is: This opensips version is able to work with 1<br>
>>>>>>>>>> record-route<br>
>>>>>>>>>> field
containing 2<br>
>>>>>> informations ?<br>
>>>>>>>>>> Thanks in
advance<br>
>>>>>>>>>><br>
>>>>>>>>>> regards<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>>
_______________________________________________<br>
>>>>>>>>>> Users mailing
list<br>
>>>>>>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>>>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>>>>>
_______________________________________________<br>
>>>>>>>> Users mailing list<br>
>>>>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>>>>><br>
>>>>>>>
_______________________________________________<br>
>>>>>>> Users mailing<br>
>>>>>> list<br>
>>>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>>>><br>
>>>>>>
_______________________________________________<br>
>>>>>> Users mailing list<br>
>>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>>>
_______________________________________________<br>
>>>>>> Users mailing list<br>
>>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>>><br>
>>>>>
_______________________________________________<br>
>>>>> Users mailing list<br>
>>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>>><br>
>>>>
_______________________________________________<br>
>>>> Users mailing list<br>
>>>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>>>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>>>><br>
>>
_______________________________________________<br>
>> Users mailing list<br>
>> <a rel="nofollow">Users@lists.opensips.org</a><br>
>> <a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>><br>
><br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a rel="nofollow">Users@lists.opensips.org</a><br>
<a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</blockquote>
</td>
</tr>
</tbody>
</table>
<pre><fieldset class="yiv320135327mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a rel="nofollow" class="yiv320135327moz-txt-link-abbreviated" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a>
<a rel="nofollow" class="yiv320135327moz-txt-link-freetext" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
</div></blockquote></td></tr></table>