Hello,

I am using the X-Lite 2.0 build 1086 with ser 0.8.11 and noticed a strange behaviour regarding the CANCEL method. Whenever the X-lite sends a CANCEL to a Cisco gateway after having received a 183 Session Progress, the gateway sends back a 481 Call Leg/Transaction Does Not Exist. This way, the call is not being canceled as the called phone will keep ringing. If no 183 Session Progress is received, the call is normally canceled.

Any ideas on this issue? Has anyone has experienced the same problems?

Thanks,

Chuck Ramirez

####################

INVITE sip:555199434103@200.229.101.9:5060 SIP/2.0

Record-Route: <sip:99434103@200.229.119.20;ftag=760418566;lr>

Via: SIP/2.0/UDP 200.229.100.20;branch=z9hG4bK4851.71c4b895.2

Via: SIP/2.0/UDP 200.229.100.18:5060

Via: SIP/2.0/UDP 200.176.103.227:54708

Via: SIP/2.0/UDP 10.0.0.25:5060;rport;branch=z9hG4bKEF01CC8838FF465AB1FC49BFADEC2843

Record-Route: <sip:99434103@200.229.100.18:5060>

From: 55519 <sip:55519@myproxy.com>;tag=760418566

To: <sip:99434103@myproxy.com>

Call-ID: E43869EB-1F92-4FE4-A73B-3EAAEEE5B6EE@10.0.0.25

CSeq: 53730 INVITE

Contact: <sip:55519@200.229.100.18:5060>

Authorization: Digest username="55519", realm="myproxy.com", nonce="3fc226f57eab90d318703f3913f8d12bdfdf27fd", uri="sip:99434103@myproxy.com", response="2058c7da78fea8ed4b6c894d460fce71"

max-forwards: 69

user-agent: X-Lite build 1086

Content-Type: application/sdp

Content-Length: 238

v=0

o=55519 1033766 1033766 IN IP4 10.0.0.25

s=X-Lite

c=IN IP4 200.229.100.18

t=0 0

m=audio 7074 RTP/AVP 3 0 8 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 200.229.100.20;branch=z9hG4bK4851.71c4b895.2,SIP/2.0/UDP 200.229.100.18:5060,SIP/2.0/UDP 200.176.103.227:54708,SIP/2.0/UDP 10.0.0.25:5060;rport;branch=z9hG4bKEF01CC8838FF465AB1FC49BFADEC2843

From: 55519 <sip:55519@myproxy.com>;tag=760418566

To: <sip:99434103@myproxy.com>;tag=C221BDBC-46A

Date: Mon, 24 Nov 2003 15:37:46 GMT

Call-ID: E43869EB-1F92-4FE4-A73B-3EAAEEE5B6EE@10.0.0.25

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 53730 INVITE

Content-Length: 0

SIP/2.0 100 Trying

From: 55519 <sip:55519@myproxy.com>;tag=760418566

To: <sip:99434103@myproxy.com>;tag=C221BDBC-46A

Date: Mon, 24 Nov 2003 15:37:46 GMT

Call-ID: E43869EB-1F92-4FE4-A73B-3EAAEEE5B6EE@10.0.0.25

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 53730 INVITE

Content-Length: 0

CANCEL sip:555199434103@200.229.101.9:5060 SIP/2.0

Max-Forwards: 10

Record-Route: <sip:99434103@200.229.100.20;ftag=760418566;lr>

Via: SIP/2.0/UDP 200.229.100.20;branch=z9hG4bK4851.71c4b895.2

Via: SIP/2.0/UDP 200.229.100.18:5060

Via: SIP/2.0/UDP 200.176.103.227:54708

Via: SIP/2.0/UDP 10.0.0.25:5060;rport;branch=z9hG4bKEF01CC8838FF465AB1FC49BFADEC2843

Record-Route: <sip:99434103@200.229.100.18:5060>

From: 55519 <sip:55519@myproxy.com>;tag=760418566

To: <sip:99434103@myproxy.com>;tag=C221BDBC-46A

Call-ID: E43869EB-1F92-4FE4-A73B-3EAAEEE5B6EE@10.0.0.25

CSeq: 53730 CANCEL

Contact: <sip:55519@200.229.100.18:5060>

Authorization: Digest username="55519", realm="myproxy.com", nonce="3fc226f57eab90d318703f3913f8d12bdfdf27fd", uri="sip:99434103@myproxy.com", response="1f17428b2a3e7ad85ed1aea6fdb162e3"

user-agent: X-Lite build 1086

Content-Length: 0

SIP/2.0 481 Call Leg/Transaction Does Not Exist

From: 55519 <sip:55519@myproxy.com>;tag=760418566

To: <sip:99434103@myproxy.com>;tag=C221BDBC-46A

Call-ID: E43869EB-1F92-4FE4-A73B-3EAAEEE5B6EE@10.0.0.25

CSeq: 53730 CANCEL

Content-Length: 0