cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2042
Views
0
Helpful
2
Replies

Call not cancelled during ringing - 481 Call Leg/Transaction Does Not Exist

Risko
Level 1
Level 1

Hi,

 

I have working setup:

ISP - SIP trunk - CUBE - SIP trunk - CUCM - IP Phone

 

CUBE is vCUBE on CSR1000V 16.9.5

CUCM is 12.5 SU2

 

Calls in and out are working as expected.

Call cancel works from CUCM side for both already connected and also for ringing calls.

Call cancel works from ISP side for already connected calls.

Call cancel does not work from ISP side for ringing calls.

 

I checked INVITE/CANCEL pair against RFC3261, but found no problem.

 

 

Mar 20 21:04:53.593: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:249202050@10.21.28.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKg0893o00c0h0q8hm61j1.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Call-ID: BW210453577200320914369156@10.20.60.10
CSeq: 1019622501 INVITE
Contact: <sip:0998797808@10.10.10.10:5060;transport=udp>
P-Early-Media: supported
Supported: 100rel
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Recv-Info: x-broadworks-client-session-info
Accept: application/btbc-session-info,application/dtmf-relay,application/media_control+xml,application/sdp,multipart/mixed
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 281
v=0
o=BroadWorks 741313458 1 IN IP4 10.10.10.10
s=-
c=IN IP4 10.10.10.10
t=0 0
a=sendrecv
m=audio 22770 RTP/AVP 8 0 96
c=IN IP4 10.10.10.10
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=ptime:20
a=maxptime:40
Mar 20 21:04:53.597: //1717/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKg0893o00c0h0q8hm61j1.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: BW210453577200320914369156@10.20.60.10
CSeq: 1019622501 INVITE
Allow-Events: telephone-event
         
Server: Cisco-SIPGateway/IOS-16.9.5
Session-ID: 00000000000000000000000000000000;remote=438a659d807659068a774134a0661487
Content-Length: 0

Mar 20 21:04:53.599: //1718/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:1744@192.168.12.11:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.13.13:5060;branch=z9hG4bK4ACECF
From: <sip:00998797808@sip.vvn.telekom.xx>;tag=1F7ACDC-170C
To: <sip:1744@192.168.12.11>
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: E5D7DE5A-6A1C11EA-86ECD506-AE138B73@192.168.13.13
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 3856089650-1780224490-2263274758-2920516467
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1584734693
Contact: <sip:00998797808@192.168.13.13:5060>
Call-Info: <sip:192.168.13.13:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
P-Preferred-Identity: <sip:00998797808@192.168.13.13>
Session-ID: 438a659d807659068a774134a0661487;remote=00000000000000000000000000000000
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 269
v=0
o=CiscoSystemsSIP-GW-UserAgent 5447 338 IN IP4 192.168.13.13
s=SIP Call
c=IN IP4 192.168.13.13
t=0 0
m=audio 8070 RTP/AVP 8 0 101
c=IN IP4 192.168.13.13
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Mar 20 21:04:53.603: //1718/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.13.13:5060;branch=z9hG4bK4ACECF
From: <sip:00998797808@sip.vvn.telekom.xx>;tag=1F7ACDC-170C
To: <sip:1744@192.168.12.11>
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: E5D7DE5A-6A1C11EA-86ECD506-AE138B73@192.168.13.13
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0

Mar 20 21:04:53.608: //1718/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.13.13:5060;branch=z9hG4bK4ACECF
From: <sip:00998797808@sip.vvn.telekom.xx>;tag=1F7ACDC-170C
To: <sip:1744@192.168.12.11>;tag=3363747~0e8a5909-b53b-4564-b0ce-49d6ede91b3c-32644709
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: E5D7DE5A-6A1C11EA-86ECD506-AE138B73@192.168.13.13
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Server: Cisco-CUCM12.5
Call-Info: <sip:192.168.12.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-ID: 5297ccfe38b5cf155813c8ba32644710;remote=438a659d807659068a774134a0661487
P-Preferred-Identity: "KC1744" <sip:1744@192.168.12.11>
Remote-Party-ID: "KC1744" <sip:1744@192.168.12.11>;party=called;screen=yes;privacy=off
Contact: <sip:1744@192.168.12.11:5060>
Content-Length: 0

Mar 20 21:04:53.609: //1717/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKg0893o00c0h0q8hm61j1.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>;tag=1F7ACE6-1AFA
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: BW210453577200320914369156@10.20.60.10
CSeq: 1019622501 INVITE
Require: 100rel
RSeq: 6923
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
         
P-Preferred-Identity: "KC1744" <sip:1744@10.21.28.3>
Contact: <sip:249202054@10.21.28.3:5060>
Server: Cisco-SIPGateway/IOS-16.9.5
Session-ID: 5297ccfe38b5cf155813c8ba32644710;remote=438a659d807659068a774134a0661487
Content-Length: 0

Mar 20 21:04:53.647: //1717/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:249202054@10.21.28.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKpg360m00do6gn9h3p2p0.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>;tag=1F7ACE6-1AFA
Call-ID: BW210453577200320914369156@10.20.60.10
CSeq: 1019622502 PRACK
RAck: 6923 1019622501 INVITE
Max-Forwards: 69
Content-Length: 0

