cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2992
Views
0
Helpful
4
Replies

'Stuck' / Inactive calls consuming DSP resources on CUBE router

voip7372
Level 4
Level 4

We recently opened a ticket with Cisco regarding DSP resources being tied up in the CUBE router by what appears to be stuck calls - calls that never finished clearing after the call ended.  These are all calls that had trannscoding.  It looks like the transcoding part of the call is still live/stuck and eating up the PVDM4 resources (4351 router).  

 

The entries below were not in the router but the tech suggested we add them, so I did.  I'm still seeing the stuck calls.  The idea was that these entries would check for inactivity and automatically clear these calls after a certain period of time so we don't have to reload the router to clear them.   My concern of course is that we don't accidentally clear any real/live/active calls.  

 

Anyway, I was wondering about the entry called timer receive-rtp 1200, because the cisco document says if you're going to use the combination of commands called ip rtcp report interval and timer receive-rtcp, the router would watch for the rtcp and not rtp to see if the call is really active.  So I'm wondering if I should remove that entry rtp.  

 

So, based on the entries below, I'm not sure if the entries we have for the rtp and rtcp is correct and maybe that's why these inactive transcoding sessions are still live?   I'll paste an example of what I see near the end of the day.   Lots of inactive calls/sccp connections.

 

ip rtcp report interval 10000
ip rtcp report interval 10000' means Interval between subsequent Real-Time Control Protocol (RTCP) report transmissions - 10000 is milliseconds (10 seconds)

 

gateway
media-inactivity-criteria all
Both rtcp and rtp will be checked

 

timer receive-rtcp 15
‘timer receive-rtcp 15’ means 15 x the ‘ip rtcp report interval’ command, so in this case the report interval is 10000....so 15 x 10000 = 150 seconds (150,000 miliseconds)

 

timer receive-rtp 1200
‘timer receive-rtp 1200’ means 1200 milliseconds which is 20 minutes. RTCP should be catching the inactive calls, but the RTP entry was added as a backup/failsafe to catch hung/stuck calls.

 

Per Cisco Doc: When the ip rtcp report interval and timer receive-rtcp commands are used, the gateway uses RTCP report detection, rather than RTP packet detection, to determine whether calls on the gateway are still active or should be disconnected.

 

