We recently upgraded from 3.1(3a) to 3.2(2c) and went straight to spC, since then our automated attendent no longer functions, in fact the whole CCRA engine is playing up, unable to refresh scripts, etc. We are on CCRA v2.2(3b).
Is anyone else have these problems? Any advise?
I noticed that Cisco released a new version of CCRA v2.2(4) on 20th August - is this perhaps a bug fix for the above? There is no information nor is 2.2(4) in the Cisco Call Manager Compatibility Matrix - so I am reluctant to try it.
I fixed my issue with CCRA, the CallManager JTAPI doesnt get updated on the CM during either the 3.2(2c) upgrade, the CM spC, upgrade or a fresh install of the CCRA. The version in use was 1.3(1.14) but needed to be 1.3(1.15), this is how I resoved the issue:-
Step 1 Log in to the CallManager Administration Page.
Step 2 Click on Applications.
Step 3 Click on Plug-ins.
Step 4 Click on Cisco JTAPI.
Step 5 Download Cisco JTAPI to the CallManager server.
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...