[Kamailio-Devel] [tm] t_lookupOriginalT : cannot find matching INVITE for CANCEL because of display name

Aurelien Grimaud gstelzz at yahoo.fr
Tue Jan 20 14:47:12 CET 2009


Hi,
it seems that I have a problem with finding initial INVITE when request 
is CANCELED.
sipp uac (192.168.160.141:5064) contact a uas (192.168.160.23:6075) 
through kamailio 1.4.3 (192.168.160.141:5060)

The request is CANCELED by uac.
But From field is taken from 180 reply and is trhough slightly different 
from initial one.
The display name is quoted and whitespace is missing.

This makes the t_lookupOriginalT fails .... attached log from kamailio 
(check the end)

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
Subject: Performance Test
Content-Type: application/sdp
Content-Length:   200

v=0
o=user1 53655765 2353687637 IN IP4 192.168.160.141
s=-
c=IN IP4 192.168.160.141
t=0 0
m=audio 6001 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16

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
Subject: Performance Test
Content-Type: application/sdp
Content-Length:   200

v=0
o=user1 53655765 2353687637 IN IP4 192.168.160.141
s=-
c=IN IP4 192.168.160.141
t=0 0
m=audio 6001 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16

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
Content-Type: application/sdp
User-Agent: svi
Content-Length: 225

v=0
o=sip:1-16122-192.168.160.141 at 192.168.160.141:5064 1232458155 1232458155 
IN IP4 127.0.0.1
s=frtsip
t=0 0
m=audio 35792 RTP/AVP 8 101
c=IN IP4 192.168.160.141
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000

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
Content-Type: application/sdp
User-Agent: svi
Content-Length: 225

v=0
o=sip:1-16122-192.168.160.141 at 192.168.160.141:5064 1232458155 1232458155 
IN IP4 127.0.0.1
s=frtsip
t=0 0
m=audio 35792 RTP/AVP 8 101
c=IN IP4 192.168.160.141
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000

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



-------------- next part --------------
A non-text attachment was scrubbed...
Name: openser.5060.log.zip
Type: application/x-zip-compressed
Size: 4551 bytes
Desc: not available
Url : http://lists.kamailio.org/pipermail/devel/attachments/20090120/ccf855dc/attachment.bin 


More information about the Devel mailing list