I have to reboot my CCM server 2-3 times a day, if not the calls are getting dropped or the transfer, hold, etc are not working also the connections are very slow or also to call a number the user have to try three or more times.
For last week I have been rebooting the CCM server every 2-3 times day in bussines hour.
From RTMT is see that the memory usage is very high.
Also I get alerts:
At 15:07:47 on 08/26/2007 on node a.b.c.d. Available memory below 10 Percent. sqlservr (286 MB) uses most of the memory.
I guess that you are probably running the call manager service on both servers, Publisher and Subscriber. There are several design possibilities around that (e.g. running it only in one Sub) but anyway in at least one server of the cluster, whatever the design is, you must run ccm.exe . For more information please click following URL:
What version of CallManager and service release? What model MCS server and how much RAM is installed? I would open a TAC case. With the right tools they can find memory leaks, etc. I would expect this would be a known issue and you need to apply a service relase or upgrade.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...