CCM 3.1.3(a), three call managers total in the same cluster, two subscribers, one publisher.
A weird situation going on:
We've been having problems with 7940 and 7960 IP phones and VG248's that seem to drop their connection and start the registration process over again seemingly at random. This has been happening for over a month, and we're still trying to pin down the cause - is it the call managers? Is it the new switches we ordered? Is the wiring in the new closets substandard? We don't know, and personally I'm reaching my wit's end.
Here's the scenario:
1. All phones that are re-registering are connected to two brand new wiring closets. One closet has phones that re-register more than others.
2. Both closets have a VG248. However, I have four VG248's installed total, one also in a new closet that has had no problems. We never had any problems until a month ago.
3. I usually receive one error on the VG248 a few minutes before the phones restart themselves: "Registration Failed: Unexpected CM Register Acknowledgment"
4. The re-registering does not occur at the same time every day.
5. Today, the CallManager service gave me a "SDL Router Services Declared Dead" on the subscriber call manager the phones normally register with. The server was restarted, and everything came right back where it should.
6. The status on my VG248's and the inline power switches say they've been up for over a month, so I don't think it's a power loss issue.
7. A few days ago, while the phones tried to re-register, I was getting TFTP errors, seemingly from those IP phones whose registration took too long (several hours).
Here are some excerpts from the trace logs on the subscriber call manager (these were taken when the devices went to register with their correct subscriber call manager):
Take a look at the release notes for CCM 3.1.3a... There is a bug listed under open caveats that sounds like it matches your problem description. The resolution is to "Set runtime priority on StiView.exe to low using task manager. This will prevent the Cisco CallManager from stopping and restarting."
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...