Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

How to clear the hung calls on CUBE?

 

 

Problem Description

 

Requirement / Issue:

 

Service Provider is using ISR 3945 as a Cisco Unified Border Element (CUBE) to connect to his Interconnects over SIP trunks. It is unclear what causes the condition when a call disconnects on one side but does not get cleared on the other side, and results in Call hanging/Call hung.

However, it does happen sometimes and causes hanging calls on CUBE. ISP will be requesting their partner Service Provider to identify and clear the hung state calls to avoid blocking of connections and these can be cleared manually in CUBE as shown here.

 

Solution

 

Show commands to Identify the active calls:

 

Show commands

 

 

 

SBC02#sh call active voice summary

 

Telephony call-legs: 0

 

SIP call-legs: 4

 

H323 call-legs: 0

 

Call agent controlled call-legs: 0

 

SCCP call-legs: 0

 

Multicast call-legs: 0

 

Total call-legs: 4


SBC02#sh rtp call

 

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 138 139 17110 16400 10.22.0.113 200.0.2.254

callId 138 (dir=1): called=2126315001 calling=2009 redirect=

dest callId 139: called=2126315001 calling=2009 redirect=

1 context C0B89140 xmitFunc 6369789C

2 139 138 17582 16428 10.22.0.113 20.1.1.22

callId 139 (dir=2): called=2126315001 calling=2009 redirect=

dest callId 138: called=2126315001 calling=2009 redirect=

1 context 68F85540 xmitFunc 6369789C

3 140 141 16514 16430 10.22.0.113 20.1.1.22

1 context 68F5CF00 xmitFunc 6369789C

4 141 140 16432 16402 10.22.0.113 200.0.2.254

1 context 68F61DC0 xmitFunc 6369789C

 

Found 4 active RTP connections

 

 

SBC02#show sip calls

 

SIP UAC CALL INFO

 

Call 1

SIP Call ID : BD56F427-1A5311DE-80C2D220-A86CA6FD@10.21.0.113

State of the call : STATE_ACTIVE (7)

Substate of the call : SUBSTATE_NONE (0)

Calling Number : 26316001

Called Number : 2126315001

Bit Flags : 0xC04018 0x300 0x80080

CC Call ID : 139

Source IP Address (Sig ): 10.21.0.113

Destn SIP Req Addr:Port : [20.1.1.1]:5060

Destn SIP Resp Addr:Port: [20.1.1.1]:5060

Destination Name : 20.1.1.1

Number of Media Streams : 2

Number of Active Streams: 2

RTP Fork Object : 0x0

Media Mode : flow-through

Media Stream 1

State of the stream : STREAM_ACTIVE

Stream Call ID : 139

Stream Type : voice+dtmf (1)

Stream Media Addr Type : 1

Negotiated Codec : Passthrough (0 bytes)

Codec Payload Type : 255 (None)

Negotiated Dtmf-relay : inband-voice

Dtmf-relay Payload Type : 0

Media Source IP Addr:Port: [10.22.0.113]:17582

Media Dest IP Addr:Port : [20.1.1.22]:16428

Media Stream 2

State of the stream : STREAM_ACTIVE

Stream Call ID : 140

Stream Type : voice+dtmf (1)

Stream Media Addr Type : 1

Negotiated Codec : Passthrough (0 bytes)

Codec Payload Type : 255 (None)

Negotiated Dtmf-relay : inband-voice

Dtmf-relay Payload Type : 0

Media Source IP Addr:Port: [10.22.0.113]:16514

Media Dest IP Addr:Port : [20.1.1.22]:16430

 

Options-Ping ENABLED:NO ACTIVE:NO

Number of SIP User Agent Client(UAC) calls: 1

 

SIP UAS CALL INFO

 

Call 1

SIP Call ID : 622C6BFA-1@200.0.2.254

State of the call : STATE_ACTIVE (7)

Substate of the call : SUBSTATE_NONE (0)

Calling Number : 2009

Called Number : 2126315001

Bit Flags : 0xC0401E 0x300 0x80004

CC Call ID : 138

Source IP Address (Sig ): 10.21.0.113

Destn SIP Req Addr:Port : [200.0.2.254]:5063

Destn SIP Resp Addr:Port: [200.0.2.254]:1261

Destination Name : 200.0.2.254

Number of Media Streams : 2

Number of Active Streams: 2

RTP Fork Object : 0x0

Media Mode : flow-through

Media Stream 1

State of the stream : STREAM_ACTIVE

Stream Call ID : 138

Stream Type : voice+dtmf (1)

Stream Media Addr Type : 1

Negotiated Codec : Passthrough (0 bytes)

Codec Payload Type : 255 (None)

Negotiated Dtmf-relay : inband-voice

Dtmf-relay Payload Type : 0

Media Source IP Addr:Port: [10.22.0.113]:17110

Media Dest IP Addr:Port : [200.0.2.254]:16400

Media Stream 2

State of the stream : STREAM_ACTIVE

Stream Call ID : 141

Stream Type : voice+dtmf (1)

Stream Media Addr Type : 1

Negotiated Codec : Passthrough (0 bytes)

Codec Payload Type : 255 (None)

Negotiated Dtmf-relay : inband-voice

Dtmf-relay Payload Type : 0

Media Source IP Addr:Port: [10.22.0.113]:16432

Media Dest IP Addr:Port : [200.0.2.254]:16402

 

Options-Ping ENABLED:NO ACTIVE:NO

Number of SIP User Agent Server(UAS) calls: 1

 

 

Use the "called" number from the show commands given and use the "clear call voice" command to clear the hung calls towards the ISP network with the Call ID and Cause Code Value of the hung call:

 

Clear Call Voice command: To clear one or more voice calls detected as inactive because there is no RTP or RTCP activity, use the clear call voice command in EXEC or privileged EXEC mode.

 

hung-1.png

 

 

For the above example execute this command and use the "Called-number" field to clear the hung calls with the Called Number : 2126315001

 

SBC02#clear call voice causecode 17 called-number 2126315001

 

This is how you can clear the hung inactive voice calls on Cisco Unified Border Element (CUBE).

 

 

More Example:

 

The following example clears inactive voice calls with the cause code ID of 112B:

 

SBC02# clear call voice causecode 1 id 112B

 

 

 

Related Information

Comments

Sometimes there are very persistent, often 'faulty' calls in there as a result of testing and misconfiguration and these calls won't be cleared with the above command.

 

Any clues as to how these calls may be cleared?

New Member

Hi Peet

 

The only way to clear those persistent calls would be to reboot the CUBE. I have tried several methods to clear hung calls, none of them seemed to work. I opened a Cisco TAC case and they said to reboot the CUBE is the only way to really clear them.

 

 

9381
Views
0
Helpful
2
Comments