[OpenSIPS-Users] [Re: Routing problem with Record-Route]

mickael at winlux.fr mickael at winlux.fr
Mon Aug 27 16:58:58 CEST 2012


Hi
in attachement call flow and ACK from provider (this ACK is not resend by
opensips to customer IPBX).

Thanks

> Hi,
>
> Please post the ACK message your opensips proxy gets, and also the
> outbound ACK request (leaving your opensips) - Include also the net
> layer info (like src ip and port) - feel free to masquerade the IPs, but
> do it consistently,
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
>
> On 08/27/2012 09:17 AM, mickael at winlux.fr wrote:
>> Hi,
>> do you think this may be the cause of my routing ACK problem ?
>>
>>> Hi,
>>> loose route parameter lr , which can be present in sip or sips
>>> Record-Route and Route URIs to indicate that the proxy server
>>> identified
>>> by the URI supports loose routing.
>>>
>>>
>>> RFC 3261 explains the "lr" parameter as just ";lr", not lr=on. This
>>> brokes
>>> some UAs which add =on to the "lr".  opensips adds=on  to be compatible
>>> with these UAs
>>>
>>>
>>> //Binan.
>>>
>>>
>>> --- On Fri, 8/24/12, mickael at winlux.fr<mickael at winlux.fr>  wrote:
>>>
>>> From: mickael at winlux.fr<mickael at winlux.fr>
>>> Subject: Re: [OpenSIPS-Users] [Re:  Routing problem with Record-Route]
>>> To: "OpenSIPS users mailling list"<users at lists.opensips.org>
>>> Date: Friday, August 24, 2012, 5:08 AM
>>>
>>> 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, mickael at winlux.fr 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, mickael at winlux.fr 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
>>>>>>> Users at lists.opensips.org
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>> _______________________________________________
>>>> Users mailing
>>>   list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: trace_call_prob.txt
URL: <http://lists.opensips.org/pipermail/users/attachments/20120827/a262edf5/attachment.txt>


More information about the Users mailing list