I do not see many issues from CallManager looking at syslog messages. Some are DeviceTransientConnection with reason code 6, DeviceUnregistered for home workers, HuntListExhausted (it is strange but when I see this error, it repeats 30 times in one second, I don't know why).
I have checked failed registration attempts also and this is the only one server in our cluster that has 0 failed attempts.
This server has about 300 registered phones where others have between 700-900.
The server has also the smallest "Calls InProgress" rate.
Generally speaking it's very difficult to determine the cause of these memory 'leaks' without being able to look inside the app. It's really down to guesswork...You could open a TAC case to get them to analyse it.
Usually the fix is a software patch, and in the CUCM world that will normally mean a system upgrade. If you have one of these planned I'd review the problem afterwards and worry about TAC or further troubleshooting if it doesn't go away.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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...