Mar 20 21:04:53.647: //1717/E5D7423286E6/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKpg360m00do6gn9h3p2p0.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>;tag=1F7ACE6-1AFA
Date: Fri, 20 Mar 2020 20:04:53 GMT
Call-ID: BW210453577200320914369156@10.20.60.10
Server: Cisco-SIPGateway/IOS-16.9.5
CSeq: 1019622502 PRACK
Session-ID: 5297ccfe38b5cf155813c8ba32644710;remote=438a659d807659068a774134a0661487
Content-Length: 0

Mar 20 21:04:57.058: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:249202050@10.21.28.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKg0893o00c0h0q8hm61j1.1
CSeq: 1019622501 CANCEL
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Call-ID: BW210453577200320914369156@10.20.60.10
Max-Forwards: 69
Content-Length: 0

Mar 20 21:04:57.058: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKg0893o00c0h0q8hm61j1.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=687003861-1584734693577-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Call-ID: BW210453577200320914369156@10.20.60.10
CSeq: 1019622501 CANCEL
Content-Length: 0

 

 

What can be wrong?

 

Thank you

 

Kind regards,

Richard

1 Accepted Solution

Accepted Solutions

Risko
Level 1
Level 1

I've got rid of 481 error.

Because of ITSP requirement I have to do some SIP header manipulation for inbound calls.

I was only doing these for INVITE.

Now I do the same for CANCEL and 481 is gone

 

 

But now I have error 400 Bad Request - 'Malformed/Missing Contact field'

 

Mar 23 12:16:27.249: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:249202050@10.21.28.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKig8e4d302gn1mvcas640.1
CSeq: 59626521 CANCEL
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=1748283543-1584962185264-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Call-ID: BW1216252642303201296355456@10.20.60.10
Max-Forwards: 69
Content-Length: 0

Mar 23 12:16:27.250: //13305/91760D45B42C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field'
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKig8e4d302gn1mvcas640.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=1748283543-1584962185264-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>;tag=F86EC5C-103D
         
Call-ID: BW1216252642303201296355456@10.20.60.10
Session-ID: 5297ccfe38b5cf155813c8ba32645933;remote=077e058905325f3b904b639e2701bcf8
CSeq: 59626521 CANCEL
Reason: Q.850;cause=100
Content-Length: 0

 

 

After looking at sip-profiles rules again I've found typo.

Was:

request CANCEL sip-header To copy "sip:(.*)@" u01

request CANCEL sip-header SIP-Req-URI modify ".*@(.*)" "INVITE sip:\u01@\1"

Should be:

request CANCEL sip-header To copy "sip:(.*)@" u01

request CANCEL sip-header SIP-Req-URI modify ".*@(.*)" "CANCEL sip:\u01@\1"

 

Everything works as expected now.

 

Kind regards,

Richard

View solution in original post

2 Replies 2

Risko
Level 1
Level 1

Still don't know why CUBE generates 481 for CANCEL from ITSP. Looks like a bug to me.

 

But instead of letting IP Phone to ring 3 minutes for already cancelled call from ITSP I've set forward no answer to nonexistent DN (we stopped using voicemail - nobody used it). It rings 12 seconds and drops.

Not the best workaround, but acceptable for today..

 

Richard

Risko
Level 1
Level 1

I've got rid of 481 error.

Because of ITSP requirement I have to do some SIP header manipulation for inbound calls.

I was only doing these for INVITE.

Now I do the same for CANCEL and 481 is gone

 

 

But now I have error 400 Bad Request - 'Malformed/Missing Contact field'

 

Mar 23 12:16:27.249: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:249202050@10.21.28.3:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKig8e4d302gn1mvcas640.1
CSeq: 59626521 CANCEL
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=1748283543-1584962185264-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>
Call-ID: BW1216252642303201296355456@10.20.60.10
Max-Forwards: 69
Content-Length: 0

Mar 23 12:16:27.250: //13305/91760D45B42C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field'
Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bKig8e4d302gn1mvcas640.1
From: <sip:0998797808@sip.vvn.telekom.xx;user=phone>;tag=1748283543-1584962185264-
To: "02 49202054"<sip:249202054@sip.vvn.telekom.xx:5060;user=phone>;tag=F86EC5C-103D
         
Call-ID: BW1216252642303201296355456@10.20.60.10
Session-ID: 5297ccfe38b5cf155813c8ba32645933;remote=077e058905325f3b904b639e2701bcf8
CSeq: 59626521 CANCEL
Reason: Q.850;cause=100
Content-Length: 0

 

 

After looking at sip-profiles rules again I've found typo.

Was:

request CANCEL sip-header To copy "sip:(.*)@" u01

request CANCEL sip-header SIP-Req-URI modify ".*@(.*)" "INVITE sip:\u01@\1"

Should be:

request CANCEL sip-header To copy "sip:(.*)@" u01

request CANCEL sip-header SIP-Req-URI modify ".*@(.*)" "CANCEL sip:\u01@\1"

 

Everything works as expected now.

 

Kind regards,

Richard

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: