Situation now, is that a CallManager upgrade from CCM4.1(2) to CCM4.1(3)SR3 are messing up the ATA-boxes. Althoug we followed the instructions carefully, approx 30% of all the ATAs didnt register at all. Also some of them come and go. After troubleshooting all the day, problem still seems to be totally random distributed, both geographically and network technically.
An troublesome ATA might be placed in the same building, have identical configuration, have neighbour IP-address, and have an identical history to the one that works perfectly OK. This follows no rules.
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...