Have you tried turning on logging on the AC client? If you click edit - settings - advanced - check the enable trace box. This may give you an idea of why it's not working or at least give you good information to send to TAC.
Normally the first indication that the "Initialization of call control failure" message should give you is that the line appearance is not associated with the AC user. I'm assuming that you have the *global* AC user configured and associated with the all the devices. Please make sure that the device controlled by the particular instance of AC that you are attempting to log into is associated with the AC user as well.
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...