Example of stuck calls (only pasting in the stuck calls, not the real calls since those have phone numbers appearing and I don't want to post that here...and I also changed the IP addresses below - not real):

 

CUBE#show call act voi com
<callID> A/O FAX T<sec> Codec type Peer Address IP R<ip>:<udp>
Total call-legs: 71
315 ORG T23209 g711ulaw VOIP P 172.16.5.30:8184
332 ORG T23109 g711ulaw VOIP P 172.16.5.30:8202
851 ORG T17707 g711ulaw VOIP P 172.16.5.30:8220
1018 ORG T16010 g711ulaw VOIP P 172.16.5.30:8776
1078 ORG T15669 g711ulaw VOIP P 172.16.5.30:8850
1136 ORG T15297 g711ulaw VOIP P 172.16.5.30:8918
1196 ORG T14831 g711ulaw VOIP P 172.16.5.30:8980
1209 ORG T14731 g711ulaw VOIP P 172.16.5.30:8998
1226 ORG T14649 g711ulaw VOIP P 172.16.5.30:9016
1235 ORG T14584 g711ulaw VOIP P 172.16.5.30:9026
1261 ORG T14456 g711ulaw VOIP P 172.16.5.30:9044
1280 ORG T14376 g711ulaw VOIP P 172.16.5.30:9086
1308 ORG T14293 g711ulaw VOIP P 172.16.5.30:9104
1322 ORG T14229 g711ulaw VOIP P 172.16.5.30:9138
1352 ORG T14080 g711ulaw VOIP P 172.16.5.30:9172
1363 ORG T14025 g711ulaw VOIP P 172.16.5.30:9198
1377 ORG T13938 g711ulaw VOIP P 172.16.5.30:9216
1406 ORG T13877 g711ulaw VOIP P 172.16.5.30:9258
1443 ORG T13711 g711ulaw VOIP P 172.16.5.30:9308
1464 ORG T13672 g711ulaw VOIP P 172.16.5.30:9332
1484 ORG T13587 g711ulaw VOIP P 172.16.5.30:9370
1523 ORG T13522 g711ulaw VOIP P 172.16.5.30:9420
1554 ORG T13335 g711ulaw VOIP P 172.16.5.30:9468
1561 ORG T13316 g711ulaw VOIP P 172.16.5.30:9484
1576 ORG T13233 g711ulaw VOIP P 172.16.5.30:9508
1594 ORG T13170 g711ulaw VOIP P 172.16.5.30:9534
1648 ORG T12733 g711ulaw VOIP P 172.16.5.30:9116
2441 ORG T8351 g711ulaw VOIP P 172.16.5.30:8928
2652 ORG T6908 g711ulaw VOIP P 172.16.5.30:10836
2671 ORG T6803 g711ulaw VOIP P 172.16.5.30:10866
2719 ORG T6702 g711ulaw VOIP P 172.16.5.30:10948
2745 ORG T6597 g711ulaw VOIP P 172.16.5.30:10974
2755 ORG T6492 g711ulaw VOIP P 172.16.5.30:10992
2931 ORG T5355 g711ulaw VOIP P 172.16.5.30:11206
2956 ORG T5160 g711ulaw VOIP P 172.16.5.30:11236
2993 ORG T4979 g711ulaw VOIP P 172.16.5.30:11278
3034 ORG T4792 g711ulaw VOIP P 172.16.5.30:11332
3062 ORG T4617 g711ulaw VOIP P 172.16.5.30:11366
3089 ORG T4424 g711ulaw VOIP P 172.16.5.30:11400

 

CUBE#show sccp conn
sess_id conn_id stype mode codec sport rport ripaddr conn_id_tx
50825156 50700719 xcode inactive g711u 8200 8184 172.16.5.30
50825165 50700728 xcode inactive g711u 8218 8202 172.16.5.30
50825169 50700997 xcode inactive g711u 8640 8220 172.16.5.30
50825375 50701097 xcode inactive g711u 8784 8776 172.16.5.30
50825397 50701136 xcode inactive g711u 8858 8850 172.16.5.30
50825420 50701175 xcode inactive g711u 8926 8918 172.16.5.30
50825421 50701941 xcode inactive g711u 10606 8928 172.16.5.30
50825441 50701210 xcode inactive g711u 8988 8980 172.16.5.30
50825446 50701219 xcode inactive g711u 9006 8998 172.16.5.30
50825450 50701229 xcode inactive g711u 9024 9016 172.16.5.30
50825455 50701240 xcode inactive g711u 9034 9026 172.16.5.30
50825458 50701247 xcode inactive g711u 9068 9044 172.16.5.30
50825466 50701261 xcode inactive g711u 9094 9086 172.16.5.30
50825473 50701279 xcode inactive g711u 9132 9104 172.16.5.30
50825474 50701464 xcode inactive g711u 9600 9116 172.16.5.30
50825477 50701286 xcode inactive g711u 9150 9138 172.16.5.30
50825487 50701301 xcode inactive g711u 9192 9172 172.16.5.30
50825490 50701307 xcode inactive g711u 9206 9198 172.16.5.30
50825493 50701314 xcode inactive g711u 9224 9216 172.16.5.30
50825505 50701338 xcode inactive g711u 9270 9258 172.16.5.30
50825514 50701354 xcode inactive g711u 9320 9308 172.16.5.30
50825518 50701368 xcode inactive g711u 9352 9332 172.16.5.30
50825524 50701380 xcode inactive g711u 9382 9370 172.16.5.30
50825533 50701396 xcode inactive g711u 9446 9420 172.16.5.30
50825540 50701406 xcode inactive g711u 9488 9468 172.16.5.30
50825542 50701409 xcode inactive g711u 9494 9484 172.16.5.30
50825547 50701417 xcode inactive g711u 9516 9508 172.16.5.30
50825552 50701428 xcode inactive g711u 9542 9534 172.16.5.30
50825927 50702059 xcode inactive g711u 10848 10836 172.16.5.30
50825933 50702070 xcode inactive g711u 10874 10866 172.16.5.30
50825935 50702075 xcode inactive g711u 10956 10948 172.16.5.30
50825942 50702090 xcode inactive g711u 10990 10974 172.16.5.30
50825946 50702099 xcode inactive g711u 11000 10992 172.16.5.30
50826007 50702207 xcode inactive g711u 11218 11206 172.16.5.30
50826017 50702230 xcode inactive g711u 11244 11236 172.16.5.30
50826031 50702251 xcode inactive g711u 11290 11278 172.16.5.30
50826044 50702272 xcode inactive g711u 11344 11332 172.16.5.30
50826059 50702295 xcode inactive g711u 11378 11366 172.16.5.30
50826068 50702312 xcode inactive g711u 11408 11400 172.16.5.30

1 Accepted Solution

Accepted Solutions

voip7372
Level 4
Level 4

I don't need these settings I mentioned because I finally found a version of software for the 4351 that doesn't have this problem of inactive transcoding sessions / stuck calls.  After installing this version, the problem magically disappeared!  :-)    I have not seen ANY stuck/inactive calls since installing this.  

 

Cisco IOS XE Software, Version 03.16.07a.S - Extended Support Release
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S7a, RELEASE SOFTWARE (fc1)

View solution in original post

4 Replies 4

voip7372
Level 4
Level 4

I don't need these settings I mentioned because I finally found a version of software for the 4351 that doesn't have this problem of inactive transcoding sessions / stuck calls.  After installing this version, the problem magically disappeared!  :-)    I have not seen ANY stuck/inactive calls since installing this.  

 

Cisco IOS XE Software, Version 03.16.07a.S - Extended Support Release
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S7a, RELEASE SOFTWARE (fc1)

What version were you on previously ?

Description: Cisco ISR 4300 Series IOS XE Universal
Release: 3.16.6S
Release Date: 31/Jul/2017
File Name: isr4300-universalk9.03.16.06.S.155-3.S6-ext.SPA.bin

 

I had another version before that one that had the same problem but I don't remember the exact version I was using.  

R0g22
Cisco Employee
Cisco Employee
Those are some recommended best practices to workaround this issue. With ISR-4k, the DSP code is or I should say was a bit meh. BU has worked really well to fix a large number of issues with DSP's in general. Some older versions like the one you have and the newer ones are much more stable. The issues in general are due to the architecture change where we moved to a split plane versus the G2's single plane.