Got a issue that has been getting worse of the last few weeks. It went from maybe a few loops to holy cow batman. I have no way of seeing which calls are looping in which dial-peers because the show call history voice doesn't go that far back even though it was onl about 7 hours ago. Is there anyway to see these calls that I am missing? This particular CUBE doesn't handle much voice traffic compared to our other two but I want to get this resolved. Any ideas would be greatly appreciated.
Oct 4 2012 03:11:37.899 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:13:25.281 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:15:05.991 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:16:15.177 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:17:12.350 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:18:48.012 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:19:30.021 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:19:50.902 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:20:46.399 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 03:21:08.799 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 10:43:06.920 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 4 2012 11:01:41.832 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:09:48.661 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:10:07.437 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:10:16.406 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:10:30.046 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:10:39.510 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:11:00.183 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:11:22.175 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:11:42.179 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:12:05.500 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:14:04.535 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:14:37.687 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:16:00.405 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:16:36.134 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:17:01.858 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:17:24.075 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:17:52.016 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:18:42.521 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:18:48.669 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Oct 5 2012 03:19:20.237 UTC: %CALL_CONTROL-6-CALL_LOOP: The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
====================================================================
AUDC1M1APVGR01#show proc cpu his
AUDC1M1APVGR01 03:02:40 PM Friday Oct 5 2012 UTC
555555333333333333333333334444444444333338888844444555556666
100
90
80
70
60
50
40
30
20
10 ****** ***** *********
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per second (last 60 seconds)
====================================================================
1 1 1 1 1111111111111111111111111111111211111
797899298962888988808091112223422221311226322222211222034122
100
90
80
70
60
50
40
30
20 * *
10 ******##*************#######################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
=====================================================================
221112111113111122121111121111111113111111311111902111211125111121111121
009841472865448700616455836454577463513365446478900573786416485633550509
100 **
90 **
80 **
70 **
60 ** *
50 ** *
40 * ** *
30 * * * ** * *
20 **** * * *** ******* ***** * *** *** *** * ******* *** ** **** ** ***
10 ##**#*##**#************######*##**#***********######**#####***********##
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
So based on Solarwinds and my router they both line up exactly as expected but I can't go that far back in the call history. Please help
