Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

JTAPI in partial_service

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?


Re: JTAPI in partial_service


Have you updated the JTAPI version in IPCC Express?

Hope this helps,

Juan Luis

New Member

Re: JTAPI in partial_service

Thanks. I'm getting a number of these messages:

MIVR-SS_TEL-3-DISCONNECT_FAILED and Task:91000003750 dropped before answering, but we haven't received Dropped ev

2191: Sep 06 14:08:05.496 EDT %MIVR-SS_TEL-2-SS_PARTIAL_SERVICE:JTAPI subsystem

in partial service: Failure reason=A number of CTI ports are OOS -


New Member

Re: JTAPI in partial_service

Yes, I did. I also have three other IPCCX apps running on the same server without problems. Thanks.