<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Mickael,<br>Do you have this in you script: <br>modparam("rr", "enable_full_lr", 1)<br><br>BR.<br>//Binan<br><br><br>--- On <b>Fri, 8/24/12, mickael@winlux.fr <i><mickael@winlux.fr></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: mickael@winlux.fr <mickael@winlux.fr><br>Subject: Re: [OpenSIPS-Users] [Re: Routing problem with Record-Route]<br>To: "OpenSIPS users mailling list" <users@lists.opensips.org><br>Date: Friday, August 24, 2012, 5:08 AM<br><br><div class="plainMail">Exactly Opensips add lr=on and callee device transform it into 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 using?<br>><br>> Regards,<br>><br>> Bogdan-Andrei Iancu<br>> OpenSIPS Founder and Developer<br>> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>><br>><br>> On 08/24/2012 02:27 PM, <a ymailto="mailto:mickael@winlux.fr" href="/mc/compose?to=mickael@winlux.fr">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>>> <sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>> <sip:8.8.8.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>><br>>> and in 200OK I have 1 RR with just lr:<br>>><br>>>
<sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>,<sip:8.8.8.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>><br>>> and in ACK I have 2 Route with lr:<br>>><br>>> <sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>> <sip:8.8.8.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>><br>>><br>>>> Hi Mickael,<br>>>><br>>>> Can you confirm (for the failed call) that OpenSIPS added in INVITE 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 href="http://www.opensips-solutions.com"
target="_blank">http://www.opensips-solutions.com</a><br>>>><br>>>><br>>>> On 08/24/2012 11:09 AM, <a ymailto="mailto:mickael@winlux.fr" href="/mc/compose?to=mickael@winlux.fr">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 destination<br>>>>> (look<br>>>>> attachement .txt).<br>>>>><br>>>>> The only difference with a normal call (Call OK), it's 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
200OK<br>>>>><br>>>>> Record-Route:<br>>>>> <sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>,<sip:9.9.9.9;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><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>>>>> <sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>>>> Record-Route:<br>>>>> <sip:9.9.9.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4><br>>>>><br>>>>> My question is: This opensips version is able to work with 1<br>>>>> record-route<br>>>>> field containing 2
informations ?<br>>>>><br>>>>> Thanks in advance<br>>>>><br>>>>> regards<br>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> Users mailing list<br>>>>> <a ymailto="mailto:Users@lists.opensips.org" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a><br>>>>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>>><br>>><br>>> _______________________________________________<br>>> Users mailing list<br>>> <a ymailto="mailto:Users@lists.opensips.org" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a><br>>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>>><br>><br>> _______________________________________________<br>> Users mailing list<br>> <a ymailto="mailto:Users@lists.opensips.org" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a><br>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>><br><br><br>_______________________________________________<br>Users mailing list<br><a ymailto="mailto:Users@lists.opensips.org" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></div></blockquote></td></tr></table>