Exactly Opensips add lr=on and callee device transform it into lr;r2=on. my other devices (asterisk, avaya, etc ...) do not transform lr...
My Opensips version is version: opensips 1.6.4-2-tls (i386/freebsd) what is the difference between lr=on and lr;r2=on ? > So OpenSIPS adds "lr=on" but the callee device transform it into a > "lr"..... > > What version of opensips are you using? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > > On 08/24/2012 02:27 PM, [email protected] wrote: >> Hi Bogdan-Andrei, >> Thank you for your response. >> >> Yes I confirm in INVITE I have 2 RR with lr=on: >> >> <sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4> >> <sip:8.8.8.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4> >> >> and in 200OK I have 1 RR with just lr: >> >> <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> >> >> and in ACK I have 2 Route with lr: >> >> <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> >> >> >>> Hi Mickael, >>> >>> Can you confirm (for the failed call) that OpenSIPS added in INVITE RR >>> hdrs with "lr=on" param and in the 200 OK or ACK you get only "lr" >>> param >>> (with no value) ? >>> >>> Regards, >>> >>> Bogdan-Andrei Iancu >>> OpenSIPS Founder and Developer >>> http://www.opensips-solutions.com >>> >>> >>> On 08/24/2012 11:09 AM, [email protected] wrote: >>>> Hi list, >>>> I have a routing problem with my Opensips >>>> version: opensips 1.6.4-2-tls (i386/freebsd) >>>> >>>> Indeed Opensips is unable to route ACK packet to final destination >>>> (look >>>> attachement .txt). >>>> >>>> The only difference with a normal call (Call OK), it's Record-Route >>>> formating. Customer's device send 200OK with differents fields: >>>> >>>> >>>> Test device with the problem (call NOT OK): >>>> Ex: problem call = 1 field for 2 routes >>>> Extract from the customer 200OK >>>> >>>> Record-Route: >>>> <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> >>>> >>>> >>>> Test with another device (call OK) >>>> Ex: normal call = 2 fields for 2 routes >>>> Extract from the Customer 200OK >>>> >>>> Record-Route: >>>> <sip:8.8.8.8;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4> >>>> Record-Route: >>>> <sip:9.9.9.9;r2=on;lr=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4> >>>> >>>> My question is: This opensips version is able to work with 1 >>>> record-route >>>> field containing 2 informations ? >>>> >>>> Thanks in advance >>>> >>>> regards >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
