Cisco Unified Communications Manager (CallManager)

Unified Communications Manager: kCtiIncompatibleProtocolVersion - Incompatible Protocol Version Error in Event Log

Document ID: 91885

Updated: May 29, 2007



This document discusses the kCtiIncompatibleProtocolVersion - Incompatible protocol version error message that is displayed in the event log after an upgrade of the Cisco Unified Communications Manager.

This error message indicates that some applications that have a Telephony Application Programming Interface and Java Telephony Application Programming Interface (TAPI/JTAPI) in use still run an outdated version which is not compatible with the version included in the new version of CallManager.



Readers of this document should have a general knowledge of Cisco Unified Communications Manager.

Components Used

The information in this document is based on Cisco Unified Communications Manager 4.1.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.


Refer to Cisco Technical Tips Conventions for more information on document conventions.


After an upgrade of the Cisco Unified Communications Manager, this error message is displayed in the event log.

Event Type:	Error
Event Source:	Cisco CTIManager
Event Category:	None
Event ID:	3
Date:		6/28/2005
Time:		11:24:54 AM
User:		N/A
Computer:	CBHP-SUB1
Error: kCtiIncompatibleProtocolVersion - Incompatible protocol version.
 Message Version: 0
 Minimum Version: 60000
 Current Version: 60000
 CallManager Version: 
 App ID: Cisco CTIManager
 Cluster ID: CBHA-PUB1-Cluster
 Node ID:
 Process ID: 852
 Process Name: CtiHandler
Explanation: The JTAPI/TAPI application version is not compatible 
with this version of CTIManager, so received message has 

been rejected. 
Recommended Action: Verify correct version of application 
are being used; otherwise,contact TAC.. 

This problem arises when the Cisco Unified Communications Manager is upgraded, but not the TAPI/JTAPI clients.

You must upgrade the TAPI/JTAPI client software on any application server or client workstation on which TAPI/JTAPI applications are installed. If you do not upgrade the TAPI/JTAPI client, your application fails to initialize.


In the event log error message, the TAPI or JTAPI client installed on the device with the IP address of has not been upgraded to a compatible version.

You need to investigate the device to find what application at this address uses TAPI/JTAPI and update the corresponding package from the CallManager Administration > Applications > Install Plugins as this section shows. In this example, the device is the one with the IP address of

Note: Some of the applications that use JTAPI/TAPI interfaces are Personal Assistant, Attendant Console, IPCC Express, TAPS, and Extension Mobility.


If you need to upgrade the JTAPI version, select Cisco JTAPI, as this example shows:


If you need to upgrade the Telephony Service Provider, select Cisco Telephony Service Provider, as this example shows:


Related Information

Updated: May 29, 2007
Document ID: 91885