We have an IPCCX 4.0(5) HA system where the JTAPI subsystem is in partial service, but all CTI ports and CTI Route point are correctly registered and are working.
The MIVR logs a problem with CTI RPs being out of service, but all RPs are workings. Although I have noticed some RPs will go to dead air if they're updated and sometimes need a refresh to put back in service.
3677895: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-2-SS_PARTIAL_SERVICE:JTAPI subsystem in partial service: Failure reason=A number of route points are OOS - RP[num=1664]
3677896: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-7-UNK:calculateSubsystemState
you pointed at the issue by yourself, whenever a route point is going out of service(loss of heartbeats, high CPU, network issues, network card settings mismatch), the JTAPI will move to partial service, in your case 11 triggers that are showing Out of Service
3677900: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-7-UNK:calculateSubsystemState -> subsystem partial in service, unchanged cause: A number of route points are OOS - RP[num=1664]
3677901: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-6-CTI_ADDRESS_EVENT:Receives: Event=CiscoAddrOutOfService,cause=100,Addr=RP[num=1664]
3677902: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-6-CTI_ADDRESS_EVENT:Receives: Event=CiscoAddrInService,Addr=RP[num=1664]
3677903: Mar 10 18:58:35.677 GMT %MIVR-SS_TEL-7-UNK:Route.setServiceState() from Out of Service to In Service for RP[num=1664]
They are in service and are holding. I've just had to restart the second node, as some of the services had failed over to the second node as a result of overnight power issues. Now on the second node, the JTAPI subsystem is in full service.
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...