We have recently upgraded to 3.3(2) from 3.1(4b). AC works fine using the AC Client that came with 3.1(4b), ver 1.1.2, connecting to CM3.3(2), but when i upgraded one machine to AC 1.2.1 I get Call Control setup error when login on to the 1.2.1 AC client.
The older client still works fine. Anyone else had a problem like this and found a resolution?
Installed Ver 1.1.3 and still had the same problem. on checking the AC Log files on the client, there seemed to be an issue with Call Park. This was confusing as we don't use the call park feature.
The new version now gives a call park window, and the AC user (config not changed since 3.3 upgrade) was not configured to retrieve parked calls. Enabled the tick box, logged back in and everything now working.
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...