How do I associate the "ac" user with pilot points and phones (Hunt Groups, Attendant Console) when I have 2 clusters and one Active Directory? Both clusters are integrated now and all works fine, but now they want Hunt Groups!
Help! CCM 3.3(3), AD, CRA and Unity at each cluster. Clusters joined by Intercluster Trunk. I have gleaned from Forum ppostings and what-not, that it's a bad idea to associate a user with devices at 2 clusters, come on Cisco, help me out!
For one of the clusters, we need to change the 'ac' userid. In the file:
C:\Program Files\Cisco\CallManagerAttendant\etc\ACServer.properties, there is an entry:
Change the value 'ac' to another user besides 'ac'. Just ensure that if you have multiple call managers in a cluster then the you need to do this on all the systems within that cluster. Restart the Cisco Telephone Call Dispatcher service once you have made the change.
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...