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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

How to kill a VoIP call on AS5300?

I've got several hanged VoIP calls on AS5300, timers ticking but there is no active connections on e1 line nor on other side gateway. This calls keep spamming AAA server and slow down active calls listing. How can i:

1. Clear that calls without rebooting AS

2. Setup peer with call timeout, so no single call may exist for over than 30 min, for example?

I do not use any gatekeeper software.

8 REPLIES
New Member

Re: How to kill a VoIP call on AS5300?

For the command clear call, you these option some them may help you.

clear call voice causecode 1 ?

called-number clear only call with specific called number pattern

calling-number clear only call with specific calling number pattern

id clear only call with specific id

long-dur-call clear only call with long-duration being detected and notified

media-inactive clear only call with media inactive being detected and notified

New Member

Re: How to kill a VoIP call on AS5300?

gw1#clear call ?

fallback VoIP Fallback

threshold Clear stats about resource measurement

treatment Clear commands for call admission

this is all i got :(

New Member

Re: How to kill a VoIP call on AS5300?

to disconnect a given call:

Gateway#show voice call status

CallID CID ccVdb Port DSP/Ch Called # Codec Dial-peers

0x20314 2970 0x645FD848 3/1:D.28 2009/2 *2025463834 g729br8 104/103

0x20350 29D3 0x645FD848 3/1:D.30 1000/5 *0959212564 g729br8 104/103

0x20366 29F6 0x645FD848 3/1:D.29 1017/2 *2025380945 g729br8 104/103

0x20378 13C9 0x648BFA88 3/3:D.29 1002/1 *8472267541 g723r63 108/107

0x2037C 2A20 0x645FD848 3/1:D.24 2007/5 *6596841400 g729br8 104/103

0x20386 2A33 0x645FD848 3/1:D.25 2000/0 *4632220027 g729br8 104/103

0x2038C 2A3B 0x645FD848 3/1:D.23 1007/0 *4142223792 g729br8 104/103

0x20392 3D4 0x645FD848 3/1:D.21 2012/2 *5978614115 g711ulaw 104/103

clear interface serialX:Y where X is the PRI number and Y is the channel.

Bear in mind, that dorpping channel 15 will drop all calls on the given PRI!

with calltracker

(1st you have to enable it and use something like: show call calltracker active | include calling).

If you found the channel, you can use:

e.g.: (with calltracker)

DS0 slot/port/ds1/chan=0/1/1/13, called=, calling=(n/a)

clear int s1:13

New Member

Re: How to kill a VoIP call on AS5300?

Clear interface serialX:Y will NOT work, because the only thing hanging is DSP. Look this sample output (as5350, 12.3(16a)):

b5-c5350-voip5#show voice call stat | i 2/4:D.1

0x4E9B E44 0x64980238 2/4:D.1 3016/5 8228100324 g729r8 7893737/6008

0x1EF1A 1327 0x64980238 2/4:D.1 1014/3 8432647073 g729r8 7893737/6008

0x25003 1D4F 0x64980238 2/4:D.1 3015/0 8123126627 g729r8 7893737/6008

As you might see, all three calls reside on the same port.

Timeslot could be free or occupied by another call. There could be no opened TCP and UDP sockets related to the first call. Just a busy DSP. No known workaround yet, unfortunately.

New Member

Re: How to kill a VoIP call on AS5300?

You have a point, but can you explain me a little bit more? I know a DSP is a physical module on the voice board. With a G.729 codec - 8 kbps,you have two voice channels encoded per DSP.

The question is: how is the DSP busy ? Not the voice channel is busy ?

You say the voice channels are free or busy with new calls, but the DSP is busy from this bug, feature or whatewer, which is keeping the call alive and is messing up the billing...

New Member

Re: How to kill a VoIP call on AS5300?

Well, the original post was about as5300, but as5350's have similar problem and I believe that problems have a common root.

Lets look closer:

router#show voice call status | i 2/4:D.1|Port

CallID CID ccVdb Port DSP/Ch Called # Codec Dial-peers

0x4E9B E44 0x64980238 2/4:D.1 3016/5 8228100324 g729r8 7893737/6008

Substring "3016/5" shows that 5th channel on spe 3/16 is dead.

router#show spe | include 3/16|Port

SPE SPE SPE SPE Port Call

SPE# Port # State Busyout Shut Crash State Type

3/16 0096-0101 ACTIVE 0 0 0 _____a ______

Notice, that Port State is "a" (active), but corresponding Call Type is empty. Not "v" (voice), not "f" (fax), just empty.

You may shut/no shut that particular spe, mark it as "busyout" or upgrade its firmware, but all these actions won't help. Port State "a" appears again for the same channel and as5350 marks that channel as "In-Use".

router#sh spe | i Total

Ports : Total 120 In-use 35 Free 85 Disabled 0

router#sh isdn stat | i Total

Total Allocated ISDN CCBs = 32

See the difference between ports "in-use" and isdn ccbs. There are three dead ports.

New Member

Re: How to kill a VoIP call on AS5300?

gw1#sho spe ?

version SPE Version

gw1#

dammit

New Member

Re: How to kill a VoIP call on AS5300?

Sorry, I reloaded all my as5300's last night, so there are no dead DSPs.

Try to compare the first "Inuse channels" field from

router#show call resource voice stat | i Inuse|Stat

Resource Monitor - Dial-up Resource Statistics Information:

DSP Statistics:

Inuse channels: 0

DS0 Statistics:

Inuse channels: 0

and

router#show isdn stat | i Total

Total Allocated ISDN CCBs = 0

1014
Views
0
Helpful
8
Replies