CallManager 4.2(1)ES38 outgoing calls problem

Unanswered Question
Feb 1st, 2008


we have a big problem making outgoing calls with a CallManager 4.2(1)ES38 cluster. We have many voicegateway connected via H.323 to the callmanager cluster. Each voicegateway is located on an different branch office.

The configuration for outboun calls on the CallManager is:

Route Patter 0.T point to a RouteList that contains a RouteGroup that contain one H.323 VoiceGateway.

Everything goes well until we add a new branch office. During the creation of the new office (configured on the callmanager like the others) we notice that the CPU of one of the subscriber suddenly grew (mainly due to the ccm.exe process), and then we are not able to make outgoing calls from some of the branch offices.

Troubleshooting the problem we notice that the branch offices unable to make outgoing calls are using a Route List registered on the subscriber with high CPU.

Resetting the "frezeed" route list and registering it to another subscriber resolve the issue.

Yesterday we add a new branch office and the problem rise again.

What could be the problem? What we could do?

Thank you in advance for the help.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
mattcalderon Thu, 02/07/2008 - 08:22

That bug id is not relevant. It pertains to a memory leak on the 7900 series phones.

uldericonucci Thu, 02/07/2008 - 08:39

In fact, i thing that if there is a bug involved it would be relate to the management of route-lists or H.323 gateways, not on phones.

We are able to make outgoing calls after resetting the route-lists or doing stop/start of the callmanager process on the subscriber with high Cpu.


This Discussion