I have succeeded installing CUOM 2.0.3 and CUSM 2.0.1 without erros. The server was in pre production. Afterwards the customer's TI staff took the server and made the updates and changes they need to conform the server to their policies.
I have completely removed the CUOM/CUSM software before the TI staff updated the server.
After they finisheded I have reinstalled the CUOM/CUSM but it did not work properly as before. I got several erros on the isnstallation log. I have removed and reinstaled but still the same. I am attaching the good (before TI changes) and the bad installation log and a Server Information file generated using the bad installation.
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...