JTAPI subsystem is flapping between in_service and partial_service on one of our IPCCX applications. I've stopped and restarted the CRS engine but it would run for a while and back in partial_service again. I can see in the MIVR trace file some CTI ports going OOS but they always stay registered with CCM and are associated with the proper JTAPI user. The calls to these OOS CTI ports would ring the hunt pilot since they would hit it as the CTI Route Point forwarding target (FW on Failure Ext/Int, FW Busy Int/Ext, FW No Answer Int/Ext). No FW targets defined for the CTI ports though.
What could be causing this issue? My impression is that this problem has started since we upgraded CCM 3.3 to 4.1(3)sr3a and IPCCX 3.1 to 3.5(3) but not sure.
Is anybody experiencing such a behaviour and would an upgrade to CCM 4.1(3)sr3c fix the problem?
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...