CUCM MOBILITY AND H323 PROCESSOR UTILIZATION

Unanswered Question
Sep 15th, 2010

Guys,

ive configured mobility for a client on their local H323 gateway. everything works fine from a functionality standpoint but im getting a serious issue with the router itself.

if anyone dials into the DID number or presses the mobility softkey designated for MOBILITY, the router CPU Utilization goes from about 11% straight up to 98%. if i remove the IVR url under application on the router and the associated dial peer, the CPU util drops immediately back to 11%.

i was not able to collect any further information since this is a production router and calls were not going through but its a little strange to say the least.

the router is setup on the same switch as the CUCM and the phones are in the same building.

i think the CPU HOG is CCH323_CT but ill have to verify this after hours.

the router is a 3825 ADVANCED IP SERVICES Version 12.4(25c).

i know this is really not much information to go on at all but i was jus wondering if anyone had any similar issues with MOBILITY and H323 gateways similar to my current experience.

PS. ive done about two other mobility setups like this and have never seen any issues thus far.

thanks for any insight.

ps this is the cpu history


    888888777777777777777999997777777777777778888877777888887777
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)


       11 111111111111 11111 11 1111            1   11 129999999
    889019001011001000990200909999798898899988999899089118998888
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%


    9911  111 1 1111 1999119991111 11 111 1 1122
    99506853180720048088883858130490290117888461
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%

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
a.gooding Thu, 09/16/2010 - 12:31

im able to recreate the high utilization by NOT specifying the incoming called number under the dial-peer for mobility on the router.

on my production system i do have the incoming called number but this might be the underlying issue.

Actions

This Discussion