[Kamailio-Devel] [ openser-Bugs-2523849 ] tm : t_lookupOriginal : display name makes match fails

[SourceForge.net]

Bugs item #2523849, was opened at 2009-01-20 15:54
Message generated for change (Comment added) made by ibc_sf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2523849&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Aurelien Grimaud (gstelzz)
Assigned to: Nobody/Anonymous (nobody)
Summary: tm : t_lookupOriginal : display name makes match fails

Initial Comment:
if the uas changes the display name in the from field, and the uac uses this new from field (only display name change) for CANCEL, then tm module cannot find the initial INVITE.

Here the from field set by uac is
sipp <sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091

but reply 1xx returns
"sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091

t_lookupOriginal fails because the headers does not have the same length  (no ws but 2 quotes for second one)


14:29:15.297598 IP 192.168.160.141.5064 > 192.168.160.141.5060: SIP, length: 608
E..|.. at .@.v..............h..INVITE sip:999005 at rtpfc9 SIP/2.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
From: sipp <sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
To: sut <sip:999005 at rtpfc9>
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE
Contact: sip:sipp at 192.168.160.141:5064
Max-Forwards: 70
Expires: 180

14:29:15.300870 IP 192.168.160.141.5060 > 192.168.160.141.5064: SIP, length: 311
E..S.. at .@.w&.............?..SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
From: sipp <sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
To: sut <sip:999005 at rtpfc9>
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE
Server: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0


14:29:15.301208 IP 192.168.160.141.5060 > 192.168.160.23.6075: SIP, length: 753
E..
... at .@.u.................INVITE sip:999005 at rtpfc9 SIP/2.0
Record-Route: <sip:192.168.160.141;lr=on;ftag=16122SIPpTag091;did=2e1.27e5e684>
Via: SIP/2.0/UDP 192.168.160.141;branch=z9hG4bK4773.2365d4b7.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
From: sipp <sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
To: sut <sip:999005 at rtpfc9>
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE
Contact: sip:sipp at 192.168.160.141:5064
Max-Forwards: 69
Expires: 180

14:29:15.328240 IP 192.168.160.23.6075 > 192.168.160.141.5060: SIP, length: 370
E..... at .@.u..............z..SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.160.141;branch=z9hG4bK4773.2365d4b7.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
To: "sut"<sip:999005 at rtpfc9>;tag=082ea729
From: "sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE
User-Agent: svi
Content-Length: 0


14:29:15.328360 IP 192.168.160.23.6075 > 192.168.160.141.5060: SIP, length: 750
E..
... at .@.t5..............%.SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.160.141;branch=z9hG4bK4773.2365d4b7.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
Record-Route: <sip:192.168.160.141;lr;ftag=16122SIPpTag091;did=2e1.27e5e684>
Contact: <sip:999005 at 192.168.160.23:6075>
To: "sut"<sip:999005 at rtpfc9>;tag=082ea729
From: "sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE

14:29:15.329332 IP 192.168.160.141.5060 > 192.168.160.141.5064: SIP, length: 686
E..... at .@.u................3SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
Record-Route: <sip:192.168.160.141;lr;ftag=16122SIPpTag091;did=2e1.27e5e684>
Contact: <sip:999005 at 192.168.160.23:6075>
To: "sut"<sip:999005 at rtpfc9>;tag=082ea729
From: "sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
Call-ID: 1-16122-192.168.160.141
CSeq: 1 INVITE

14:29:17.756022 IP 192.168.160.141.5064 > 192.168.160.141.5060: SIP, length: 426
E..... at .@.v................/CANCEL sip:999005 at rtpfc9 SIP/2.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
From: "sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
To: "sut"<sip:999005 at rtpfc9>;tag=082ea729
Route: <sip:192.168.160.141;lr;ftag=16122SIPpTag091;did=2e1.27e5e684>
Call-ID: 1-16122-192.168.160.141
CSeq: 1 CANCEL
Contact: sip:sipp at 192.168.160.141:5064
Max-Forwards: 70
Subject: Performance Test


14:29:17.762596 IP 192.168.160.141.5060 > 192.168.160.141.5064: SIP, length: 347
E..w.. at .@.w..............c..SIP/2.0 476 Unresolvable destination (476/TM)
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk1-1
From: "sipp"<sip:1-16122-192.168.160.141 at 192.168.160.141:5064>;tag=16122SIPpTag091
To: "sut"<sip:999005 at rtpfc9>;tag=082ea729
Call-ID: 1-16122-192.168.160.141
CSeq: 1 CANCEL
Server: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0 


----------------------------------------------------------------------

>Comment By: Iñaki Baz (ibc_sf)
Date: 2009-01-20 20:56

Message:
The UAC is not using the proper RFC 3261 magic cookie, so pre-RFC 3261
transaction matching is being permormed on Kamailio. This requires From
header matching the previous From header. So the bug is invalid.

----------------------------------------------------------------------

Comment By: Iñaki Baz (ibc_sf)
Date: 2009-01-20 15:59

Message:
I don't understand why Kamailio matches the From header. IMHO the only
matching should be done against the Via branch parameter.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2523849&group_id=139143