Sorry, I should have done it in the first place.
kamailio runs on port 5060
UAC : 5064
UAS : 5062
Having a better look, CANCEL request CSeq is set (wrongly) to 1 INVITE....
kamailio uses this for reply right ?
Note that CANCEL is relayed to UAS with CSeq 1 CANCEL.
12:03:48.874973 IP 127.0.0.1.5064 > 127.0.0.1.5060: SIP, length: 605
e.....@.@.:r.............e.yINVITE sip:si...@agent SIP/2.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Contact: sip:[email protected]: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 6109 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16
12:03:48.876993 IP 127.0.0.1.5060 > 127.0.0.1.5064: SIP, length: 329
e.....@.@.;~.............Q.dSIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk27-1;received=127.0.0.1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Server: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0
12:03:48.877115 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 757
e.....@[email protected] sip:si...@agent SIP/2.0
Record-Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0
Via: SIP/2.0/UDP 192.168.160.141:5064;received=127.0.0.1;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Contact: sip:[email protected]: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 6109 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11,16
12:03:48.982957 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 443
e.....@.@.;.................SIP/2.0 100 Trying
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0, SIP/2.0/UDP
192.168.160.141:5064;received=127.0.0.1;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Record-Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
12:03:49.024667 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 466
e.....@.@.:.................SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0, SIP/2.0/UDP
192.168.160.141:5064;received=127.0.0.1;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>;tag=29892SIPpTag01991
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Record-Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
12:03:49.025871 IP 127.0.0.1.5060 > 127.0.0.1.5064: SIP, length: 413
e.....@.@.;*................SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.160.141:5064;received=127.0.0.1;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>;tag=29892SIPpTag01991
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Record-Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
*12:03:49.581162 IP 127.0.0.1.5064 > 127.0.0.1.5060: SIP, length: 427
e.....@.@.;$................CANCEL sip:si...@agent SIP/2.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>;tag=29892SIPpTag01991
Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Contact: sip:[email protected]:5064
Max-Forwards: 70
Subject: Performance Test*
*12:03:49.631009 IP 127.0.0.1.5060 > 127.0.0.1.5064: SIP, length: 348
e.....@.@.;k.............d.wSIP/2.0 200 canceling
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk27-1;received=127.0.0.1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>;tag=29892SIPpTag01991
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Server: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0*
*12:03:49.631337 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 338
e.....@.@.;u.............Z.mCANCEL sip:si...@agent SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
Call-ID: 27-2905-192.168.160.141
To: sut <sip:si...@agent>
CSeq: 1 CANCEL
Max-Forwards: 70
User-Agent: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0*
12:03:49.642256 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 292
e...@..@....@.;..............,.?SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 CANCEL
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
12:03:49.653951 IP 127.0.0.1.5062 > 127.0.0.1.5060: SIP, length: 308
e.....@.@.;..............<.OSIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
12:03:49.675936 IP 127.0.0.1.5060 > 127.0.0.1.5062: SIP, length: 332
e.....@.@.;{.............T.gACK sip:si...@agent SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bK5d8d.942b65d7.0
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
Call-ID: 27-2905-192.168.160.141
To: sut <sip:si...@agent>
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: Kamailio (1.4.3-notls (i386/linux))
Content-Length: 0
12:03:49.676670 IP 127.0.0.1.5060 > 127.0.0.1.5064: SIP, length: 250
e.....@.@.;.................SIP/2.0 487 Request Terminated
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 INVITE
Contact: <sip:192.168.160.141:5062>
Content-Length: 0
12:03:49.677965 IP 127.0.0.1.5064 > 127.0.0.1.5060: SIP, length: 418
e.....@.@.;-................ACK sip:si...@agent SIP/2.0
Via: SIP/2.0/UDP 192.168.160.141:5064;branch=z9hG4bk27-1
From: sipp
<sip:[email protected]:5064>;tag=2905SIPpTag0927
To: sut <sip:si...@agent>
Route: <sip:127.0.0.1;lr=on;ftag=2905SIPpTag0927;did=ef8.d115a076>
Call-ID: 27-2905-192.168.160.141
CSeq: 1 ACK
Contact: sip:[email protected]:5064
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
Daniel-Constantin Mierla a écrit :
On 01/09/2009 12:44 PM, Aurelien Grimaud wrote:
When an INVITE is being Canceled, I receive a 200 canceling from
kamailio 1.4.3.
But the CSeq is set to the initial INVITE CSeq.
Should not it be CSeq:1 CANCEL ?
please paste the sip trace.
Daniel
_______________________________________________
Kamailio (OpenSER) - Devel mailing list
[email protected]
http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
