Upgraded CCM from 3.3.3 to 4.1 That went fine no issues.
Upgraded the IPCC from 3.1 to 4.02 now agents can't login. Getting LDAP error. Also, none of the CTI ports are registered with CCM...The subsystem service shows stopped but all subsystems are configed correctly. (Jtapi, RM, etc.) Jtapi versions are the same etc. DC directory and LDAP appear to be setup correctly.(correct passwords etc.)
Are there any known issues etc.... Where could the problem be?
When I had the problem of the JTAPI subsystem not starting, it ended up being a bogus HTTP trigger in Active Directory. I didn't have any HTTP triggers configured, but one showed up after the upgrade. The solution was to delete the HTTP trigger. I'm not sure if this issue is specific to AD or could also occur with DC directory. If you are working with TAC, have them refer to case# 602121725.
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...