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, [email protected] 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, [email protected]<[email protected]> wrote:
>>>
>>> From: [email protected]<[email protected]>
>>> Subject: Re: [OpenSIPS-Users] [Re: Routing problem with Record-Route]
>>> To: "OpenSIPS users mailling list"<[email protected]>
>>> 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, [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
>>> _______________________________________________
>>> 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
>
|Time | 9.9.9.9 (SIP provider) | 7.7.7.7(IP2 proxy)|
|
| | | 8.8.8.8(IP1 proxy)| |
6.6.6.6(Customer IPBX)|
|0,000 | INVITE SDP ype-101 ) | |
|
| |(5060) ------------------> (5060) | |
|
|0,000 | 100 Trying| | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|0,000 | 100 Giving a try | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|0,000 | 180 Ringing | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|0,000 | | | INVITE SDP
|SIP Request
| | | |(5060) ------------------>
(5060) |
|0,190 | | | 100 Trying|
|SIP Status
| | | |(5060) <------------------
(5060) |
|0,285 | | | 183 Session
Progress |SIP Status
| | | |(5060) <------------------
(5060) |
|0,285 | | | 180 Ringing
|SIP Status
| | | |(5060) <------------------
(5060) |
|0,285 | 180 Ringing | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|1,818 | | | !200 OK SDP
(g711A)! |SIP Status
| | | |(5060) <------------------
(5060) |
|1,818 | 200 OK SDP (g711A) | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|1,818 | !ACK! | | |
|SIP Request
| |(5060) ------------------> (5060) | |
|
|2,289 | 200 OK SDP (g711A) | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|2,289 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|2,289 | ACK | | |
|SIP Request
| |(5060) ------------------> (5060) | |
|
|3,242 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|3,338 | ACK | | |
|SIP Request
| |(5060) ------------------> (5060) | |
|
|3,338 | 200 OK SDP (g711A) | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|5,277 | 200 OK SDP (g711A) | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|5,277 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|5,278 | ACK | | |
|SIP Request
| |(5060) ------------------> (5060) | |
|
|9,245 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|13,259 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|17,336 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|21,304 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|25,243 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|29,291 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|33,328 | | | 200 OK SDP (g711A)
|SIP Status
| | | |(5060) <------------------
(5060) |
|60,716 | BYE | | |
|SIP Request
| |(5060) ------------------> (5060) | |
|
|60,716 | 404 Not here | |
|SIP Status
| |(5060) <------------------ (5060) | |
|
|239,836 | BYE | | |
|SIP Request
| |(5060) <------------------ (5060) | |
|
|239,836 | | | BYE |
|SIP Request
| | | |(5060) ------------------>
(5060) |
|239,837 | 481 Call Leg/Transaction Does Not Exist |
| |SIP Status
| |(5060) ------------------> (5060) | |
|
|239,931 | | | 481
Call/Transaction Does Not Exist |SIP Status
| | | |(5060) <------------------
(5060) |
ACK from provider, but Opensips no resend ACK to Cutomer IPBX
ACK sip:[email protected]:5060 SIP/2.0
From: <sip:[email protected]>;tag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102
To: <sip:[email protected]>;tag=407A
Call-ID: [email protected]
CSeq: 1 ACK
Via: SIP/2.0/UDP 9.9.9.9:5060;branch=z9hG4bK-16323bb-50237eff-8d49ded9-37571fbc
Max-Forwards: 69
Contact: <sip:9.9.9.9:5060;maddr=9.9.9.9;transport=udp>
Route:
<sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>
Route:
<sip:7.7.7.7;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>
Content-Length: 0
200 ok From customer IPBX
SIP/2.0 200 OK
Accept: application/sdp,application/dtmf-relay
Allow:
PRACK,ACK,CANCEL,BYE,SUBSCRIBE,NOTIFY,INVITE,REFER,OPTIONS,INFO,UPDATE,REGISTER
Call-ID: [email protected]
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
CSeq: 1 INVITE
From: <sip:[email protected]>;tag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102
Privacy: none
Record-Route:
<sip:7.7.7.7;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>,<sip:8.8.8.8;lr;r2=on;ftag=c97942d9-13c4-50237efd-8d49d7d0-5fb68102;xyz=3a2.86da31c4>
To: <sip:[email protected]>;tag=407A
Via: SIP/2.0/UDP
7.7.7.7;received=7.7.7.7;branch=z9hG4bKad65.c86bae22.0,SIP/2.0/UDP
9.9.9.9:5060;branch=z9hG4bK-1632372-50237efd-8d49d7d0-258fba13
Content-Length: 178
v=0
o=6.6.6.6 3160829095 3160829096 IN IP4 6.6.6.6
s=Session SDP
c=IN IP4 6.6.6.6
t=0 0
m=audio 16390 RTP/AVP 8
a=rtpmap:8 PCMA/8000
a=ptime:20_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
