Cisco Cisco Unified Contact Center Express 9.0(1) Information Guide
Manually Check the JTAPI Version on the CRS
Server
Server
Document ID: 51443
Contents
Introduction
How do I manually check the JTAPI client version on the Cisco Response Solutions (CRS) server?
Related Information
Related Information
Introduction
This document describes how to manually check the Java Telephony Application Programming Interface
(JTAPI) client version on the Cisco Customer Response Solutions (CRS) server when communicating with
different session partners in a Cisco IP Contact Center (IPCC) Express environment.
(JTAPI) client version on the Cisco Customer Response Solutions (CRS) server when communicating with
different session partners in a Cisco IP Contact Center (IPCC) Express environment.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Q. How do I manually check the JTAPI client version on the Cisco
Response Solutions (CRS) server?
Response Solutions (CRS) server?
A. JTAPI supports telephony call control. It is an extensible API designed to scale for use in a
range of domains, from first−party call control in a consumer device to third−party call
control in large distributed contact centers.
range of domains, from first−party call control in a consumer device to third−party call
control in large distributed contact centers.
The JTAPI client is used in order to communicate between the CRS server and the Cisco
CallManager, or between a CRS server and the Cisco Agent Desktop within Cisco IPCC
Express. You must verify the version of the JTAPI client on both the CRS server and the
Cisco CallManager, or on both the CRS server and the Cisco Agent Desktop are the same. If
the JTAPI client(s) are different, several problems can appear. These problems can include
dropped calls, an incorrect agent state, or the agents cannot log in.
CallManager, or between a CRS server and the Cisco Agent Desktop within Cisco IPCC
Express. You must verify the version of the JTAPI client on both the CRS server and the
Cisco CallManager, or on both the CRS server and the Cisco Agent Desktop are the same. If
the JTAPI client(s) are different, several problems can appear. These problems can include
dropped calls, an incorrect agent state, or the agents cannot log in.
In order to manually verify the JTAPI client version on the CRS server when communicating
with the Cisco CallManager, complete these steps:
with the Cisco CallManager, complete these steps:
On the CRS server, launch a DOS window.
1.
Change the directory to
C:\WINNT\java\lib
.
2.
Type jview /cp jtapi.jar CiscoJtapiVersion.
3.
Press Enter.
4.
This is the command sequence:
5.
In order to manually verify the JTAPI client version on the CRS server when communicating