CTI Server Message Reference Guide (Protocol 24), Release 12.6(1)
CTI Server Message Reference Guide (Protocol 24), Release 12.6(1)
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (1721R)
© 1994–2021 Cisco Systems, Inc. All rights reserved.
CONTENTS
InvokeIDs 9
Heartbeat Messages 9
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
iii
Contents
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
iv
Contents
Session Maintenance 46
Session Termination 48
PG and CTI Server Graceful Shutdown 49
STANDBY_ACTIVE_EVENT Message 49
ACTIVE_MAINTENANCE_REQ Message 49
ACTIVE_MAINTENANCE_RESP Message 50
ACTIVE_MAINTENANCE_EVENT Message 50
STOPPING_REQUESTS_TO_THIS_SIDE_IND Message 51
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
v
Contents
AGENT_PRE_CALL_ABORT_EVENT 113
RTP_STARTED_EVENT 114
RTP_STOPPED_EVENT 116
NETWORK_RECORDING_STARTED_EVENT 117
NETWORK_RECORDING_ENDED_EVENT 118
NETWORK_RECORDING_FAILED_EVENT 119
NETWORK_RECORDING_TARGET_INFO_EVENT 120
All Events Service 123
CALL_DELIVERED_EVENT 123
CALL_TRANSLATION_ROUTE_EVENT 123
Peripheral Monitor Service 125
MONITOR_START_REQ 126
MONITOR_STOP_REQ 128
CHANGE_MONITOR_MASK_REQ 129
Client Monitor Service 130
CLIENT_SESSION_OPENED_EVENT 131
CLIENT_SESSION_CLOSED_EVENT 132
SESSION_MONITOR_START_REQ 133
SESSION_MONITOR_STOP_REQ 135
Supervisor Service 136
SUPERVISE_CALL_REQ 136
EMERGENCY_CALL_REQ 140
EMERGENCY_CALL_EVENT 143
AGENT_TEAM_CONFIG_EVENT 144
LIST_AGENT_TEAM_REQ 146
MONITOR_AGENT_TEAM_START_REQ 147
MONITOR_AGENT_TEAM_STOP_REQ 148
Call Data Update Service 149
SET_CALL_DATA_REQ 149
RELEASE_CALL_REQ 153
SET_DEVICE_ATTRIBUTES_REQ 154
Miscellaneous Service 156
SYSTEM_EVENT 157
CLIENT_EVENT_REPORT_REQ 159
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
vi
Contents
USER_MESSAGE_REQ 160
USER_MESSAGE_EVENT 163
QUERY_AGENT_STATISTICS_REQ 163
QUERY_SKILL_GROUP_STATISTICS_REQ 175
REGISTER_VARIABLES_REQ 197
SET_APP_DATA_REQ 199
START_RECORDING_REQ 201
STOP_RECORDING_REQ 205
AGENT_DESK_SETTINGS_REQ 208
SET_AGENT_SERVICE_DATA_REQ 212
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
vii
Contents
AGENT_GREETING_CONTROL_REQ 286
START_NETWORK_RECORDING_REQ 287
STOP_NETWORK_RECORDING_REQ 288
Server Service 290
REGISTER_SERVICE_REQ 290
UNREGISTER_SERVICE_REQ 291
Configuration Acquisition Messages 292
Configuration keys 292
Initial configuration acquisition 293
Update messages 293
Message Order 293
CONFIG_REQUEST_KEY_EVENT 293
CONFIG_KEY_EVENT 294
CONFIG_REQUEST_EVENT 295
CONFIG_BEGIN_EVENT 299
CONFIG_SERVICE_EVENT 300
CONFIG_SKILL_GROUP_EVENT 302
CONFIG_AGENT_EVENT 304
CONFIG_TERMINAL_EVENT 306
CONFIG_AGENT_DESK_SETTINGS_EVENT 307
CONFIG_PERIPHERAL_EVENT 310
CONFIG_DEVICE_EVENT 310
CONFIG_CALL_TYPE_EVENT 312
CONFIG_MRD_EVENT 312
CONFIG_AGENT_SERVICE_EVENT 313
CONFIG_END_EVENT 315
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
viii
Contents
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
ix
Contents
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
x
Contents
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xi
Contents
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xii
Preface
• Change History, on page xiii
• About This Guide, on page xiii
• Audience, on page xiv
• Related Documents, on page xiv
• Communications, Services, and Additional Information, on page xiv
• Field Notice, on page xiv
• Documentation Feedback, on page xv
• Conventions, on page xv
Change History
Changes Section Date
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xiii
Preface
Audience
Audience
This manual is for system integrators and programmers who want to integrate CTI client applications with
Unified CCE.
Related Documents
Field Notice
Cisco publishes Field Notices to notify customers and partners about significant issues in Cisco products that
typically require an upgrade, workaround, or other user action. For more information, see Product Field Notice
Summary at https://www.cisco.com/c/en/us/support/web/tsd-products-field-notice-summary.html.
You can create custom subscriptions for Cisco products, series, or software to receive email alerts or consume
RSS feeds when new announcements are released for the following notices:
• Cisco Security Advisories
• Field Notices
• End-of-Sale or Support Announcements
• Software Updates
• Updates to Known Bugs
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xiv
Preface
Documentation Feedback
Documentation Feedback
To provide comments about this document, send an email message to the following address:
[email protected]
We appreciate your comments.
Conventions
This document uses the following conventions:
Convention Description
boldface font Boldface font is used to indicate commands, such as user entries, keys, buttons,
folder names, and submenu names.
For example:
• Choose Edit > Find.
• Click Finish.
window font Window font, such as Courier, is used for the following:
• Text as it appears in code or that the window displays. Example:
<html><title>Cisco Systems, Inc. </title></html>
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xv
Preface
Conventions
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
xvi
CHAPTER 1
CTI Server Overview
• How CTI Server Works, on page 1
• Unified CCE Call Processing, on page 2
• CTI Server Configurations, on page 4
• CTI Server Message Set, on page 7
CTI Server forwards pre-routes indications to CTI application servers. Pre-route indications identify the caller
and provide associated call attributes to applications before the call is connected to an agent or Voice Response
Unit (VRU).
In a direct desktop application environment, call event information is delivered to the targeted desktop when
the call is delivered. CTI Server reports call events and agent work state changes to the application as they
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
1
CTI Server Overview
Unified CCE Call Processing
occur through each stage of the call flow. This lasts from when a call arrives at an answering resource
(Automatic Call Distributor (ACD), Private Branch Exchange (PBX), or VRU), until the caller hangs up.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
2
CTI Server Overview
Post Route Call
entered digits collected in the network and any other call data set by the routing script is also sent to the
PG in the message.
6. The call arrives at the chosen ACD and is monitored by the Peripheral Gateway (PG).
7. The ACD, recognizing the “special” nature of the call, performs a Route Request to collect the call’s
ultimate target.
8. The ultimate target and other “call context” data determined by Unified CCE in step 5 is returned by
the PG in a Route Response
9. The ACD routes the call to the ultimate target. As in the “normal” call case, the PG is informed of the
call’s state changes as they occur. Eventually the call is connected to an agent.
10. The agent may either handle the call directly or transfer the call to another agent.
11. Upon completion of the call, a Termination Call Detail record is created and sent to the CC database.
Transfer Call
1. In the case of a “local” transfer, the agent handling a call directs the ACD to transfer the call to another
destination on the same ACD.
2. The peripheral gateway (PG) is informed of the various events associated with the call’s transfer.
3. Call transfers are handled differently by different types of ACDs. In general a new logical call is created
for the resulting call. A Termination Call Detail record is created for the original call.
4. The new call is connected to an agent and is then handled or transferred (again) like any other call.
In the case of a “remote” transfer, the call leaves the realm of the monitoring PG and the original call is
terminated in the usual way. The Unified CCE monitor the ACD and the "remote" transfer takes place into
this ACD, the new call is monitored on that ACD's PG when the call arrives. This new call has none of the
call context of the original call.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
3
CTI Server Overview
Conference Call
Depending upon the particular ACD’s capabilities and tie-line configuration, some ACDs may be set up to
affect call transfers using the post route and translation route features previously described. In this case, the
call context is preserved by being sent through Unified CCE via the route request and translation route
mechanisms to the remote PG, and is thus available to the CTI Client, if any, associated with the destination
device.
Conference Call
Like call transfers, call conferences are handled differently by different types of ACDs and may involve the
creation of several calls that are all linked together.
Simplex/Duplex Configuration
In simplex configurations, there is one CTI Server on the local network with the CTI clients. In duplex
configurations, two CTI Servers are present. There may be other equipment (for example, ACDs) on the
network as well.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
4
CTI Server Overview
CTI Bridge Configuration
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
5
CTI Server Overview
CTI Bridge Configuration
CTI Bridge applications are interested in all call and agent state events that are occurring on the ACD. By
comparison, agent workstation applications are interested only in the events associated with a particular agent
device. The CTI Bridge application is a specially written program that converts or adapts the CTI messages
into another format, as needed. A single CTI Bridge application provides such translation services for multiple
agent desktops. The CTI Bridge application can be designed to interface with CTI Servers or similar applications
on systems that are already in use in the call center.
Some examples of CTI Bridge applications include:
• Message converter applications. For example, an application may convert the CTI message set to the
message set of a foreign telephony server.
• Server-to-server communication applications. For example, an application may enable the CTI Server
to speak directly to a help desk application’s middle tier server.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
6
CTI Server Overview
CTI Server Message Set
Category Description
Call Data Update Messages related to CTI client modification of call data.
Client Control Messages related to the direct control of agent state (for example, sign-in,
sign-out) and control of inbound and outbound calls.
Related Topics
Session Management, on page 35
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
7
CTI Server Overview
CTI Server Message Set
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
8
CHAPTER 2
CTI Client Application Guidelines
• InvokeIDs, on page 9
• Heartbeat Messages, on page 9
• Generic vs ACD-Specific Applications, on page 10
• Message Masks, on page 10
• Message Order, on page 10
• Definitions of Symbolic Constants, on page 10
• Side AB Selection TCPIP Connections, on page 10
• Alignment of Data Elements, on page 11
• CTI Operations During Unified CCE Failures, on page 11
InvokeIDs
The CTI protocol provides an integer InvokeID field in each request message. This field is always returned
in the corresponding response message. You can set the Invoke ID to a unique value for each request you sent
to the server. This allows you to have multiple requests outstanding and to correctly determine which request’s
response has been received. For example, you can implement a simple counter that is incremented with each
request.
Heartbeat Messages
The Heartbeat Interval designates the time in seconds between sending heartbeat messages to the CTI Server.
A Heartbeat Interval of -1 disables heartbeats. The default setting for application developers is -1.
You must determine the appropriate heartbeat interval for a production environment -- it depends on the
application and the environment. It should represent a reasonable balance between the speed of failure detection
and the network bandwidth consumed by heartbeat messages and their corresponding confirmations.
In cases where there are very few CTI clients, such as a CTI Bridge, the minimum heartbeat interval of 5
seconds should suffice. Workstation (desktop) clients should use a much larger heartbeat interval (at least 90
seconds), since these clients typically number into the hundreds and possibly thousands. However, if the
TCP/IP time-out period is adequate, or if there is nothing the application can do even if it is aware that
something is wrong, it may be appropriate to disable heartbeats even in a production environment.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
9
CTI Client Application Guidelines
Generic vs ACD-Specific Applications
Message Masks
CTI Server can provide much more real-time data than the typical CTI client needs. The CTI Server provides
message masks to suppress the transmission of unneeded data and avoid wasting network bandwidth. You
should carefully consider the network impact of the expected number of simultaneously connected CTI clients
before deploying a CTI client application that unmasks a large number of messages.
Message Order
When an event occurs that would conceptually result in two or more event messages being generated at the
same time, the CTI client must be prepared to handle the messages arriving in any order. For example, an
agent answering an inbound call might generate both a CALL_ESTABLISHED_EVENT and an
AGENT_STATE_EVENT message. These may be received by a CTI client in either order, and other event
messages may be sent to the client in between. Also, since ACD event data is often obtained from multiple
sources, there can be a noticeable delay between event reports that logically occur at the same time.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
10
CTI Client Application Guidelines
Alignment of Data Elements
hundreds of clients attempting to connect simultaneously). The algorithm is terminated as soon as a successful
TCP/IP connection is achieved:
1. Attempt to connect to the same side as the last successful connection.
2. Attempt to connect to the opposite side.
3. Generate a random integer number N between 0 and the expected number of CTI clients divided by 10.
4. Wait for N seconds. This step helps avoid “rush hour” traffic when all clients at a site are reconnecting
simultaneously.
5. Attempt to connect to the same side as the last successful connection.
6. Attempt to connect to the opposite side.
7. Wait for 15 seconds.
8. Attempt to connect to the same side as the last successful connection.
9. Attempt to connect to the opposite side.
10. Wait for 30 seconds.
11. Attempt to connect to the same side as the last successful connection.
12. Attempt to connect to the opposite side.
13. Wait for 60 seconds.
14. Attempt to connect to the same side as the last successful connection.
15. Attempt to connect to the opposite side.
16. Wait for 120 seconds.
17. Repeat steps 14 – 16 until a connection is achieved.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
11
CTI Client Application Guidelines
CTI Operations During Unified CCE Failures
• A failure of the data link or related software between the ACD and the Unified CCE will cause applications
not to receive event messages for the duration of the outage. This type of failure is reported to all CTI
clients via a SYSTEM_EVENT indicating that the peripheral (ACD) is offline. In addition, the Unified
CCE may take additional action depending upon the type of failure and the ACD involved. In many
cases, an END_CALL_EVENT will be sent immediately for every call that was in progress, even though
the actual voice calls may still be in progress. When normal operation is restored, calls that are in progress
may or may not have their call events reported, depending upon the particular type of ACD. If so, a new
BEGIN_CALL_EVENT is sent for each call that will have event reporting resumed. In other cases, the
calls will be allowed to linger for a short time after the failure without sending an END_CALL_EVENT.
If the data link is restored within the short time interval, normal call event reporting continues (although
events that occurred during the outage are not reported and the call may now be in a different state). If
normal operation is not restored within the allotted time an END_CALL_EVENT is then sent for each
call.
• A failure of the datalink between the Unified CCE Peripheral Gateway and the Central Controller does
not prevent event messages, however, the failure does prevent use of the Unified CCE post-routing and
translation-routing features.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
12
CHAPTER 3
Messaging Conventions
• CTI Message Convention, on page 13
• Message Types, on page 13
• Data Types, on page 28
• Message Formats, on page 31
• Floating Fields, on page 31
• Call Event Data, on page 32
• Failure Indication Messages, on page 34
Message Types
This table defines the complete CTI server message set. The messages are described in greater detail in the
remainder of this document. The length of the largest possible message (including the message header) defined
by this protocol is 12500 bytes.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
13
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
14
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
15
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
16
Messaging Conventions
Message Types
66 to 77 Reserved Reserved
80 to 81 Reserved Reserved
87 to 90 Reserved Reserved
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
17
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
18
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
19
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
20
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
21
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
22
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
23
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
24
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
25
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
26
Messaging Conventions
Message Types
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
27
Messaging Conventions
Data Types
Data Types
This table lists the data types that define fields within messages. All numeric data longer than 1 byte are sent
in order of most significant byte to least significant byte. This is the canonical network byte order defined by
TCP/IP standards.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
28
Messaging Conventions
MHDR Data Type
MessageLength The length of the message in bytes, excluding the size UINT 4
of the message header (the first 8 bytes).
MessageType The type of message. This value determines the format UINT 4
of the remainder of the message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
29
Messaging Conventions
NAMEDARRAY Data Type
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
30
Messaging Conventions
Message Formats
TaskGroupHigh The most significant 4 bytes of the Task Group ID. INT 4
The Task Group ID links multiple Termination Call
Detail (TCD) records together for reporting purposes.
Use this when the same customer interaction involves
multiple tasks over time. For example, this might
happen if an agent stops the work and then another
agent restarts it.
TaskGroupLow The least significant 4 bytes of the Task Group ID. INT 4
Message Formats
Messages contain either a fixed part only or a fixed part and a floating part. The fixed part of a message
contains the message header and all required, fixed length fields. The variable part of a message immediately
follows the fixed part. It contains one or more floating fields that are optional and/or variable in length. The
message type field in the message header determines the format of the message, and therefore indicates if the
message includes a floating part and what types of floating fields may appear within it.
Figure 4: CTI Server Message Format
Floating Fields
Each floating field has the same format. The field begins with a two-byte tag, which identifies the field type.
Following the tag is a two-byte field length, which indicates the number of bytes of data in the field (excluding
the tag and field length). The data immediately follows the FieldLength. The maximum size listed for each
floating field is the maximum number of data bytes allowed. It does not include the tag and field length bytes.
For string data, it includes the null termination byte.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
31
Messaging Conventions
Call Event Data
Floating fields are packed together in the floating part of the message. The tag of one floating field immediately
follows the data of the previous field. The message length (in the message header) indicates the end of the
message. This figure shows the format of a floating field.
Figure 5: CTI Server Floating Field Format
Within the floating part, floating fields may appear in any order. In general, each floating field appears only
once unless the field is a member of a list. In this case, a fixed field in the message indicates the number of
list entries present. This table defines the format of the floating field:
For a list of possible floating field tag values, see the Tag Values table.
Related Topics
Tag Values, on page 328
Device IDs
The Call Event messages detailed later in this document typically provide several different device ID fields.
Depending upon the type of peripheral and the nature of the event, the device ID may represent a Trunk
number, a Trunk Group number, or an agent teleset number (extension). Some peripheral types may not
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
32
Messaging Conventions
CTI Client History
provide a device ID for one or more fields. To handle these situations, the Call Event messages provide device
IDs using two fields: a fixed field indicating whether or not the device ID was provided and enumerating the
type of device identified, and a floating field containing the device ID (if provided).
Call Identification
CTI Server uses the CSTA method of identifying calls. A numeric ConnectionCallID identifies a call; each
connection of a device to that call is identified by a ConnectionDeviceID string and an enumerated
ConnectionDeviceIDType value. All call related messages identify the ConnectionCallID as well as the
ConnectionDeviceIDType and ConnectionDeviceID of the call connection that is the subject of the event.
Figure 6: Sample CSTA Call/Device/ConnectionID Values
A ConnectionDeviceID uniquely identifies a call connection. However, it cannot directly identify the connected
device; use other event message fields for that purpose. In some cases, the ConnectionDeviceID may simply
be the ID of the connected device, the connected deviceID with additional identifying data included, or a
string that does not contain the deviceID at all. A valid CTI Server application can make no assumption about
the content or format of a ConnectionDeviceID.
Occasionally, both the ConnectionDeviceID and the numeric ConnectionCallID are required in order to
properly identify the subject call. This occurs when the ACD uses the ConnectionCallID value from an ACD
call as the ConnectionCallID value for any related consultative calls. This poses two particularly significant
requirements for applications: they must be able to keep track of two calls with the same numeric
ConnectionCallID value, and they must be able to decide which of the two calls is being referenced by any
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
33
Messaging Conventions
Failure Indication Messages
given call event message. These requirements are relatively easy to implement by keeping track of the
ConnectionDeviceIDs associated with each call. The call that has a ConnectionDeviceID that matches the
ConnectionDeviceID provided in the call event message is the call that is the subject of the event. The only
difficult case is determining which call is the subject when a new call connection is created. For this case, the
following rule applies:
• When more than one call with the same ConnectionCallID value exists, the connection being created by
a CALL_ESTABLISHED_ EVENT shall apply to the call that does not yet have a destination connection
established.
Typically, when this occurs, one call will have been the subject of a prior CALL_ESTABLISHED_EVENT
and will have two connections; the other will have only one originating connection. The
CALL_ESTABLISHED_EVENT will therefore create the second connection on that call. It should never be
the case that both calls have already been the subject of a CALL_ESTABLISHED_EVENT.
FailureCode A Status Code value specifying the reason that the USHORT 2
request failed.
The CTI Server may use the FAILURE_EVENT message to asynchronously indicate a failure or error condition
to the CTI client. The format of the FAILURE_EVENT message is defined in this table:
Status A status code indicating the cause of the failure. The UINT 4
possible status codes are defined in the Failure
Indication Message status code table.
Related Topics
Failure Indication Message Status Codes, on page 319
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
34
CHAPTER 4
Session Management
• Configuring TCPIP Transport Services, on page 35
• Connection Management, on page 35
• Session Initialization, on page 35
• Session Maintenance, on page 46
• Session Termination, on page 48
• PG and CTI Server Graceful Shutdown, on page 49
Connection Management
You should configure the CTI clients with two sets of hostname/port number pairs; one for the IP address and
TCP port number of the CTI Server on side “A” and the other for the corresponding CTI Server on side “B”.
The CTI clients should alternately attempt to connect to each side until a connection is established. Once a
connection between the CTI client and the CTI Server has been established, the connection remains in place
until a failure occurs or the client closes the connection. Connection failures may be detected by the TCP layer
or by the heartbeat message mechanism described later in this chapter. If a failure occurs, the CTI client should
again alternately attempt to establish a connection to either side until a new connection is established.
Session Initialization
Once a TCP connection has been established, you can attempt to initialize a communications session by
sending an OPEN_REQ message to the CTI Server. The CTI Server responds with an OPEN_CONF message
to confirm the successful establishment of a session. This figure depicts the message flow.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
35
Session Management
CTI Service Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
36
Session Management
CTI Service Masks
Unused 0x00004000
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
37
Session Management
OPEN_REQ Message
OPEN_REQ Message
This table defines the OPEN_REQ message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
38
Session Management
OPEN_REQ Message
Floating Part
AgentID The agent’s ACD sign-in ID. For CLIENT EVENTS STRING 12
service, the CTI Client must provide at least one of
AgentExtension, AgentID, or AgentInstrument.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
39
Session Management
Unsolicited Call Event Message Masks
Related Topics
CONFIG_REQUEST_EVENT, on page 295
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
40
Session Management
Unsolicited Call Event Message Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
41
Session Management
Agent State Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
42
Session Management
OPEN_CONF Message
AGENT_WORK_NOT_READY_MASK Set when client wishes to receive “work not ready” 0x00000020
AGENT_STATE_EVENT messages.
OPEN_CONF Message
This table defines the OPEN_CONF message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
43
Session Management
OPEN_CONF Message
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
44
Session Management
OPEN_CONF Message
Floating Part
AgentID (Client Events The agent’s ACD sign-in ID, when STRING 12
Service Only) Client Events service has been granted
and the agent is currently signed in on
the ACD.
If the CTI Server determines that a new session should not be opened, it responds to the OPEN_REQ message
with a FAILURE_CONF message. If necessary floating data has not been provided, a FAILURE_CONF
message is returned with the status code set to E_CTI_REQUIRED_DATA_MISSING.
A CTI client might try to open a session for Client Events service and the provide device information items
that are inconsistent with each other. Then, a FAILURE_CONF message is returned with the status code set
to E_CTI_INCONSISTENT_AGENT_DATA. If the ACD device is already associated with a different CTI
client, the CTI Server refuses to open the new session and returns a FAILURE_CONF message. The status
code in the message is set to E_CTI_DEVICE_IN_USE. If the ACD device is already associated with the
same CTI client, the existing session is terminated and the CTI Server opens the new session.
During an OPEN_REQ of an ALL_EVENTS client session, the CTI Server responds with an OPEN_CONF
message to confirm the successful establishment of a session. In addition to the OPEN_CONF,
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
45
Session Management
Session Maintenance
SYSTEM_EVENT messages are sent to the ALL_EVENTS client, per peripheral, to indicate the status of
each peripheral associated with the PG.
If the CTI Server rejects an OPEN_REQ message, reset the TCP connection. The status code received in the
rejection indicates the message data to correct before retrying to establish a session.
Normally, you receive a response to the OPEN_REQ message within 5 seconds. Some failure scenarios cause
all connected CTI clients to lose their connection to the CTI Server. This causes them to then reconnect and
reopen their sessions. In the worst case situations, there could be hundreds or even thousands of simultaneous
OPEN_REQ messages sent to the CTI Server, causing significant response delays. For this reason, allow at
least 30 seconds before considering a lack of response to the OPEN_REQ message as a failure to open the
session. In larger configurations of more than 500 clients, allow 60 seconds or more. Then reset the TCP
connection, reconnect, and retry the OPEN_REQ after a short delay.
Related Topics
Constants and Status Codes, on page 317
Session Maintenance
Compared to some other protocols, TCP/IP is relatively slow at detecting and recovering from communication
path failures. If an IP packet is dropped within the network, retransmission does not occur until the sender
notices a time-out. This time-out period is long enough to allow for worst-case round-trip delays and network
congestion. If you need more rapid error detection, you may send an optional HEARTBEAT_REQ message
to the CTI Server whenever no heartbeat interval messages have been sent. Upon receipt of a
HEARTBEAT_REQ message, the CTI Server immediately responds with a HEARTBEAT_CONF message.
If three heartbeats go unconfirmed, the CTI client declares a session failure and resets the TCP connection.
You determine the appropriate heartbeat interval for a production environment—It depends on the application
and the environment. Find a reasonable balance between the speed of failure detection and the network
bandwidth consumed by heartbeat messages and confirmations. In cases with few CTI clients, such as a CTI
Bridge, the minimum heartbeat interval of 5 seconds should suffice. Workstation (desktop) clients usually
need a larger heartbeat interval (at least 90 seconds), since there are typically hundreds or thousands of clients.
A Heartbeat Interval of –1 disables heartbeats. The default setting for application developers is –1. However,
if the TCP/IP time-out period is adequate or if the application can do nothing during a failure, you can choose
to disable heartbeats in a production environment.
This figure depicts the heartbeat message flow.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
46
Session Management
Session Maintenance
The CTI Server does not begin HEARTBEAT_REQ messages. The CTI Server detects failures using the
IdleTimeout value from the OPEN_REQ message. If you are using heartbeat messages, the CTI client should
set the IdleTimeout value to four times the heartbeat interval. If the CTI Server receives no messages (including
HEARTBEAT_REQ messages) for this period, the CTI Server declares a session failure and resets the TCP
connection.
The CTI Server may respond to a HEARTBEAT_REQ message with a FAILURE_CONF. This indicates to
the CTI client that the CTI Server is off-line, and the CTI client resets the TCP connection.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
47
Session Management
Session Termination
Session Termination
The CTI client may begin the graceful termination of a communication session by sending a CLOSE_REQ
message. The CTI Server responds with a CLOSE_CONF message. Upon receipt of the CLOSE_CONF
message, the CTI client can reset the TCP connection. The CTI client should wait up to 5 seconds for the
CLOSE_CONF message before resetting the connection.
The CTI Server may indicate that it no longer wishes to communicate with the client through an unsolicited
FAILURE_EVENT message. The Status field in the message is set to E_CTI_CTI_SERVER_OFFLINE.
Upon receipt of this message, the CTI client closes the session.
The CLOSE_REQ message includes a status code that indicates the reason for closing the session. You can
set the status code to one of the following:
• E_CTI_NO_ERROR—If the CTI client began the request to end the session.
• E_CTI_CTI_SERVER_OFFLINE—If the CTI Server is no longer online.
• E_CTI_TIMEOUT—If the CTI Server does not respond to a request message within the time-out period.
Status A status code indicating the reason for closing the UINT 4
session.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
48
Session Management
PG and CTI Server Graceful Shutdown
Related Topics
Failure Indication Messages, on page 34
STANDBY_ACTIVE_EVENT Message
Standby CTI Server informs the clients when it is changing from Standby to Active.
ACTIVE_MAINTENANCE_REQ Message
This request is sent from Active CTI Server to all the clients who have opened the session with the Service
Mask 0x02000000. This request is to affirm if the client is ready to accept the PG going into Maintainence
Mode.
This table defines the ACTIVE_MAINTENANCE_RESP message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
49
Session Management
ACTIVE_MAINTENANCE_RESP Message
ACTIVE_MAINTENANCE_RESP Message
This is a response from clients for ACTIVE_MAINTENANCE_REQ_MSG request. This response indicates
whether or not it accepts the PG Maintenance Mode. The CTI Server expects this response with in 5secs from
receiving the request. If there is no response received, then it is considered as the negative acknowledgement
from the client
ACTIVE_MAINTENANCE_EVENT Message
This event indicates the final decision of the PG and whether it is going to Maintenance Mode or not. This
decision depends on the responses from all the clients to which the ACTIVE_MAINTENANCE_REQ_MSG
request message is sent. If any client negatively acknowledged the ACTIVE_MAINTENANCE_REQ_MSG,
PG Maintenance Mode will be cancelled. This event is sent from the Active CTI Server.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
50
Session Management
STOPPING_REQUESTS_TO_THIS_SIDE_IND Message
STOPPING_REQUESTS_TO_THIS_SIDE_IND Message
Clients send this message to the CTI Server that went to Maintenance Mode to indicate that it will no longer
send any requests to this side. Typically, clients are expected to send this message after it receives the
STANDBY_ACTIVE_EVENT_MSG from the Standby CTI Server. Once CTI Server in Maintenance Mode
receives this message, it will disconnect the socket. CTI Server expects this message with in 5secs from the
time it sent ACTIVE_MAINTENANCE_EVENT_MSG to indicate that it is continuing with the Maintenance
Mode
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
51
Session Management
STOPPING_REQUESTS_TO_THIS_SIDE_IND Message
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
52
CHAPTER 5
Application Level Interfaces
• CTI Server Application Level Interfaces, on page 53
• Client Events Service, on page 54
• All Events Service, on page 123
• Peripheral Monitor Service, on page 125
• Client Monitor Service, on page 130
• Supervisor Service, on page 136
• Call Data Update Service, on page 149
• Miscellaneous Service, on page 156
• Connection Monitor Service, on page 214
• Client Control Service, on page 214
• Server Service, on page 290
• Configuration Acquisition Messages, on page 292
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
53
Application Level Interfaces
Client Events Service
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
54
Application Level Interfaces
Client Events Service
The content of most of the Call Event message is event-specific and, often, peripheral-specific. Some ACDs
may not provide all these events.
For peripheral-specific Call Event message information, see the CTI OS Developer Guide for Cisco Unified
ICM at https://www.cisco.com/c/en/us/support/customer-collaboration/computer-telephony-integration-option/
products-programming-reference-guides-list.html.
The relative order of call event messages and any corresponding agent state change event messages is not
specified. An agent state event message for an agent in the “talking” state, for example, can be sent before or
after the corresponding call established event message.
This table lists the Client Events service messages.
BEGIN_CALL_EVENT When the CTI Server associates a call with the CTI client
END_CALL_EVENT When CTI Server dissolves association between a call and the
CTI Client
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
55
Application Level Interfaces
BEGIN_CALL_EVENT
CALL_ORIGINATED_EVENT Sent to CTI client upon initialization of a call from the peripheral
RTP_STARTED_EVENT Indicates that a Real Time Protocol (RTP) media stream has
started.
RTP_STOPPED_EVENT Indicates that a Real Time Protocol (RTP) media stream has
stopped
BEGIN_CALL_EVENT
When the CTI Server associates a call with the CTI client, it sends the client a BEGIN_CALL_EVENT
message. This message provides the call ID and the initial call context data. The combination of
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
56
Application Level Interfaces
BEGIN_CALL_EVENT
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
57
Application Level Interfaces
BEGIN_CALL_EVENT
… … … …
NamedVariable (optional) Call-related variable data that has a NAMED VAR 251
variable name defined in the Unified
CCE. There may be an arbitrary
number of NamedVariable and
NamedArray fields in the message,
subject to a combined total limit of
2000 bytes.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
58
Application Level Interfaces
END_CALL_EVENT
CTIClientTimestamp (optional) The date and time that the preceding TIME 4
CTIClientSignature was first
associated with the call. There may be
more than one CTIClientTimestamp
field in the message. (See
NumCTIClients.) This field always
immediately follows the
CTIClientSignature field to which it
refers.
Related Topics
CallType Values, on page 353
ConnectionDeviceIDType Values, on page 356
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
PeripheralType Values, on page 346
END_CALL_EVENT
The CTI Server sends an END_CALL_EVENT message to the CTI client when the association between a
call and the CTI client is dissolved. This message does not necessarily indicate that the subject call has been
terminated. The message indicates only that the CTI client is no longer responsible for processing the call and
is receiving no further call event messages for the call.
This table defines the format of the END_CALL_EVENT message: defines the format of the
END_CALL_EVENT message:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
59
Application Level Interfaces
CALL_AGENT_GREETING_EVENT
Fixed Part
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
PeripheralType Values, on page 346
CALL_AGENT_GREETING_EVENT
This message indicates if the agent greeting has started, finished, or failed after the Agent Greeting request
has been made. This table defines the format of the message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
60
Application Level Interfaces
CALL_AGENT_GREETING_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
61
Application Level Interfaces
CALL_DATA_UPDATE_EVENT
CALL_DATA_UPDATE_EVENT
The CTI Server sends a CALL_DATA_UPDATE_EVENT message to the CTI client when changes to the
call context data occur. In general, this message contains only the items that have changed. But, the message
always contains all ECC variables that are associated with the call. Each time a client receives this message,
the client must replace any stored ECC variables with the ECC variables from this message.
The initial call context is provided in the BEGIN_CALL_EVENT message. This table defines the
CALL_DATA_UPDATE_EVENT message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
62
Application Level Interfaces
CALL_DATA_UPDATE_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
63
Application Level Interfaces
CALL_DATA_UPDATE_EVENT
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
64
Application Level Interfaces
CALL_DATA_UPDATE_EVENT
Related Topics
CallType Values, on page 353
ConnectionDeviceIDType Values, on page 356
NAMEDVAR Data Type, on page 29
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
65
Application Level Interfaces
CALL_DELIVERED_EVENT
CALL_DELIVERED_EVENT
The CTI Server may send a CALL_DELIVERED_EVENT message to the CTI client in two cases:
• A call arrives at the agent’s teleset.
• An inbound ACD trunk is seized and the client has the All Events service enabled.
The LocalConnectionState field indicates which case applies. This table defines the
CALL_DELIVERED_EVENT message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
66
Application Level Interfaces
CALL_DELIVERED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
67
Application Level Interfaces
CALL_DELIVERED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
68
Application Level Interfaces
CALL_DELIVERED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
69
Application Level Interfaces
CALL_ESTABLISHED_EVENT
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
LocalConnectionState Values, on page 347
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
PeripheralType Values, on page 346
Special Values, on page 327
CALL_DELIVERED_EVENT, on page 66
CALL_ESTABLISHED_EVENT
When a call is answered at the agent’s teleset, the CTI Server may send a CALL_ESTABLISHED_EVENT
message to the CTI client. This table defines the CALL_ESTABLISHED_EVENT message:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
70
Application Level Interfaces
CALL_ESTABLISHED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
71
Application Level Interfaces
CALL_ESTABLISHED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
72
Application Level Interfaces
CALL_HELD_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_HELD_EVENT
The CTI Server may send a CALL_HELD_EVENT message to the CTI client when a call is placed on hold
at the agent’s teleset. This table defines the CALL_HELD_EVENT message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
73
Application Level Interfaces
CALL_HELD_EVENT
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
74
Application Level Interfaces
CALL_RETRIEVED_EVENT
CALL_RETRIEVED_EVENT
The CTI Server may send a CALL_RETRIEVED_EVENT message to the CTI client when a call previously
placed on hold at the agent’s teleset is resumed.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
75
Application Level Interfaces
CALL_CLEARED_EVENT
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CALL_CLEARED_EVENT
The CTI Server sends a CALL_CLEARED_EVENT message to the CTI client when a call is terminated,
usually when the last device disconnects from a call.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
76
Application Level Interfaces
CALL_CONNECTION_CLEARED_EVENT
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CALL_CONNECTION_CLEARED_EVENT
The CTI Server may send a CALL_CONNECTION_CLEARED_ EVENT message to the CTI client when
a party drops from a conference call.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
77
Application Level Interfaces
CALL_ORIGINATED_EVENT
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CALL_ORIGINATED_EVENT
The CTI Server may send a CALL_ORIGINATED_EVENT message to the CTI client when the peripheral
initiates an outbound call.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
78
Application Level Interfaces
CALL_ORIGINATED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
79
Application Level Interfaces
CALL_ORIGINATED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
80
Application Level Interfaces
CALL_FAILED_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_FAILED_EVENT
The CTI Server may send a CALL_FAILED_EVENT message to the CTI client when a call cannot be
completed.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
81
Application Level Interfaces
CALL_CONFERENCED_EVENT
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CALL_CONFERENCED_EVENT
The CTI Server may send a CALL_CONFERENCED_EVENT message to the CTI client when calls are
joined into a conference call.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
82
Application Level Interfaces
CALL_CONFERENCED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
83
Application Level Interfaces
CALL_CONFERENCED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
84
Application Level Interfaces
CALL_CONFERENCED_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
85
Application Level Interfaces
CALL_TRANSFERRED_EVENT
CALL_TRANSFERRED_EVENT
The CTI Server may send a CALL_TRANSFERRED_EVENT message to the CTI client when a call is
transferred to another destination.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
86
Application Level Interfaces
CALL_TRANSFERRED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
87
Application Level Interfaces
CALL_TRANSFERRED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
88
Application Level Interfaces
CALL_DIVERTED_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_DIVERTED_EVENT
The CTI Server may send a CALL_DIVERTED_EVENT message to the CTI client when a call is removed
from a previous delivery target.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
89
Application Level Interfaces
CALL_DIVERTED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
90
Application Level Interfaces
CALL_SERVICE_INITIATED_EVENT
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_SERVICE_INITIATED_EVENT
The CTI Server may send a CALL_SERVICE_INITIATED_EVENT message to the CTI client upon the
initiation of telecommunications service (“dial tone”) at the agent’s teleset.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
91
Application Level Interfaces
CALL_SERVICE_INITIATED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
92
Application Level Interfaces
CALL_SERVICE_INITIATED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
93
Application Level Interfaces
AGENT_STATE_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LineType Values, on page 356
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
AGENT_STATE_EVENT
An agent state change (such as logging on or becoming available to handle incoming calls) generates an
AGENT_STATE_EVENT message to the CTI client.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
94
Application Level Interfaces
AGENT_STATE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
95
Application Level Interfaces
AGENT_STATE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
96
Application Level Interfaces
AGENT_STATE_EVENT
An available agent is
eligible to be assigned a
task. Who can assign a
task to the agent is
determined by whether or
not the agent is Routable.
An agent is ICMAvailable
in MRD X if he is
available in X and
Routable with respect to
X. An agent is
ApplicationAvailable in
MRD X if he is available
in X and not Routable
with respect to X.
Otherwise an agent is
NotAvailable in MRD X.
The values are:
• NOT AVAILABLE
=0
• ICM AVAILABLE
=1
• APPLICATION
AVAILABLE = 2
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
97
Application Level Interfaces
AGENT_STATE_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
98
Application Level Interfaces
AGENT_STATE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
99
Application Level Interfaces
CALL_REACHED_NETWORK_EVENT
Related Topics
AgentState Values, on page 344
CALL_DELIVERED_EVENT, on page 66
PeripheralType Values, on page 346
Special Values, on page 327
CALL_REACHED_NETWORK_EVENT
The CTI Server may send a CALL_REACHED_NETWORK_EVENT message to the CTI client when an
outbound call is connected to another network.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
100
Application Level Interfaces
CALL_REACHED_NETWORK_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
101
Application Level Interfaces
CALL_QUEUED_EVENT
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
CALL_QUEUED_EVENT
The CTI Server may send a CALL_QUEUED_EVENT message to the CTI client when a call is placed in a
queue pending the availability of some resource.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
102
Application Level Interfaces
CALL_QUEUED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
103
Application Level Interfaces
CALL_QUEUED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
104
Application Level Interfaces
CALL_DEQUEUED_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_DEQUEUED_EVENT
The CTI Server may send a CALL_DEQUEUED_EVENT message to the CTI client when a call is removed
from a queue.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
105
Application Level Interfaces
CALL_DEQUEUED_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
106
Application Level Interfaces
CALL_DEQUEUED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
107
Application Level Interfaces
CALL_ATTRIBUTE_CHANGE_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
EventCause Values, on page 348
LocalConnectionState Values, on page 347
PeripheralType Values, on page 346
Special Values, on page 327
CALL_ATTRIBUTE_CHANGE_EVENT
Changes to certain key attributes of the call will generate a CALL_ATTRIBUTE_CHANGE_EVENT to the
client.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
108
Application Level Interfaces
AGENT_PRE_CALL_EVENT
Floating Part
AGENT_PRE_CALL_EVENT
An AGENT_PRE_CALL_EVENT message is generated when a call or task is routed to Enterprise Agent.
The message contains the call context data that is assigned to the call after it arrives at the agent’s desktop.
Unlike the translation route event message, which is only sent to All Event clients, the AGENT_PRE_CALL_
EVENT message is also sent to the targeted Client Events client, if any. Typically, the
AGENT_PRE_CALL_EVENT message is received before the BEGIN_ CALL_EVENT announcing the
arrival of the call at the agent’s device. Application developers should note that it is possible, but not typical,
for the call to arrive at the agent and to receive a BEGIN_CALL_EVENT message and other call event
messages for the call before the AGENT_PRE_CALL_EVENT message is received.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
109
Application Level Interfaces
AGENT_PRE_CALL_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
110
Application Level Interfaces
AGENT_PRE_CALL_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
111
Application Level Interfaces
AGENT_PRE_CALL_EVENT
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
112
Application Level Interfaces
AGENT_PRE_CALL_ABORT_EVENT
Related Topics
CALL_DELIVERED_EVENT, on page 66
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
Special Values, on page 327
AGENT_PRE_CALL_ABORT_EVENT
An AGENT_PRE_CALL_ABORT_EVENT message is generated when a call or task that was previously
announced via an AGENT_PRE_CALL_EVENT cannot be routed as intended (due to a busy or other error
condition detected during call routing) to Enterprise Agent. The AGENT_PRE_CALL_ABORT_ EVENT
message is sent to the to ALL_EVENTS client.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
113
Application Level Interfaces
RTP_STARTED_EVENT
RTP_STARTED_EVENT
The RTP_STARTED_EVENT message indicates that an RTP media stream has been started. There are two
media streams for audio media so there will be two RTP Started events, one indicating the input has started
(i.e. the phone is listening) and the other that the output has started (i.e. the outgoing media from the agent
phone has begun).
The RTP_STARTED_EVENT message will generally come up at the same time as the established event. It
also occurs when a call is retrieved from being on hold, and when the transfer or conference operations are
completed.
There is no guarantee of order of the RTP started events in relationship to the established and retrieved events.
The RTP started events may occur before or after the established event.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
114
Application Level Interfaces
RTP_STARTED_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
115
Application Level Interfaces
RTP_STOPPED_EVENT
RTP_STOPPED_EVENT
The RTP_STOPPED_EVENT message indicates that an RTP media has been stopped. There are two media
streams for audio media so there will be two RTP Stopped events, one indicating the input has started (i.e.
the phone is not listening) and the other that the output has started (i.e. the outgoing media from the agent
phone has stopped).
The RTP_STOPPED_EVENT will be received when the call is placed on hold, and when the call disconnects.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
116
Application Level Interfaces
NETWORK_RECORDING_STARTED_EVENT
Floating Part
NETWORK_RECORDING_STARTED_EVENT
This message will be sent by a CTI server to clients indicating start of recording at recording server.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
117
Application Level Interfaces
NETWORK_RECORDING_ENDED_EVENT
Fixed Part
Floating Part
NETWORK_RECORDING_ENDED_EVENT
This message will be sent by a CTI server to clients indicating recording ended at recording server.
Recording End is signaled either by Network Recording End event or by Call Cleared Event
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
118
Application Level Interfaces
NETWORK_RECORDING_FAILED_EVENT
Floating Part
NETWORK_RECORDING_FAILED_EVENT
This message will be sent by a CTI server to clients indicating recording failed at recording server.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
119
Application Level Interfaces
NETWORK_RECORDING_TARGET_INFO_EVENT
Floating Part
NETWORK_RECORDING_TARGET_INFO_EVENT
This message will be sent by a CTI server to recording initiator providing info about Recorder.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
120
Application Level Interfaces
NETWORK_RECORDING_TARGET_INFO_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
121
Application Level Interfaces
NETWORK_RECORDING_TARGET_INFO_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
122
Application Level Interfaces
All Events Service
CALL_DELIVERED_EVENT
In addition to the Client Events service CALL_DELIVERED_EVENT message, a CTI client with the All
Events service may also receive a CALL_DELIVERED_EVENT message when an inbound ACD trunk is
seized. The same message format is used in both cases; the LocalConnectionState field distinguishes between
the two cases. In this case, the LocalConnectionState is set to LCS_INITIATE.
CALL_TRANSLATION_ROUTE_EVENT
The CTI Server sends a CALL_TRANSLATION_ROUTE_EVENT message to the CTI client when a call
is routed to a peripheral monitored by the PG via a translation route. The message contains the call context
data that will be assigned to the call after it arrives at the peripheral.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
123
Application Level Interfaces
CALL_TRANSLATION_ROUTE_EVENT
Floating Part
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
124
Application Level Interfaces
Peripheral Monitor Service
Related Topics
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
125
Application Level Interfaces
MONITOR_START_REQ
CHANGE_MONITOR_MASK_ REQ When a call and agent state event mask is changed.
Related Topics
CALL_TRANSLATION_ROUTE_EVENT, on page 123
MONITOR_START_REQ
Use this message to create a new monitor for the given call or device.
This figure depicts the Monitor Start message flow.
Figure 10: Monitor Start Message Flow
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
126
Application Level Interfaces
MONITOR_START_REQ
Floating Part
When the requested device or call monitor has been created, the CTI Server responds to the CTI client with
the MONITOR_START_CONF message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
127
Application Level Interfaces
MONITOR_STOP_REQ
Related Topics
AgentState Values, on page 344
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
MONITOR_STOP_REQ
Use this message to terminate a call or device monitor. This figure depicts the Monitor Stop message flow.
Figure 11: Monitor Stop Message Flow
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
128
Application Level Interfaces
CHANGE_MONITOR_MASK_REQ
When the requested device or call monitor has been terminated, the CTI Server responds to the CTI client
with the MONITOR_STOP_CONF message.
CHANGE_MONITOR_MASK_REQ
Use this message to change the call and agent state change event masks used to filter messages from the given
call or device monitor. This figure depicts the Change Monitor Mask message flow.
Figure 12: Change Monitor Mask Message Flow
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
129
Application Level Interfaces
Client Monitor Service
When the requested device or call monitor masks have been updated, the CTI Server responds to the CTI
client with the CHANGE_MONITOR_MASK_CONF message.
Related Topics
AgentState Values, on page 344
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
130
Application Level Interfaces
CLIENT_SESSION_OPENED_EVENT
CLIENT_SESSION_OPENED_EVENT
This message indicates that a new CTI client session has been opened. One of these messages is sent for each
existing CTI client session to the newly opened session, as if those CTI clients had just opened their sessions.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
131
Application Level Interfaces
CLIENT_SESSION_CLOSED_EVENT
Related Topics
AgentState Values, on page 344
CTI Service Masks, on page 371
CLIENT_SESSION_CLOSED_EVENT
This message indicates that a CTI client session has been terminated.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
132
Application Level Interfaces
SESSION_MONITOR_START_REQ
Floating Part
SESSION_MONITOR_START_REQ
Use this message to initiate monitoring of the given CTI client session. This figure depicts the Session Monitor
Start message flow. The SESSION_MONITOR_START_REQ and SESSION_MONITOR_START_CONF
messages formats are defined in the tables given in the following.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
133
Application Level Interfaces
SESSION_MONITOR_START_REQ
When the requested session monitor has been created, the CTI Server responds to the CTI client with the
SESSION_MONITOR_START_CONF message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
134
Application Level Interfaces
SESSION_MONITOR_STOP_REQ
SESSION_MONITOR_STOP_REQ
Use this message to terminate monitoring of a CTI client session. This figure depicts the Session Monitor
stop message flow.
Figure 14: Session Monitor Stop Message Flow
When the requested CTI client session monitor terminates, the CTI Server responds to the CTI client with the
SESSION_MONITOR_STOP_CONF message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
135
Application Level Interfaces
Supervisor Service
Supervisor Service
The Supervisor service requests supervisor services when the client opens a CTI session.
CTI_SERVICE_SUPERVISOR service type will be used in addition to the existing Service types, and requires
CTI_SERVICE_CLIENT_EVENTS to be specified as well.
Supervisor services rely on the configuration of Agent Teams in the Unified CCE. When an agent opens a
session with CTI_SERVICE_SUPERVISOR service type requested, the CTI Server will check to see if the
agent is configured as a supervisor. If the agent is a supervisor, the CTI Server will open the session and send
the OPEN_CONF to the agent. Otherwise, the FAILURE_CONF message with the status code set to
E_CTI_FUNCTION_NOT_AVAILABLE will be sent to the requesting client.
The CTI Client that has been granted Supervisor Service receives notifications whenever agent team clients
request supervisor assistance or indicate that they are handling an emergency call. The following messages
are used by Supervisor Service clients to provide these notifications and to perform agent supervisory functions.
SUPERVISE_CALL_REQ
At any time, for monitoring quality of service, training, etc., a supervisor CTI client may send a
SUPERVISE_CALL_REQ message to the CTI Server to request barge-in or interception of a call. At end of
such call supervision, a supervisor CTI client should send SUPERVISE_CALL_REQ message with
SUPERVISOR_CLEAR as the SupervisorAction value to disconnect the supervisor’s device from the call.
The SUPERVISE_CALL_REQ message allows a supervisor CTI Client to supervise an agent’s call, either
through barge-in or interception. The client may select a specific agent call connection, or may select an
agent’s currently active call by specifying only the agent:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
136
Application Level Interfaces
SUPERVISE_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
137
Application Level Interfaces
SUPERVISE_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
138
Application Level Interfaces
SUPERVISE_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
139
Application Level Interfaces
EMERGENCY_CALL_REQ
Fixed Part
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
EMERGENCY_CALL_REQ
The EMERGENCY_CALL_REQ message indicates that a CTI Client is handling the indicated call as an
emergency call:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
140
Application Level Interfaces
EMERGENCY_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
141
Application Level Interfaces
EMERGENCY_CALL_REQ
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
142
Application Level Interfaces
EMERGENCY_CALL_EVENT
Related Topics
ConnectionDeviceIDType Values, on page 356
LineType Values, on page 356
EMERGENCY_CALL_EVENT
The EMERGENCY_CALL_EVENT message, defined below, notifies bridge clients that an agent is handling
the indicated call as an emergency call:
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
143
Application Level Interfaces
AGENT_TEAM_CONFIG_EVENT
Related Topics
ConnectionDeviceIDType Values, on page 356
AGENT_TEAM_CONFIG_EVENT
Once a supervisor CTI client session is opened, the CTI Server sends one or more
AGENT_TEAM_CONFIG_EVENT messages with the list of team members for that supervisor.
The CTI Server also sends out the AGENT_TEAM_CONFIG_EVENT when any change is made to the agent
team configuration.
The AGENT_TEAM_CONFIG_EVENT message contains the list of team members for a supervisor or
changes to the team configuration.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
144
Application Level Interfaces
AGENT_TEAM_CONFIG_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
145
Application Level Interfaces
LIST_AGENT_TEAM_REQ
LIST_AGENT_TEAM_REQ
A CTI Supervisor Client could use the LIST_AGENT_TEAM_REQ message to obtain the list of associated
agent teams. Once the list of agent teams is obtained, the supervisor could use
MONITOR_AGENT_TEAM_START_REQ to start monitoring agent teams. The agent states of the agent
team will be send to the requesting supervisor session until a MONITOR_AGENT_TEAM_STOP_REQ is
received.
When any change is made to the agent team configuration, an AGENT_TEAM_CONFIG_EVENT will be
sending out. If agent team and supervisor mapping are changed (add or remove), an
AGENT_TEAM_CONFIG_EVENT will be sending out with AgentFlags set to 0x0004 for supervisor.
The LIST_AGENT_TEAM_REQ message allows a CTI Supervisor Client to obtain the list of agent team
that the supervisor can monitor. The list should be pre-configured in the Agent Team Supervisor Table.
The LIST_AGENT_TEAM_CONF message contains the list of agent teams that associated with the requesting
supervisor.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
146
Application Level Interfaces
MONITOR_AGENT_TEAM_START_REQ
Floating Part
MONITOR_AGENT_TEAM_START_REQ
The MONITOR_AGENT_TEAM_START_REQ allows a CTI Supervisor Client to start monitoring agent
team.
When the request has been received, the CTI Server responds to the CTI Client with the
MONITOR_AGENT_TEAM_START_CONF message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
147
Application Level Interfaces
MONITOR_AGENT_TEAM_STOP_REQ
MONITOR_AGENT_TEAM_STOP_REQ
The MONITOR_AGENT_TEAM_STOP_REQ message allows a CTI Supervisor Client to stop monitoring
agent teams.
When the request has been received, the CTI Server responds to the CTI Client with the
MONITOR_AGENT_TEAM_STOP_CONF message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
148
Application Level Interfaces
Call Data Update Service
RELEASE_CALL_REQ To indicate that you are finished with a call and that
all call variable and call wrapup updates have been
made.
SET_DEVICE_ATTRIBUTES_REQ To set the default service, skill group, and call type
information associated with a calling device that is
defined in the Unified CCE Dialer_Port_Map database
table.
SET_CALL_DATA_REQ
Send this message to the CTI Server to set one or more call variables and/or call wrapup data. The combination
of ConnectionCallID, ConnectionDeviceIDType, and ConnectionDeviceID uniquely identify the call to be
operated upon. Variables not provided in the message are not affected. This figure depicts the Set Call Data
message flow
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
149
Application Level Interfaces
SET_CALL_DATA_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
150
Application Level Interfaces
SET_CALL_DATA_REQ
Floating Part
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
151
Application Level Interfaces
SET_CALL_DATA_REQ
When the requested call variables have been updated and the new values are guaranteed to remain set should
the CTI session be abnormally terminated, the CTI Server responds to the CTI client that requested the update
with the SET_CALL_DATA_CONF message.
Related Topics
CallType Values, on page 353
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
152
Application Level Interfaces
RELEASE_CALL_REQ
RELEASE_CALL_REQ
Send this message to the CTI Server to indicate that you are finished with a call and that all call variable and
call wrapup data updates have been made. This message does not disconnect the call. The combination of
ConnectionCallID, ConnectionDeviceIDType, and ConnectionDeviceID uniquely identify the call to be
operated upon. CTI clients with Call Data Update Service should use this message to let the call termination
record be logged in the Unified CCE central database prior to the expiration of the call wrapup data timer
(default value 2 minutes).
Figure 15: Release Call Message Flow
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
153
Application Level Interfaces
SET_DEVICE_ATTRIBUTES_REQ
Floating Part
The CTI Server responds to the CTI client with the RELEASE_CALL_CONF message.
Related Topics
ConnectionDeviceIDType Values, on page 356
SET_DEVICE_ATTRIBUTES_REQ
This message is sent by a CTI Client to set the default service, skill group, and call type information associated
with a calling device that is defined in the Unified CCE Dialer_Port_Map database table. The default attributes
are initially assigned to all subsequent calls that originate from that device, although the service, skill group,
and call type of any call may be modified during subsequent call handling. These tables define the
SET_DEVICE_ATTRIBUTES_REQ and SET_DEVICE_ATTRIBUTES_CONF messages.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
154
Application Level Interfaces
SET_DEVICE_ATTRIBUTES_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
155
Application Level Interfaces
Miscellaneous Service
Floating Part
When the requested default settings have been updated the CTI Server responds to the CTI Client that requested
the update with the SET_DEVICE_ATTRIBUTES_CONF message. A FAILURE_CONF message is returned
if the provided Service or SkillGroup values are invalid, or if the CallingDevice is not configured in the Unified
CCE Dialer_Port_Map database table.
Related Topics
CALL_DELIVERED_EVENT, on page 66
CallType Values, on page 353
ConnectionDeviceIDType Values, on page 356
Special Values, on page 327
Miscellaneous Service
The Miscellaneous service is provided to all connected CTI clients. This service consists of a variety of
unsolicited event messages and request/response paired messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
156
Application Level Interfaces
SYSTEM_EVENT
QUERY_AGENT_STATISTICS_ REQ To obtain the current call handling statistics for the
client’s agent.
QUERY_SKILL_GROUP_ STATISTICS_REQ To obtain the current call handling statistics for one
of the client agent’s skill groups.
SYSTEM_EVENT
System event messages include the current PG Status as well as data related to the specific event that has
occurred. You can use the PG Status as a general indication of the operational health of the PG. Normally
you need not be aware of any specific codes; a non-zero value indicates a component failure or data link
outage that prevents normal CTI operations.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
157
Application Level Interfaces
SYSTEM_EVENT
Floating Part
Related Topics
DeviceIDType Values, on page 352
PGStatusCode Values, on page 345
SystemEventID Values, on page 326
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
158
Application Level Interfaces
CLIENT_EVENT_REPORT_REQ
CLIENT_EVENT_REPORT_REQ
Send the CLIENT_EVENT_REPORT_REQ message to report significant events through the Unified CCE
Alarm subsystem. The Unified CCE Alarm subsystem allows simple textual event reports as well as an
object-oriented model that tracks the current state of named objects. The Unified CCE Alarm subsystem can
also forward these events as SNMP traps.
A CTI client that elects to report events with named objects should initialize the objects in the Unified CCE
Alarm subsystem soon after establishing its session with the CTI Server by reporting the current state of each
named object. The object name given uniquely identifies the alarm object. Therefore, CTI client applications
that wish to create multiple instances of an alarm object must include some instance-identifying characters
(such as ClientID or ACD extension) in the object name.
For example, if a CTI client “A” and a CTI client “B” both report events on an object named “C”, there will
be one Unified CCE Alarm object “C” that is manipulated by both clients. If, on the other hand, the Client
ID were included in the object name, then two Unified CCE Alarm objects would result; object “A:C” being
manipulated by client “A” and object “B:C” being independently manipulated by client “B”.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
159
Application Level Interfaces
USER_MESSAGE_REQ
The CTI Server responds to the CTI client with the CLIENT_EVENT_REPORT_CONF message:
USER_MESSAGE_REQ
The USER_MESSAGE_REQ message allows a CTI Client to send a message to a specified client, the client
agent’s supervisor, all clients in the client agent’s team, or all clients connected to the CTI Server.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
160
Application Level Interfaces
USER_MESSAGE_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
161
Application Level Interfaces
USER_MESSAGE_REQ
The CTI Server responds to the CTI Client with the USER_MESSAGE_CONF message:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
162
Application Level Interfaces
USER_MESSAGE_EVENT
USER_MESSAGE_EVENT
The USER_MESSAGE_EVENT message delivers a message that was sent from another CTI Server client:
Fixed Part
Floating Part
Related Topics
USER_MESSAGE_REQ, on page 160
QUERY_AGENT_STATISTICS_REQ
The QUERY_AGENT_STATISTICS_REQ message allows a CTI Client to obtain the current call handling
statistics for the client’s agent. To avoid impacting system performance, clients should not request agent
statistics too frequently. Depending upon the needs of the client application, updating agent statistics after
each call is handled my be appropriate.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
163
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
Floating Part
The CTI Server responds to the CTI Client with the QUERY_AGENT_STATISTICS_CONF message.
“Session” values represent statistics accumulated since the agent logged in. “Today” values represent statistics
accumulated since midnight. Call counts and times are updated when any after-call work for the call is
completed (calls currently in progress are not included in the statistics):
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
164
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
165
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
166
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
167
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
168
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
169
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
170
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
171
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
172
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
173
Application Level Interfaces
QUERY_AGENT_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
174
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
Floating Part
QUERY_SKILL_GROUP_STATISTICS_REQ
The QUERY_SKILL_GROUP_STATISTICS_REQ message allows a CTI Client to obtain the current call
handling statistics for one of the client agent’s skill groups. To avoid impacting system performance, clients
should not request skill group statistics too frequently. Depending upon the needs of the client application,
updating skill group statistics after each call is handled my be appropriate.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
175
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
The CTI Server responds to the CTI Client with the QUERY_SKILL_GROUP_STATISTICS_CONF message.
“ToHalf” values represent statistics accumulated in the current half hour period. “Today” values represent
statistics accumulated since midnight. Call counts and times are updated when any after-call work for the call
is completed (calls currently in progress are not included in the statistics):
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
176
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
Real-Time Statistics
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
177
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
178
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
179
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
180
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
181
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
182
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
183
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
184
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
185
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
186
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
187
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
188
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
189
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
190
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
191
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
192
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
193
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
194
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
195
Application Level Interfaces
QUERY_SKILL_GROUP_STATISTICS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
196
Application Level Interfaces
REGISTER_VARIABLES_REQ
Related Topics
CALL_DELIVERED_EVENT, on page 66
Special Values, on page 327
REGISTER_VARIABLES_REQ
The REGISTER_VARIABLES_REQ message allows a CTI Client to register the call context variables that
it will use. By default, a CTI Client that does not explicitly register variables will receive all call and ECC
variables. If a CTI Client does not want to receive all possible variables, it must explicitly register for each
variable that it wants.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
197
Application Level Interfaces
REGISTER_VARIABLES_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
198
Application Level Interfaces
SET_APP_DATA_REQ
If any specified Named Variable or Named Array is subsequently removed from the Unified CCE while the
CTI Client session is still open, the CTI Server will send a FAILURE_EVENT message to the CTI Client.
If any specified Named Variable or Named Array is not currently configured in the Unified CCE, the CTI
Server responds to the CTI Client with a FAILURE_CONF message. Otherwise, the CTI Server responds
with a REGISTER_VARIABLES_CONF message:
Related Topics
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
SET_APP_DATA_REQ
This message is sent by a CTI Client to set one or more application variables. Variables not provided in the
message are not affected.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
199
Application Level Interfaces
SET_APP_DATA_REQ
Fixed Part
Floating Part
… … … …
When the requested call variables have been updated, and the new values are guaranteed to remain set in the
event that the CTI session is abnormally terminated, the CTI Server responds to the CTI Client that requested
the update with the SET_APP_DATA_CONF message:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
200
Application Level Interfaces
START_RECORDING_REQ
START_RECORDING_REQ
A CTI client may send a START_RECORDING_REQ message, requesting CTI server to start recording a
call. Upon receiving the START_RECORDING_REQ, CTI server will try to find an available recording
server to satisfy the recording request. The recording server will return START_RECORDING_CONF to
CTI Server. Upon receipt of the START_RECORDING_CONF from the recording server, it will send
START_RECORDING_CONF to the requesting CTI client.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
201
Application Level Interfaces
START_RECORDING_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
202
Application Level Interfaces
START_RECORDING_REQ
The CTIServer forwards the START_RECORDING_REQ message to one or more servers applications that
have registered the “Cisco:CallRecording” service. The recording server will return the
START_RECORDING_CONF message when call recording has been activated. Upon receipt of the
START_RECORDING_CONF, the CTI Server forwards the response to the requesting CTI Client:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
203
Application Level Interfaces
START_RECORDING_REQ
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
204
Application Level Interfaces
STOP_RECORDING_REQ
STOP_RECORDING_REQ
This table defines the format of the STOP_RECORDING_REQ message:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
205
Application Level Interfaces
STOP_RECORDING_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
206
Application Level Interfaces
STOP_RECORDING_REQ
The CTIServer forwards the STOP_RECORDING_REQ message to the server application with session
SessionID if non-zero, or if SessionID is zero to one or more server applications that have registered the
“Cisco:CallRecording” service. The recording server will return the STOP_RECORDING_CONF message
when call recording has been terminated. Upon receipt of the STOP_RECORDING_CONF, the CTI Server
forwards the response to the requesting CTI Client:
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
207
Application Level Interfaces
AGENT_DESK_SETTINGS_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
AGENT_DESK_SETTINGS_REQ
This table defines the format of the AGENT_DESK_SETTINGS_REQ message:
Fixed Part
Floating Part
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
208
Application Level Interfaces
AGENT_DESK_SETTINGS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
209
Application Level Interfaces
AGENT_DESK_SETTINGS_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
210
Application Level Interfaces
AGENT_DESK_SETTINGS_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
211
Application Level Interfaces
SET_AGENT_SERVICE_DATA_REQ
SET_AGENT_SERVICE_DATA_REQ
This event is used to get the feedback from agent on agent answers suggestion provided by Google (or any
Answer Service). The agent selects thumbs-up or thumbs-down for each suggestion. This number is passed
using SET_AGENT_SERVICE_DATA_REQ event.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
212
Application Level Interfaces
SET_AGENT_SERVICE_DATA_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
213
Application Level Interfaces
Connection Monitor Service
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
214
Application Level Interfaces
Client Control Service
The CTI client may receive unsolicited call or agent event messages that are caused by the request before or
after the request confirmation message.
This figure illustrates the general Client Control message flow (using the messages to control agent state,
described later in this section):
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
215
Application Level Interfaces
QUERY_AGENT_STATE_REQ
Related Topics
Failure Indication Message Status Codes, on page 319
QUERY_AGENT_STATE_REQ
Send this message to retrieve the current state of an agent at a specified device.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
216
Application Level Interfaces
QUERY_AGENT_STATE_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
217
Application Level Interfaces
QUERY_AGENT_STATE_REQ
The CTI Server sends the QUERY_AGENT_STATE CONF message as the query response:
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
218
Application Level Interfaces
QUERY_AGENT_STATE_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
219
Application Level Interfaces
QUERY_AGENT_STATE_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
220
Application Level Interfaces
QUERY_AGENT_STATE_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
221
Application Level Interfaces
SET_AGENT_STATE_REQ
Related Topics
Agent Internal States Message Values, on page 375
AgentState Values, on page 344
Special Values, on page 327
SET_AGENT_STATE_REQ
Use this message to change an ACD agent state to one of the values defined below.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
222
Application Level Interfaces
SET_AGENT_STATE_REQ
Note For Remote Agent login, use “;” to separate the instrument and agent phone number in the AgentInstrument
field. Use RA_CALL_BY_CALL or RA_NAILED_CONNECTION in the AgentWorkMode field for the
Remote Agent login mode.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
223
Application Level Interfaces
SET_AGENT_STATE_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
224
Application Level Interfaces
SET_AGENT_STATE_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
225
Application Level Interfaces
ALTERNATE_CALL_REQ
The CTI Server sends the SET_AGENT_STATE_CONF message to confirm receipt of the request:
Related Topics
AgentState Values, on page 344
AgentWorkMode Values, on page 370
CALL_DELIVERED_EVENT, on page 66
ALTERNATE_CALL_REQ
Use this message to alternate between calls. This message requests the compound action of placing an active
call on hold and then either retrieving a previously held call or answering an alerting call at the same device.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
226
Application Level Interfaces
ALTERNATE_CALL_REQ
Floating Part
The CTI Server sends the ALTERNATE_CALL_CONF message to confirm receipt of the request:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
227
Application Level Interfaces
ANSWER_CALL_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
ANSWER_CALL_REQ
Use this message upon delivery of an alerting call, to connect the alerting call at the device that is alerting.
The ANSWER_CALL_REQ message is defined in this table:
Fixed Part
Floating Part
The CTI Server sends the ANSWER_CALL_CONF message to confirm receipt of the request:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
228
Application Level Interfaces
CLEAR_CALL_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
CLEAR_CALL_REQ
Use this message on hanging up a call, to release all devices from the specified call.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
229
Application Level Interfaces
CLEAR_CONNECTION_REQ
The CTI Server sends the CLEAR_CALL_CONF message to confirm receipt of the request:
Related Topics
ConnectionDeviceIDType Values, on page 356
CLEAR_CONNECTION_REQ
Use this message on hanging up a specific phone, to release the device connection from the designated call.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
230
Application Level Interfaces
CONFERENCE_CALL_REQ
Floating Part
The CTI Server sends the CLEAR_CONNECTION_CONF message to confirm receipt of the request:
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
CONFERENCE_CALL_REQ
Use this message to conference an existing held call with another active call. The two calls are merged and
the two connections at the conferencing device are in the connected state.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
231
Application Level Interfaces
CONFERENCE_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
232
Application Level Interfaces
CONFERENCE_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
233
Application Level Interfaces
CONFERENCE_CALL_REQ
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
234
Application Level Interfaces
CONFERENCE_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
235
Application Level Interfaces
CONFERENCE_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
236
Application Level Interfaces
CONSULTATION_CALL_REQ
Related Topics
AnsweringMachine Values, on page 368
CallMannerType Values, on page 366
CallOption Values, on page 367
CallPlacementType Values, on page 366
ConnectionDeviceIDType Values, on page 356
FacilityType Values, on page 368
LineType Values, on page 356
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
CONSULTATION_CALL_REQ
Use this message to request the combined action of placing an active call on hold and then making a new call.
By default, the CTI Server uses the call context data of the active call to initialize the context data of the
consultation call. You can override some or all of this original call context in the consultation call by providing
the desired values in this request.
Because this request includes putting the call on hold, you cannot use it for a call that is already on hold. If
you use this in a third-party desktop, the desktop must disable any options that make use of this call when the
active call is on hold.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
237
Application Level Interfaces
CONSULTATION_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
238
Application Level Interfaces
CONSULTATION_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
239
Application Level Interfaces
CONSULTATION_CALL_REQ
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
240
Application Level Interfaces
CONSULTATION_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
241
Application Level Interfaces
DEFLECT_CALL_REQ
Floating Part
Related Topics
AnsweringMachine Values, on page 368
CallMannerType Values, on page 366
CallOption Values, on page 367
CallPlacementType Values, on page 366
ConnectionDeviceIDType Values, on page 356
ConsultType Values, on page 368
FacilityType Values, on page 368
LineType Values, on page 356
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
DEFLECT_CALL_REQ
Use this message during a call forward operation, to take an alerting call from a known device and move it
to another device.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
242
Application Level Interfaces
DEFLECT_CALL_REQ
Floating Part
The CTI Server sends the DEFLECT_CALL_CONF message to confirm receipt of the request:
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
243
Application Level Interfaces
HOLD_CALL_REQ
HOLD_CALL_REQ
Use this message to place an existing call connection into the held state.
Fixed Part
Floating Part
The CTI Server sends the HOLD_CALL_CONF message to confirm receipt of the request.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
244
Application Level Interfaces
MAKE_CALL_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
MAKE_CALL_REQ
Use this message to initiate a call between two devices. This request attempts to create a new call and establish
a connection between the calling device (originator) and the called device (destination).
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
245
Application Level Interfaces
MAKE_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
246
Application Level Interfaces
MAKE_CALL_REQ
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
247
Application Level Interfaces
MAKE_CALL_REQ
Fixed Part
Floating Part
Related Topics
AnsweringMachine Values, on page 368
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
248
Application Level Interfaces
MAKE_PREDICTIVE_CALL_REQ
MAKE_PREDICTIVE_CALL_REQ
Use this message to request the initiation of a call between a group of devices and a logical device on behalf
of a calling device (originating). The request creates a new call and establishes a connection with the called
device (terminating).
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
249
Application Level Interfaces
MAKE_PREDICTIVE_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
250
Application Level Interfaces
MAKE_PREDICTIVE_CALL_REQ
Floating Part
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
251
Application Level Interfaces
MAKE_PREDICTIVE_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
252
Application Level Interfaces
RECONNECT_CALL_REQ
Fixed Part
Floating Part
Related Topics
AllocationState Values, on page 363
AnswerDetectMode Values, on page 369
RECONNECT_CALL_REQ
Use this message to request the combined action of clearing an active call and then retrieving an existing held
call.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
253
Application Level Interfaces
RECONNECT_CALL_REQ
Fixed Part
Floating Part
The CTI Server sends the RECONNECT_CALL_CONF message to confirm receipt of the request:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
254
Application Level Interfaces
RETRIEVE_CALL_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
RETRIEVE_CALL_REQ
Use this message to retrieve an existing held connection.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
255
Application Level Interfaces
TRANSFER_CALL_REQ
The CTI Server sends the RETRIEVE_CALL_CONF message to confirm receipt of the request.
Related Topics
ConnectionDeviceIDType Values, on page 356
TRANSFER_CALL_REQ
Use this message to transfer a held call to an active call. The two calls must have connections to a single
common device. Upon transfer, both of the connections with the common device become NULL and their
connection identifiers are released.
You can also use this message to transfer an active call to another number (single step or blind transfer).
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
256
Application Level Interfaces
TRANSFER_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
257
Application Level Interfaces
TRANSFER_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
258
Application Level Interfaces
TRANSFER_CALL_REQ
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
259
Application Level Interfaces
TRANSFER_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
260
Application Level Interfaces
TRANSFER_CALL_REQ
Floating Part
Related Topics
AnsweringMachine Values, on page 368
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
261
Application Level Interfaces
QUERY_DEVICE_INFO_REQ
QUERY_DEVICE_INFO_REQ
Use this message to retrieve general information about a specified device.
Fixed Part
Floating Part
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
262
Application Level Interfaces
QUERY_DEVICE_INFO_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
263
Application Level Interfaces
QUERY_DEVICE_INFO_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
264
Application Level Interfaces
QUERY_DEVICE_INFO_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
265
Application Level Interfaces
QUERY_DEVICE_INFO_REQ
Related Topics
AgentState Values, on page 344
ClassOfDevice Values, on page 365
LineType Values, on page 356
PeripheralType Values, on page 346
TypeOfDevice Values, on page 364
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
266
Application Level Interfaces
SNAPSHOT_CALL_REQ
SNAPSHOT_CALL_REQ
Use this message to retrieve information about a specified call, including a list of the associated devices and
the connection state for each device.
Fixed Part
Floating Part
The CTI Server sends the SNAPSHOT_CALL_CONF message to provide the requested data.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
267
Application Level Interfaces
SNAPSHOT_CALL_REQ
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
268
Application Level Interfaces
SNAPSHOT_CALL_REQ
… … … …
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
269
Application Level Interfaces
SNAPSHOT_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
270
Application Level Interfaces
SNAPSHOT_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
271
Application Level Interfaces
SNAPSHOT_CALL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
272
Application Level Interfaces
SNAPSHOT_DEVICE_REQ
Related Topics
CallType Values, on page 353
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
LocalConnectionState Values, on page 347
NAMEDVAR Data Type, on page 29
NAMEDARRAY Data Type, on page 30
Special Values, on page 327
SNAPSHOT_DEVICE_REQ
Use this message to retrieve information on a specified device, including a list of the calls associated with the
device and the current state of each call. The CTI Client must be granted both Client Control and All Events
services to look at all devices.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
273
Application Level Interfaces
SNAPSHOT_DEVICE_REQ
The CTI Server sends the SNAPSHOT_DEVICE_CONF message to provide the requested data.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
274
Application Level Interfaces
SNAPSHOT_DEVICE_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
275
Application Level Interfaces
SEND_DTMF_SIGNAL_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
DeviceIDType Values, on page 352
LocalConnectionState Values, on page 347
Special Values, on page 327
SEND_DTMF_SIGNAL_REQ
Use this message to request that the ACD transmits a sequence of DTMF tones on behalf of a call party.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
276
Application Level Interfaces
SEND_DTMF_SIGNAL_REQ
Floating Part
The CTI Server sends the SEND_DTMF_SIGNAL_CONF message to confirm receipt of the request.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
277
Application Level Interfaces
SUPERVISOR_ASSIST_REQ
Related Topics
ConnectionDeviceIDType Values, on page 356
SUPERVISOR_ASSIST_REQ
When an agent needs supervisor assistance, an agent may send a SUPERVISOR_ASSIST_REQ message to
the CTI server asking for assistance from a team supervisor. The message will be forwarded to the PIM, who
will first check the team’s primary supervisor. If the primary supervisor is not available, the PIM will initiate
a post-route request to the Unified CCE CallRouter using the team’s configured DialedNumber to find an
available supervisor in the supervisor group. Once an available supervisor is found, a call with calltype
SUPERVISOR_ASSIST is initiated, and a SUPERVISOR_ASSIST_CONF will be sent to the requesting
client. If no supervisor can be found a FAILURE_CONF response is returned to the requesting client.
The SUPERVISOR_ASSIST_REQ message allows a CTI Client to notify the client agent’s supervisor that
assistance with the indicated call is required.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
278
Application Level Interfaces
SUPERVISOR_ASSIST_REQ
Floating Part
When a supervisor CTI client has been notified the CTI Server responds to the CTI Client with the
SUPERVISOR_ASSIST_CONF message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
279
Application Level Interfaces
EMERGENCY_CALL_REQ
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
LineType Values, on page 356
EMERGENCY_CALL_REQ
When an agent needs to declare an emergency situation to their supervisor, an agent may send
EMERGENCY_CALL_REQ to the CTI server to notify an agent team supervisor. Like the Supervisor Assist
Request, the message will be forwarded to the PIM, who will first check the team’s primary supervisor. If the
primary supervisor is not available, the PIM will initiate a post-route request to the Unified CCE CallRouter
using the team’s configured DialedNumber to find an available supervisor in the supervisor group. Once an
available supervisor is found, a call with calltype EMERGENCY_ASSIST is initiated and an
EMERGENCY_CALL_CONF will be sent to the requesting client. If no supervisor can be found a
FAILURE_CONF response is returned to the requesting client. In addition, an EMERGENCY_CALL_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
280
Application Level Interfaces
EMERGENCY_CALL_REQ
will be sent to all bridge applications, even if no supervisor was found. At same time, an
EMERGENCY_CALL_EVENT will be sent to recording servers. Emergency Call requests will always cause
an Unified CCE event to be reported whether or not a supervisor was found to satisfy the request.
The EMERGENCY_CALL_REQ message allows a CTI Client to notify the client agent’s supervisor that an
emergency call is in progress and generate a corresponding Unified CCE Alarm.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
281
Application Level Interfaces
EMERGENCY_CALL_REQ
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
282
Application Level Interfaces
EMERGENCY_CALL_REQ
Floating Part
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
283
Application Level Interfaces
BAD_CALL_REQ
Floating Part
Related Topics
ConnectionDeviceIDType Values, on page 356
LineType Values, on page 356
BAD_CALL_REQ
The agent or supervisor can click on a Bad Call Line button on their desktop to initiate this feature. A record
would capture the information of the trunk, gateways, and other devices used in the connection. This information
is intended to aid troubleshooting by service personnel.
When a line condition is in poor quality, an agent could send the BAD_CALL_REQ message to mark the bad
line.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
284
Application Level Interfaces
BAD_CALL_REQ
Floating Part
When the request has been processed, the CTI Server responds to the CTI Client with the BAD_CALL_CONF
message.
Related Topics
ConnectionDeviceIDType Values, on page 356
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
285
Application Level Interfaces
AGENT_GREETING_CONTROL_REQ
AGENT_GREETING_CONTROL_REQ
The AGENT_GREETING_CONTROL_REQ allows the agent to stop the greeting while the greeting is
playing and allows the agent to enable or disable the playing of the greeting during a login sesssion.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
286
Application Level Interfaces
START_NETWORK_RECORDING_REQ
The CTI Server responds to the CTI Client with the AGENT GREETING_CONTROL_CONF message.
Fixed Part
START_NETWORK_RECORDING_REQ
This message will be sent by the client requesting CTI server to start recording a call. Clients need to ensure
that the call is connected before initiating this request.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
287
Application Level Interfaces
STOP_NETWORK_RECORDING_REQ
This message will be sent by CTI server to clients acknowledging receipt of the request. This response will
not indicate actual recording start.
Fixed Part
STOP_NETWORK_RECORDING_REQ
This message will be sent by a client requesting CTI server to stop recording a call. Clients need to ensure
that call is connected before initiating this request.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
288
Application Level Interfaces
STOP_NETWORK_RECORDING_REQ
Fixed Part
Floating Part
This message will be sent by CTI server to the clients, acknowledging the receipt of the request. This response
will not indicate actual recording that is to "Stop".
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
289
Application Level Interfaces
Server Service
Fixed Part
Server Service
Server Service
A server application specifies the new service type CTI_SERVICE_SERVER to identify itself as server
application. The server application then registers each service that it wishes to provide by sending a new
message, REGISTER_SERVICE_REQ, to the CTI Server. When a CTI client application requests a service
that is provided by a server application, such as CallRecording, the CTIServer selects a registered server
application and forwards the client request to the server application. If no server is registered for the desired
service the client request is refused with an E_CTI_NO_SERVER_FOR_REQUEST error.
The server service optionally allows multiple server applications to supply the same service. The ServerMode
registration parameter determines how a server is selected to handle a given request. All server applications
that wish to provide the same service must use the same ServerMode:
• Exclusive. The first server application to register the service is the only one to serve requests. All other
requests to register a server application for that service are refused with an
E_CTI_NO_SERVER_FOR_REQUEST.
• Round-Robin. Multiple server applications may register the service. The server application that has
been waiting the longest for a request of this service type is chosen to service the request.
• Parallel. Multiple server applications may register the service. Every request is sent to all registered
servers concurrently. Every server response is forwarded back to the requesting client.
REGISTER_SERVICE_REQ
Initially, the only service that server applications may provide is call recording by registering the
“Cisco:CallRecording” service using a REGISTER_SERVICE_REQ message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
290
Application Level Interfaces
UNREGISTER_SERVICE_REQ
Floating Part
UNREGISTER_SERVICE_REQ
Prior to closing its session with the CTI Server, or at any time that the server application wishes to discontinue
providing a registered service, it must send an UNREGISTER_SERVICE_REQ message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
291
Application Level Interfaces
Configuration Acquisition Messages
Fixed Part
Configuration keys
The configuration key is an 8 byte unique identifier that will be maintained by the server and optionally saved
by the client. The purpose of each key is to allow the client to determine if any configuration changes have
occurred since they last received the configuration from the server. There are 4 individual keys allowing
granularity for each major configuration item. If the server does not support 4 individual keys then it should
send up a single key in all 4 individual keys so that all configuration operations will be done. The key(s)
should be changed on the server any time when there is a configuration change.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
292
Application Level Interfaces
Initial configuration acquisition
Update messages
After the CONFIG_REQUEST_EVENT is received by the server, and if requested the configuration data is
sent up to the client, the server is free to send blocks of update configuration messages any time to the client.
Additionally, the server should honor the mask for the particular configuration event message types specified
in the OPEN_REQ message.
Message Order
The configuration must be sent in a particular order. This order is as follows:
1. Service Information
2. Skill Group
3. Agent Information
4. Agent Services
5. Device Information
6. Call Type Information
7. Media Routing Domain Information
8. Peripheral Information
9. Agent Desk Settings
Please note that there are no Invocation ID for the request and response events. This is due to the fact that
only one request can be outstanding at one time.
CONFIG_REQUEST_KEY_EVENT
The CONFIG_REQUEST_KEY_EVENT may be sent by the client to request the current configuration keys
for different items.
CONFIG_REQUEST_KEY_EVENT Message Format
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
293
Application Level Interfaces
CONFIG_KEY_EVENT
Floating Part
CONFIG_KEY_EVENT
The CONFIG_KEY_EVENT message is sent by the CTI Server in response to
CONFIG_REQUEST_KEY_EVENT message. It will contain the configuration keys at the time of the request.
Note that if the CTI Server doesn’t support separate keys that it may respond with 4 identical keys and it
should send the message with no optional fields. Returning any key of all binary 0’s will indicate to the client
that particular configuration should be uploaded.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
294
Application Level Interfaces
CONFIG_REQUEST_EVENT
CONFIG_REQUEST_EVENT
The CONFIG_REQUEST_EVENT message may be sent by the client whenever it wants to check and receive
a particular configuration from the CTI Server. The CTI Server should respond by sending a
CONFIG_BEGIN_EVENT, CONFIG_xxx records, then a CONFIG_END block containing all records for
that configuration item.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
295
Application Level Interfaces
CONFIG_REQUEST_EVENT
ConfigInformation UINT 4
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
296
Application Level Interfaces
CONFIG_REQUEST_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
297
Application Level Interfaces
CONFIG_REQUEST_EVENT
0x100 - Terminal
Information
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
298
Application Level Interfaces
CONFIG_BEGIN_EVENT
CONFIG_BEGIN_EVENT
The CONFIG_BEGIN_EVENT signifies the beginning of configuration data (all of the same key) from the
CTI Server.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
299
Application Level Interfaces
CONFIG_SERVICE_EVENT
CONFIG_SERVICE_EVENT
The CONFIG_SERVICE_EVENT message will be sent by the CTI Server to provide information about a
Service. Please note that the Peripheral Number field is considered unique for all records. Two records sent
with matching Peripheral Numbers will be the considered the same record.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
300
Application Level Interfaces
CONFIG_SERVICE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
301
Application Level Interfaces
CONFIG_SKILL_GROUP_EVENT
CONFIG_SKILL_GROUP_EVENT
The CONFIG_SKILL_GROUP_EVENT message will be sent to indicate a Skill Group configuration update.
Please note that the Peripheral Number field is considered unique for all records. Two records sent with
matching Peripheral Numbers will be the considered the same record.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
302
Application Level Interfaces
CONFIG_SKILL_GROUP_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
303
Application Level Interfaces
CONFIG_AGENT_EVENT
CONFIG_AGENT_EVENT
The CONFIG_AGENT_EVENT message is sent by the CTI Server to provide information about Agent.
Please note that the LoginID field is considered unique for all records. Two records sent with matching
LoginID’s are considered as the same record.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
304
Application Level Interfaces
CONFIG_AGENT_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
305
Application Level Interfaces
CONFIG_TERMINAL_EVENT
Note The CONFIG_AGENT_EVENT sends MRD information only for baseline configurations. Configuration
updates will not have MRD information.
CONFIG_TERMINAL_EVENT
The CONFIG_TERMINAL_EVENT message will be sent by the CTI Server to indicate an update to some
terminal configuration. Terminals contain terminal information and the extensions associated with the terminal.
For these terminals, a CONFIG_TERMINAL_EVENT message will be sent. The following shows the changes
to the existing message.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
306
Application Level Interfaces
CONFIG_AGENT_DESK_SETTINGS_EVENT
Floating Part
CONFIG_AGENT_DESK_SETTINGS_EVENT
Table 183: CONFIG_AGENT_DESK_SETTINGS_EVENT Message Format
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
307
Application Level Interfaces
CONFIG_AGENT_DESK_SETTINGS_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
308
Application Level Interfaces
CONFIG_AGENT_DESK_SETTINGS_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
309
Application Level Interfaces
CONFIG_PERIPHERAL_EVENT
CONFIG_PERIPHERAL_EVENT
Table 184: CONFIG_PERIPHERAL_EVENT Message Format
Fixed Part
Floating Part
CONFIG_DEVICE_EVENT
The CONFIG_DEVICE_EVENT message will be sent by the CTI Server to indicate an update to some device
configuration. Devices are associated with all entities like Services, Skill Groups, Agent Phones, Route Points
and CTI ports etc. For these devices, CONFIG_DEVICE_EVENT message will be sent.
Fixed Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
310
Application Level Interfaces
CONFIG_DEVICE_EVENT
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
311
Application Level Interfaces
CONFIG_CALL_TYPE_EVENT
CONFIG_CALL_TYPE_EVENT
The CONFIG_CALL_TYPE_EVENT message will be sent by the CTI Server to provide information about
a call type. Please note that the CallTypeID field is considered unique for all records. Two records sent with
matching CallTypeIDs will be the considered the same record.
Fixed Part
Floating Part
CONFIG_MRD_EVENT
The CONFIG_MRD_EVENT will be sent by the CTI Server to provide infomration about a Media Routing
Domain. Please note that the MRDomainID field is considered unique for all records. Two records sent with
matching MRDomainIDs will be the considered the same record.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
312
Application Level Interfaces
CONFIG_AGENT_SERVICE_EVENT
Fixed Part
Floating Part
CONFIG_AGENT_SERVICE_EVENT
This event will updates CTI Clients to indicate which Agent Services are enabled. The message is sent in the
following scenarios.
1. During the startup, and at least one service is enabled for the agent. If not, the message will not be sent.
2. When a service is added or removed to an existing list of services.
3. When all the services from the agent are removed, message is triggered.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
313
Application Level Interfaces
CONFIG_AGENT_SERVICE_EVENT
Fixed Part
Floating Part
5
Config Msg Flag: It will be sent only on subscription.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
314
Application Level Interfaces
CONFIG_END_EVENT
CONFIG_END_EVENT
The CONFIG_END_EVENT message will be sent by the CTI Server to indicate the end of a successful
configuration upload or an error condition. It most likely will follow configuration records preceded by a
CONFIG_BEGIN_EVENT message to respond to a CONFIG_REQUEST_EVENT message indicating either
an error or there is no configuration for the items requested.
Please note that status CONFIGEND_PARTIAL is used during the initial configuration upload if the server
needs to break up the configuration into multiple CONFIG_BEGIN_EVENT/CONFIG_END_EVENT
messages. In this case all but the last should be CONFIGEND_PARTIAL status. The reason for this is to let
the client know when the entire configuration has been received.
Fixed Part
Floating Part
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
315
Application Level Interfaces
CONFIG_END_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
316
CHAPTER 6
Constants and Status Codes
• In this chapter, on page 318
• Failure Indication Message Status Codes, on page 319
• SystemEventID Values, on page 326
• Special Values, on page 327
• Tag Values, on page 328
• AgentState Values, on page 344
• PGStatusCode Values, on page 345
• PeripheralType Values, on page 346
• LocalConnectionState Values, on page 347
• EventCause Values, on page 348
• DeviceIDType Values, on page 352
• CallType Values, on page 353
• ConnectionDeviceIDType Values, on page 356
• LineType Values, on page 356
• ControlFailureCode Values, on page 357
• AllocationState Values, on page 363
• ForwardType Values, on page 364
• TypeOfDevice Values, on page 364
• ClassOfDevice Values, on page 365
• CallPlacementType Values, on page 366
• CallMannerType Values, on page 366
• CallOption Values, on page 367
• ConsultType Values, on page 368
• FacilityType Values, on page 368
• AnsweringMachine Values, on page 368
• AnswerDetectMode Values, on page 369
• AgentWorkMode Values, on page 370
• DestinationCountry Values, on page 370
• CTI Service Masks, on page 371
• Disposition Code Values, on page 372
• Agent Service Request Masks, on page 375
• Silent Monitor Status Values, on page 375
• Agent Internal States Message Values, on page 375
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
317
Constants and Status Codes
In this chapter
In this chapter
This section lists the possible values for various status codes and fields that can appear in CTI Server messages.
These values are defined in the CTILink.h file, located in the \icm\include directory.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
318
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
319
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
320
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
321
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
322
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
323
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
324
Constants and Status Codes
Failure Indication Message Status Codes
E_CTI_SKILL_ The 86
GROUP_CONFLICT SkillGroupNumber/SkillGroupPriority
and SkillGroupID values given
represent different skill groups.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
325
Constants and Status Codes
SystemEventID Values
SystemEventID Values
This table shows the SystemEventID values that may be included in the SYSTEM_EVENT messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
326
Constants and Status Codes
Special Values
Special Values
This table shows the values used to define sizes and limits, indicate special IDs, and unspecified data elements.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
327
Constants and Status Codes
Tag Values
Tag Values
This table shows the values used in the tag subfield of floating fields.
CLIENT_ID_TAG OPEN_REQ 1
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
328
Constants and Status Codes
Tag Values
TEXT_TAG SYSTEM_EVENT, 7
CLIENT_EVENT_REPORT_REQ,
AGENT_TASKS_END_EVENT
UUI_TAG BEGIN_CALL_EVENT, 9
CALL_DATA_UPDATE_EVENT,
CALL_TRANSLATION_ROUTE_
EVENT, CONSULTATION_
CALL_REQ, MAKE_CALL_REQ,
TRANSFER_CALL_REQ,
SNAPSHOT_CALL_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
329
Constants and Status Codes
Tag Values
CTI_CLIENT_ BEGIN_CALL_EVENT, 23
SIGNATURE_TAG CALL_DATA_UPDATE_EVENT,
SNAPSHOT_CALL_CONF
CTI_CLIENT_ BEGIN_CALL_EVENT, 24
TIMESTAMP_TAG CALL_DATA_UPDATE_EVENT,
SNAPSHOT_CALL_CONF
CALLING_DEVID_TAG CALL_DELIVERED_EVENT, 27
CALL_ESTABLISHED_EVENT,
CALL_ORIGINATED_EVENT,
CALL_SERVICE_INITIATED_EVENT,
CALL_QUEUED_EVENT,
SET_DEVICE_ATTRIBUTES_REQ
CALLED_DEVID_TAG CALL_DELIVERED_EVENT, 28
CALL_ESTABLISHED_EVENT,
CALL_ORIGINATED_EVENT,
CALL_QUEUED_EVENT,
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
330
Constants and Status Codes
Tag Values
FAILING_DEVID_TAG CALL_FAILED_EVENT 34
PARTY_CALLID_TAG CALL_CONFERENCED_EVENT, 39
CALL_TRANSFERRED_EVENT,
CONFERENCE_CALL_CONF,
TRANSFER_CALL_CONF
PARTY_DEVID_TAG CALL_CONFERENCED_EVENT, 41
CALL_TRANSFERRED_EVENT,
CONFERENCE_CALL_CONF,
TRANSFER_CALL_CONF
QUEUE_DEVID_TAG CALL_QUEUED_EVENT 45
NEW_CONNECTION_ CALL_DATA_UPDATE_EVENT, 47
DEVID_TAG CONFERENCE_CALL_CONF,
CONSULTATION_CALL_CONF,
MAKE_CALL_CONF,
TRANSFER_CALL_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
331
Constants and Status Codes
Tag Values
FACILITY_CODE_TAG CONSULTATION_CALL_REQ, 51
MAKE_CALL_REQ,
TRANSFER_CALL_REQ
(reserved) 54-55
CALL_CONN_DEVID_ SNAPSHOT_CALL_CONF, 57
TYPE_TAG SNAPSHOT_DEVICE_CONF
CALL_DEVID_TAG SNAPSHOT_CALL_CONF 60
CALL_DEV_CONN_ SNAPSHOT_CALL_CONF 61
STATE_TAG
SKILL_GROUP_ CALL_QUEUED_EVENT, 64
PRIORITY_TAG CALL_DEQUEUED_EVENT,
QUERY_AGENT_STATE_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
332
Constants and Status Codes
Tag Values
OBJECT_NAME_TAG CLIENT_EVENT_REPORT 66
DTMF_STRING_TAG SEND_DTMF_SIGNAL_REQ 67
POSITION_ID_TAG SET_AGENT_STATE_REQ 68
SUPERVISOR_ID_TAG SET_AGENT_STATE_REQ 69
LINE_HANDLE_TAG QUERY_DEVICE_INFO_CONF 70
LINE_TYPE_TAG QUERY_DEVICE_INFO_CONF 71
(reserved) 74
CALL_STATE_TAG SNAPSHOT_DEVICE_CONF 75
MONITORED_DEVID_TAG MONITOR_START_REQ 76
ACCOUNT_CODE_TAG CONFERENCE_CALL_REQ, 78
CONSULTATION_CALL_REQ,
MAKE_CALL_REQ,
MAKE_PREDICTIVE_CALL_REQ,
TRANSFER_CALL_REQ
ORIGINATING_DEVID_TAG MAKE_PREDICTIVE_CALL_REQ 79
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
333
Constants and Status Codes
Tag Values
NAMED_ARRAY_TAG BEGIN_CALL_EVENT, 83
CALL_DATA_UPDATE_EVENT,
AGENT_PRE_CALL_EVENT,
CALL_TRANSLATION_ROUTE_
EVENT,
SET_CALL_DATA_REQ,
CONFERENCE_CALL_REQ,
CONSULTATION_CALL_REQ,
MAKE_CALL_REQ,
MAKE_PREDICTIVE_CALL_REQ,
TRANSFER_CALL_REQ,
SNAPSHOT_CALL_CONF,
REGISTER_VARIABLES_REQ,
SNAPSHOT_TASK_RESP,
SNAPSHOT_TASK_EVENT
SUPERVISOR_ SUPERVISE_CALL_REQ 85
INSTRUMENT_TAG
ATC_AGENT_ID_TAG AGENT_TEAM_CONFIG_EVENT 86
AGENT_FLAGS_TAG AGENT_TEAM_CONFIG_EVENT 87
AGENT_ SUPERVISE_CALL_REQ 90
CONNECTION_DEVID_ TAG
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
334
Constants and Status Codes
Tag Values
LIST_TEAM_ID_TAG LIST_AGENT_TEAM_CONF 92
DEFAULT_DEVICE_ AGENT_DESK_SETTINGS_CONF 93
PORT_ADDRESS_TAG
SERVICE_NAME_TAG REGISTER_SERVICE_REQ 94
CUSTOMER_PHONE_ SET_CALL_DATA_REQ, 95
NUMBER_TAG CALL_DATA_UPDATE_EVENT
CUSTOMER_ SET_CALL_DATA_REQ, 96
ACCOUNT_NUMBER_TAG CALL_DATA_UPDATE_EVENT
APP_PATH_ID_TAG OPEN_REQ 97
SCRIPT_SELECTOR_TAG SNAPSHOT_TASK_RESP, 99
SNAPSHOT_TASK_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
335
Constants and Status Codes
Tag Values
Unused 127-128
Reserved 143-149
Reserved 151-172
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
336
Constants and Status Codes
Tag Values
Unused 181-182
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
337
Constants and Status Codes
Tag Values
Unused 196-197
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
338
Constants and Status Codes
Tag Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
339
Constants and Status Codes
Tag Values
Used 226-227
SET_APPDATA_CALLID_TAG 233
CLIENT_SHARE_KEY_TAG 234
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
340
Constants and Status Codes
Tag Values
Unused 256
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
341
Constants and Status Codes
Tag Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
342
Constants and Status Codes
Tag Values
FLT_TERM_DEVICE_NAME CONFIG_TERMINAL_EVENTC
, ONFIG_AGENT_EVENT, 303
SET_AGENT_STATE_REQ,
AGENT_STATE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
343
Constants and Status Codes
AgentState Values
AgentState Values
This table shows the agent state values that may appear in the QUERY_AGENT_STATE_CONF messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
344
Constants and Status Codes
PGStatusCode Values
PGStatusCode Values
This table shows the PGStatusCode values that may be included in the SYSTEM_EVENT message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
345
Constants and Status Codes
PeripheralType Values
PeripheralType Values
This table shows the PeripheralType values that may be included in the Client Events service messages.
PT_G2 Lucent G2 3
PT_GALAXY Obsolete 6
PT_SPECTRUM Obsolete 7
PT_DMS100 Obsolete 10
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
346
Constants and Status Codes
LocalConnectionState Values
PT_NEC_NEAX_2x00 Obsolete 14
PT_GENERIC Generic 20
PT_ACMI_EXPERT_ADVISOR Obsolete 26
{reserved} 27
LocalConnectionState Values
This table shows the LocalConnectionState values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
347
Constants and Status Codes
EventCause Values
EventCause Values
These tables show the EventCause values.
EventCause Value
CEC_NONE 0xffff
CEC_ACTIVE_MONITOR 1
CEC_ALTERNATE 2
CEC_BUSY 3
CEC_CALL_BACK 4
CEC_CALL_CANCELLED 5
CEC_CALL_FORWARD_ALWAYS 6
CEC_CALL_FORWARD_BUSY 7
CEC_CALL_FORWARD_NO_ANSWER 8
CEC_CALL_FORWARD 9
CEC_CALL_NOT_ANSWERED 10
CEC_CALL_PICKUP 11
CEC_CAMP_ON 12
CEC_DEST_NOT_OBTAINABLE 13
CEC_DO_NOT_DISTURB 14
CEC_INCOMPATIBLE_DESTINATION 15
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
348
Constants and Status Codes
EventCause Values
EventCause Value
CEC_INVALID_ACCOUNT_CODE 16
CEC_KEY_CONFERENCE 17
CEC_LOCKOUT 18
CEC_MAINTENANCE 19
CEC_NETWORK_CONGESTION 20
CEC_NETWORK_NOT_OBTAINABLE 21
CEC_NEW_CALL 22
CEC_NO_AVAILABLE_AGENTS 23
CEC_OVERRIDE 24
CEC_PARK 25
CEC_OVERFLOW 26
CEC_RECALL 27
CEC_REDIRECTED 28
CEC_REORDER_TONE 29
CEC_RESOURCES_NOT_AVAILABLE 30
CEC_SILENT_MONITOR 31
CEC_TRANSFER 32
CEC_TRUNKS_BUSY 33
CEC_VOICE_UNIT_INITIATOR 34
CEC_TIME_OUT 35
CEC_NEW_CALL_INTERFLOW 36
CEC_SIMULATION_INIT_REQUEST 37
CEC_SIMULATION_RESET_REQUEST 38
CEC_CTI_LINK_DOWN 39
CEC_PERIPHERAL_RESET_REQUEST 40
CEC_MD110_CONFERENCE_TRANSFER 41
CEC_REMAINS_IN_Q 42
CEC_SUPERVISOR_ASSIST 43
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
349
Constants and Status Codes
EventCause Values
EventCause Value
CEC_EMERGENCY_CALL 44
CEC_SUPERVISOR_CLEAR 45
CEC_SUPERVISOR_MONITOR 46
CEC_SUPERVISOR_WHISPER 47
CEC_SUPERVISOR_BARGE_IN 48
CEC_SUPERVISOR_INTERCEPT 49
CEC_CALL_PARTY_UPDATE_IND 50
CEC_CONSULT 51
CEC_NIC_CALL_CLEAR 52
EventCause Value
CECX_ABAND_NETWORK 1001
CECX_ABAND_LOCAL_QUEUE 1002
CECX_ABAND_RING 1003
CECX_ABAND_DELAY 1004
CECX_ABAND_INTERFLOW 1005
CECX_ABAND_AGENT_TERMINAL 1006
CECX_SHORT 1007
CECX_BUSY 1008
CECX_FORCED_BUSY 1009
CECX_DROP_NO_ANSWER 1010
CECX_DROP_BUSY 1011
CECX_DROP_REORDER 1012
CECX_DROP_HANDLED_PRIMARY_ROUTE 1013
CECX_DROP_HANDLED_OTHER 1014
CECX_REDIRECTED 1015
CECX_CUT_THROUGH 1016
CECX_INTRAFLOW 1017
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
350
Constants and Status Codes
EventCause Values
EventCause Value
CECX_INTERFLOW 1018
CECX_RING_NO_ANSWER 1019
CECX_INTERCEPT_REORDER 1020
CECX_INTERCEPT_DENIAL 1021
CECX_TIME_OUT 1022
CECX_VOICE_ENERGY 1023
CECX_NONCLASSIFIED_ENERGY_DETECT 1024
CECX_NO_CUT_THROUGH 1025
CECX_UABORT 1026
CECX_FAILED_SOFTWARE 1027
CECX_BLIND_TRANSFER 1028
CECX_ANNOUNCED_TRANSFER 1029
CECX_CONFERENCED 1030
CECX_DUPLICATE_TRANSFER 1031
CECX_UNMONITORED_DEVICE 1032
CECX_ANSWERING_MACHINE 1033
CECX_NETWORK_BLIND_TRANSFER 1034
CECX_TASK_ABANDONED_IN_ROUTER 1035
CECX_TASK_ABANDONED_BEFORE_OFFERED 1036
CECX_TASK_ABANDONED_WHILE_OFFERED 1037
CECX_NORMAL_END_TASK 1038
CECX_CANT_OBTAIN_TASK_ID 1039
CECX_AGENT_LOGGED_OUT_DURING_TASK 1040
CECX_MAX_TASK_LIFETIME_EXCEEDED 1041
CECX_APPLICATION_PATH_WENT_DOWN 1042
CECX_ICM_ROUTING_COMPLETE 1043
CECX_ICM_ROUTING_DISABLED 1044
CECX_APPL_INVALID_MRD_ID 1045
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
351
Constants and Status Codes
DeviceIDType Values
EventCause Value
CECX_APPL_INVALID_DIALOGUE_ID 1056
CECX_APPL_DUPLICATE_DIALOGUE_ID 1047
CECX_APPL_INVALID_INVOKE_ID 1048
CECX_APPL_INVALID_SCRIPT_SELECTOR 1049
CECX_APPL_TERMINATE_DIALOGUE 1050
CECX_TASK_ENDED_DURING_APP_INIT 1051
CECX_CALLED_PARTY_DISCONNECTED 1052
CECX_PARTIAL_CALL 1053
CECX_DROP_NETWORK_CONSULT 1054
CECX_NETWORK_CONSULT_TRANSFER 1055
CECX_NETWORK_CONFERENCE 1056
CECX_ABAND_NETWORK_CONSULT 1057
DeviceIDType Values
This table shows the DeviceIDType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
352
Constants and Status Codes
CallType Values
CallType Values
This table shows the CallType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
353
Constants and Status Codes
CallType Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
354
Constants and Status Codes
CallType Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
355
Constants and Status Codes
ConnectionDeviceIDType Values
ConnectionDeviceIDType Values
This table shows the possible ConnectionDeviceIDType values.
LineType Values
This table shows the possible LineType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
356
Constants and Status Codes
ControlFailureCode Values
ControlFailureCode Values
This table shows the possible ControlFailureCode values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
357
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
358
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
359
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
360
Constants and Status Codes
ControlFailureCode Values
CF_INVALID_DIGITS_ 276
RNATIMEOUT_AMSDELAY_
OR_COUNTRY
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
361
Constants and Status Codes
ControlFailureCode Values
CF_ANSWER_DETECT_ 277
PORT_UNAVAILABLE
CF_VIRTUAL_AGENT_ 278
UNAVAILABLE
CF_TAKEBACK_N_XFER_ 279
ROUTE_END
CF_WRAPUP_DATA_ 280
REQUIRED
CF_REASON_CODE_ 281
REQUIRED
CF_INVALID_TRUNK_ID_ 282
SPECIFIED
CF_SPECIFIED_EXTENSION_ 283
ALREADY_IN_USE
CF_ARBITRARY_CONF_OR_ 284
XFER_NOT_SUPPORTED
CF_NETWORK_TRANSFER_OR_ 285
CONSULT
CF_NETWORK_TRANSFER_OR_ 286
CONSULT_FAILED
CF_DEVICE_RESTRICTED 287
CF_LINE_RESTRICTED 288
CF_AGENT_ACCOUNT_ 289
LOCKED_OUT
CF_DROP_ANY_PARTY_NOT_ 290
ENABLED_CTI
CF_MAXIMUM_LINE_LIMIT_ 291
EXCEEDED
CF_SHARED_LINES_NOT_ 292
SUPPORTED
CF_EXTENSION_NOT_UNIQUE 293
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
362
Constants and Status Codes
AllocationState Values
AllocationState Values
This table shows the AllocationState values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
363
Constants and Status Codes
ForwardType Values
ForwardType Values
This table shows the ForwardType values.
TypeOfDevice Values
This table shows the TypeOfDevice values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
364
Constants and Status Codes
ClassOfDevice Values
ClassOfDevice Values
This table shows the ClassOfDevice values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
365
Constants and Status Codes
CallPlacementType Values
CallPlacementType Values
This table shows the CallPlacementType values.
CallMannerType Values
This table shows the CallMannerType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
366
Constants and Status Codes
CallOption Values
CMT_RESERVED Reserved 4
CallOption Values
This table shows the CallOption values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
367
Constants and Status Codes
ConsultType Values
ConsultType Values
This table shows the ConsultType values.
FacilityType Values
This table shows the FacilityType values.
AnsweringMachine Values
This table shows the AnsweringMachine values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
368
Constants and Status Codes
AnswerDetectMode Values
AnswerDetectMode Values
This table shows the AnswerDetectMode values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
369
Constants and Status Codes
AgentWorkMode Values
AgentWorkMode Values
This table shows the AgentWorkMode values.
DestinationCountry Values
This table shows the DestinationCountry values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
370
Constants and Status Codes
CTI Service Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
371
Constants and Status Codes
Disposition Code Values
Unused 0x00004000
1 Abandoned in Network
3 Abandoned Ring
4 Abandoned Delay
5 Abandoned Interflow
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
372
Constants and Status Codes
Disposition Code Values
7 Short
8 Busy
9 Forced Busy
10 Disconnect/drop no answer
11 Disconnect/drop busy
12 Disconnect/drop reorder
15 Redirected
16 Cut Through
17 Intraflow
18 Interflow
19 Ring No Answer
20 Intercept reorder
21 Intercept denial
22 Time Out
23 Voice Energy
25 No Cut Through
26 U-Abort
27 Failed Software
28 Blind Transfer
29 Announced Transfer
30 Conferenced
31 Duplicate Transfer
32 Unmonitored Device
33 Answering Machine
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
373
Constants and Status Codes
Disposition Code Values
53 Partial Call
60 Network Error
63 Task Transfer
64 Application Disconnected
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
374
Constants and Status Codes
Agent Service Request Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
375
Constants and Status Codes
TaskState Values
TaskState Values
This table shows the TaskState values that may appear in SNAPSHOT_TASK_RESP messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
376
Constants and Status Codes
In this chapter
In this chapter
This section lists the possible values for various status codes and fields that can appear in CTI Server messages.
These values are defined in the CTILink.h file, located in the \icm\include directory.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
377
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
378
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
379
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
380
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
381
Constants and Status Codes
Failure Indication Message Status Codes
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
382
Constants and Status Codes
Failure Indication Message Status Codes
E_CTI_SKILL_ The 86
GROUP_CONFLICT SkillGroupNumber/SkillGroupPriority
and SkillGroupID values given
represent different skill groups.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
383
Constants and Status Codes
SystemEventID Values
SystemEventID Values
This table shows the SystemEventID values that may be included in the SYSTEM_EVENT messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
384
Constants and Status Codes
SystemEventID Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
385
Constants and Status Codes
Special Values
Special Values
This table shows the values used to define sizes and limits, indicate special IDs, and unspecified data elements.
Tag Values
This table shows the values used in the tag subfield of floating fields.
CLIENT_ID_TAG OPEN_REQ 1
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
386
Constants and Status Codes
Tag Values
TEXT_TAG SYSTEM_EVENT, 7
CLIENT_EVENT_REPORT_REQ,
AGENT_TASKS_END_EVENT
UUI_TAG BEGIN_CALL_EVENT, 9
CALL_DATA_UPDATE_EVENT,
CALL_TRANSLATION_ROUTE_
EVENT, CONSULTATION_
CALL_REQ, MAKE_CALL_REQ,
TRANSFER_CALL_REQ,
SNAPSHOT_CALL_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
387
Constants and Status Codes
Tag Values
CTI_CLIENT_ BEGIN_CALL_EVENT, 23
SIGNATURE_TAG CALL_DATA_UPDATE_EVENT,
SNAPSHOT_CALL_CONF
CTI_CLIENT_ BEGIN_CALL_EVENT, 24
TIMESTAMP_TAG CALL_DATA_UPDATE_EVENT,
SNAPSHOT_CALL_CONF
CALLING_DEVID_TAG CALL_DELIVERED_EVENT, 27
CALL_ESTABLISHED_EVENT,
CALL_ORIGINATED_EVENT,
CALL_SERVICE_INITIATED_EVENT,
CALL_QUEUED_EVENT,
SET_DEVICE_ATTRIBUTES_REQ
CALLED_DEVID_TAG CALL_DELIVERED_EVENT, 28
CALL_ESTABLISHED_EVENT,
CALL_ORIGINATED_EVENT,
CALL_QUEUED_EVENT,
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
388
Constants and Status Codes
Tag Values
FAILING_DEVID_TAG CALL_FAILED_EVENT 34
PARTY_CALLID_TAG CALL_CONFERENCED_EVENT, 39
CALL_TRANSFERRED_EVENT,
CONFERENCE_CALL_CONF,
TRANSFER_CALL_CONF
PARTY_DEVID_TAG CALL_CONFERENCED_EVENT, 41
CALL_TRANSFERRED_EVENT,
CONFERENCE_CALL_CONF,
TRANSFER_CALL_CONF
QUEUE_DEVID_TAG CALL_QUEUED_EVENT 45
NEW_CONNECTION_ CALL_DATA_UPDATE_EVENT, 47
DEVID_TAG CONFERENCE_CALL_CONF,
CONSULTATION_CALL_CONF,
MAKE_CALL_CONF,
TRANSFER_CALL_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
389
Constants and Status Codes
Tag Values
FACILITY_CODE_TAG CONSULTATION_CALL_REQ, 51
MAKE_CALL_REQ,
TRANSFER_CALL_REQ
(reserved) 54-55
CALL_CONN_DEVID_ SNAPSHOT_CALL_CONF, 57
TYPE_TAG SNAPSHOT_DEVICE_CONF
CALL_DEVID_TAG SNAPSHOT_CALL_CONF 60
CALL_DEV_CONN_ SNAPSHOT_CALL_CONF 61
STATE_TAG
SKILL_GROUP_ CALL_QUEUED_EVENT, 64
PRIORITY_TAG CALL_DEQUEUED_EVENT,
QUERY_AGENT_STATE_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
390
Constants and Status Codes
Tag Values
OBJECT_NAME_TAG CLIENT_EVENT_REPORT 66
DTMF_STRING_TAG SEND_DTMF_SIGNAL_REQ 67
POSITION_ID_TAG SET_AGENT_STATE_REQ 68
SUPERVISOR_ID_TAG SET_AGENT_STATE_REQ 69
LINE_HANDLE_TAG QUERY_DEVICE_INFO_CONF 70
LINE_TYPE_TAG QUERY_DEVICE_INFO_CONF 71
(reserved) 74
CALL_STATE_TAG SNAPSHOT_DEVICE_CONF 75
MONITORED_DEVID_TAG MONITOR_START_REQ 76
ACCOUNT_CODE_TAG CONFERENCE_CALL_REQ, 78
CONSULTATION_CALL_REQ,
MAKE_CALL_REQ,
MAKE_PREDICTIVE_CALL_REQ,
TRANSFER_CALL_REQ
ORIGINATING_DEVID_TAG MAKE_PREDICTIVE_CALL_REQ 79
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
391
Constants and Status Codes
Tag Values
NAMED_ARRAY_TAG BEGIN_CALL_EVENT, 83
CALL_DATA_UPDATE_EVENT,
AGENT_PRE_CALL_EVENT,
CALL_TRANSLATION_ROUTE_
EVENT,
SET_CALL_DATA_REQ,
CONFERENCE_CALL_REQ,
CONSULTATION_CALL_REQ,
MAKE_CALL_REQ,
MAKE_PREDICTIVE_CALL_REQ,
TRANSFER_CALL_REQ,
SNAPSHOT_CALL_CONF,
REGISTER_VARIABLES_REQ,
SNAPSHOT_TASK_RESP,
SNAPSHOT_TASK_EVENT
SUPERVISOR_ SUPERVISE_CALL_REQ 85
INSTRUMENT_TAG
ATC_AGENT_ID_TAG AGENT_TEAM_CONFIG_EVENT 86
AGENT_FLAGS_TAG AGENT_TEAM_CONFIG_EVENT 87
AGENT_ SUPERVISE_CALL_REQ 90
CONNECTION_DEVID_ TAG
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
392
Constants and Status Codes
Tag Values
LIST_TEAM_ID_TAG LIST_AGENT_TEAM_CONF 92
DEFAULT_DEVICE_ AGENT_DESK_SETTINGS_CONF 93
PORT_ADDRESS_TAG
SERVICE_NAME_TAG REGISTER_SERVICE_REQ 94
CUSTOMER_PHONE_ SET_CALL_DATA_REQ, 95
NUMBER_TAG CALL_DATA_UPDATE_EVENT
CUSTOMER_ SET_CALL_DATA_REQ, 96
ACCOUNT_NUMBER_TAG CALL_DATA_UPDATE_EVENT
APP_PATH_ID_TAG OPEN_REQ 97
SCRIPT_SELECTOR_TAG SNAPSHOT_TASK_RESP, 99
SNAPSHOT_TASK_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
393
Constants and Status Codes
Tag Values
Unused 127-128
Reserved 143-149
Reserved 151-172
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
394
Constants and Status Codes
Tag Values
Unused 181-182
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
395
Constants and Status Codes
Tag Values
Unused 196-197
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
396
Constants and Status Codes
Tag Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
397
Constants and Status Codes
Tag Values
Used 226-227
SET_APPDATA_CALLID_TAG 233
CLIENT_SHARE_KEY_TAG 234
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
398
Constants and Status Codes
Tag Values
Unused 256
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
399
Constants and Status Codes
Tag Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
400
Constants and Status Codes
Tag Values
FLT_TERM_DEVICE_NAME CONFIG_TERMINAL_EVENTC
, ONFIG_AGENT_EVENT, 303
SET_AGENT_STATE_REQ,
AGENT_STATE_EVENT
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
401
Constants and Status Codes
AgentState Values
AgentState Values
This table shows the agent state values that may appear in the QUERY_AGENT_STATE_CONF messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
402
Constants and Status Codes
PGStatusCode Values
PGStatusCode Values
This table shows the PGStatusCode values that may be included in the SYSTEM_EVENT message.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
403
Constants and Status Codes
PeripheralType Values
PeripheralType Values
This table shows the PeripheralType values that may be included in the Client Events service messages.
PT_G2 Lucent G2 3
PT_GALAXY Obsolete 6
PT_SPECTRUM Obsolete 7
PT_DMS100 Obsolete 10
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
404
Constants and Status Codes
LocalConnectionState Values
PT_NEC_NEAX_2x00 Obsolete 14
PT_GENERIC Generic 20
PT_ACMI_EXPERT_ADVISOR Obsolete 26
{reserved} 27
LocalConnectionState Values
This table shows the LocalConnectionState values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
405
Constants and Status Codes
EventCause Values
EventCause Values
These tables show the EventCause values.
EventCause Value
CEC_NONE 0xffff
CEC_ACTIVE_MONITOR 1
CEC_ALTERNATE 2
CEC_BUSY 3
CEC_CALL_BACK 4
CEC_CALL_CANCELLED 5
CEC_CALL_FORWARD_ALWAYS 6
CEC_CALL_FORWARD_BUSY 7
CEC_CALL_FORWARD_NO_ANSWER 8
CEC_CALL_FORWARD 9
CEC_CALL_NOT_ANSWERED 10
CEC_CALL_PICKUP 11
CEC_CAMP_ON 12
CEC_DEST_NOT_OBTAINABLE 13
CEC_DO_NOT_DISTURB 14
CEC_INCOMPATIBLE_DESTINATION 15
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
406
Constants and Status Codes
EventCause Values
EventCause Value
CEC_INVALID_ACCOUNT_CODE 16
CEC_KEY_CONFERENCE 17
CEC_LOCKOUT 18
CEC_MAINTENANCE 19
CEC_NETWORK_CONGESTION 20
CEC_NETWORK_NOT_OBTAINABLE 21
CEC_NEW_CALL 22
CEC_NO_AVAILABLE_AGENTS 23
CEC_OVERRIDE 24
CEC_PARK 25
CEC_OVERFLOW 26
CEC_RECALL 27
CEC_REDIRECTED 28
CEC_REORDER_TONE 29
CEC_RESOURCES_NOT_AVAILABLE 30
CEC_SILENT_MONITOR 31
CEC_TRANSFER 32
CEC_TRUNKS_BUSY 33
CEC_VOICE_UNIT_INITIATOR 34
CEC_TIME_OUT 35
CEC_NEW_CALL_INTERFLOW 36
CEC_SIMULATION_INIT_REQUEST 37
CEC_SIMULATION_RESET_REQUEST 38
CEC_CTI_LINK_DOWN 39
CEC_PERIPHERAL_RESET_REQUEST 40
CEC_MD110_CONFERENCE_TRANSFER 41
CEC_REMAINS_IN_Q 42
CEC_SUPERVISOR_ASSIST 43
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
407
Constants and Status Codes
EventCause Values
EventCause Value
CEC_EMERGENCY_CALL 44
CEC_SUPERVISOR_CLEAR 45
CEC_SUPERVISOR_MONITOR 46
CEC_SUPERVISOR_WHISPER 47
CEC_SUPERVISOR_BARGE_IN 48
CEC_SUPERVISOR_INTERCEPT 49
CEC_CALL_PARTY_UPDATE_IND 50
CEC_CONSULT 51
CEC_NIC_CALL_CLEAR 52
EventCause Value
CECX_ABAND_NETWORK 1001
CECX_ABAND_LOCAL_QUEUE 1002
CECX_ABAND_RING 1003
CECX_ABAND_DELAY 1004
CECX_ABAND_INTERFLOW 1005
CECX_ABAND_AGENT_TERMINAL 1006
CECX_SHORT 1007
CECX_BUSY 1008
CECX_FORCED_BUSY 1009
CECX_DROP_NO_ANSWER 1010
CECX_DROP_BUSY 1011
CECX_DROP_REORDER 1012
CECX_DROP_HANDLED_PRIMARY_ROUTE 1013
CECX_DROP_HANDLED_OTHER 1014
CECX_REDIRECTED 1015
CECX_CUT_THROUGH 1016
CECX_INTRAFLOW 1017
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
408
Constants and Status Codes
EventCause Values
EventCause Value
CECX_INTERFLOW 1018
CECX_RING_NO_ANSWER 1019
CECX_INTERCEPT_REORDER 1020
CECX_INTERCEPT_DENIAL 1021
CECX_TIME_OUT 1022
CECX_VOICE_ENERGY 1023
CECX_NONCLASSIFIED_ENERGY_DETECT 1024
CECX_NO_CUT_THROUGH 1025
CECX_UABORT 1026
CECX_FAILED_SOFTWARE 1027
CECX_BLIND_TRANSFER 1028
CECX_ANNOUNCED_TRANSFER 1029
CECX_CONFERENCED 1030
CECX_DUPLICATE_TRANSFER 1031
CECX_UNMONITORED_DEVICE 1032
CECX_ANSWERING_MACHINE 1033
CECX_NETWORK_BLIND_TRANSFER 1034
CECX_TASK_ABANDONED_IN_ROUTER 1035
CECX_TASK_ABANDONED_BEFORE_OFFERED 1036
CECX_TASK_ABANDONED_WHILE_OFFERED 1037
CECX_NORMAL_END_TASK 1038
CECX_CANT_OBTAIN_TASK_ID 1039
CECX_AGENT_LOGGED_OUT_DURING_TASK 1040
CECX_MAX_TASK_LIFETIME_EXCEEDED 1041
CECX_APPLICATION_PATH_WENT_DOWN 1042
CECX_ICM_ROUTING_COMPLETE 1043
CECX_ICM_ROUTING_DISABLED 1044
CECX_APPL_INVALID_MRD_ID 1045
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
409
Constants and Status Codes
DeviceIDType Values
EventCause Value
CECX_APPL_INVALID_DIALOGUE_ID 1056
CECX_APPL_DUPLICATE_DIALOGUE_ID 1047
CECX_APPL_INVALID_INVOKE_ID 1048
CECX_APPL_INVALID_SCRIPT_SELECTOR 1049
CECX_APPL_TERMINATE_DIALOGUE 1050
CECX_TASK_ENDED_DURING_APP_INIT 1051
CECX_CALLED_PARTY_DISCONNECTED 1052
CECX_PARTIAL_CALL 1053
CECX_DROP_NETWORK_CONSULT 1054
CECX_NETWORK_CONSULT_TRANSFER 1055
CECX_NETWORK_CONFERENCE 1056
CECX_ABAND_NETWORK_CONSULT 1057
DeviceIDType Values
This table shows the DeviceIDType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
410
Constants and Status Codes
CallType Values
CallType Values
This table shows the CallType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
411
Constants and Status Codes
CallType Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
412
Constants and Status Codes
CallType Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
413
Constants and Status Codes
ConnectionDeviceIDType Values
ConnectionDeviceIDType Values
This table shows the possible ConnectionDeviceIDType values.
LineType Values
This table shows the possible LineType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
414
Constants and Status Codes
ControlFailureCode Values
ControlFailureCode Values
This table shows the possible ControlFailureCode values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
415
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
416
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
417
Constants and Status Codes
ControlFailureCode Values
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
418
Constants and Status Codes
ControlFailureCode Values
CF_INVALID_DIGITS_ 276
RNATIMEOUT_AMSDELAY_
OR_COUNTRY
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
419
Constants and Status Codes
ControlFailureCode Values
CF_ANSWER_DETECT_ 277
PORT_UNAVAILABLE
CF_VIRTUAL_AGENT_ 278
UNAVAILABLE
CF_TAKEBACK_N_XFER_ 279
ROUTE_END
CF_WRAPUP_DATA_ 280
REQUIRED
CF_REASON_CODE_ 281
REQUIRED
CF_INVALID_TRUNK_ID_ 282
SPECIFIED
CF_SPECIFIED_EXTENSION_ 283
ALREADY_IN_USE
CF_ARBITRARY_CONF_OR_ 284
XFER_NOT_SUPPORTED
CF_NETWORK_TRANSFER_OR_ 285
CONSULT
CF_NETWORK_TRANSFER_OR_ 286
CONSULT_FAILED
CF_DEVICE_RESTRICTED 287
CF_LINE_RESTRICTED 288
CF_AGENT_ACCOUNT_ 289
LOCKED_OUT
CF_DROP_ANY_PARTY_NOT_ 290
ENABLED_CTI
CF_MAXIMUM_LINE_LIMIT_ 291
EXCEEDED
CF_SHARED_LINES_NOT_ 292
SUPPORTED
CF_EXTENSION_NOT_UNIQUE 293
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
420
Constants and Status Codes
AllocationState Values
AllocationState Values
This table shows the AllocationState values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
421
Constants and Status Codes
ForwardType Values
ForwardType Values
This table shows the ForwardType values.
TypeOfDevice Values
This table shows the TypeOfDevice values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
422
Constants and Status Codes
ClassOfDevice Values
ClassOfDevice Values
This table shows the ClassOfDevice values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
423
Constants and Status Codes
CallPlacementType Values
CallPlacementType Values
This table shows the CallPlacementType values.
CallMannerType Values
This table shows the CallMannerType values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
424
Constants and Status Codes
CallOption Values
CMT_RESERVED Reserved 4
CallOption Values
This table shows the CallOption values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
425
Constants and Status Codes
ConsultType Values
ConsultType Values
This table shows the ConsultType values.
FacilityType Values
This table shows the FacilityType values.
AnsweringMachine Values
This table shows the AnsweringMachine values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
426
Constants and Status Codes
AnswerDetectMode Values
AnswerDetectMode Values
This table shows the AnswerDetectMode values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
427
Constants and Status Codes
AgentWorkMode Values
AgentWorkMode Values
This table shows the AgentWorkMode values.
DestinationCountry Values
This table shows the DestinationCountry values.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
428
Constants and Status Codes
CTI Service Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
429
Constants and Status Codes
Disposition Code Values
Unused 0x00004000
1 Abandoned in Network
3 Abandoned Ring
4 Abandoned Delay
5 Abandoned Interflow
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
430
Constants and Status Codes
Disposition Code Values
7 Short
8 Busy
9 Forced Busy
10 Disconnect/drop no answer
11 Disconnect/drop busy
12 Disconnect/drop reorder
15 Redirected
16 Cut Through
17 Intraflow
18 Interflow
19 Ring No Answer
20 Intercept reorder
21 Intercept denial
22 Time Out
23 Voice Energy
25 No Cut Through
26 U-Abort
27 Failed Software
28 Blind Transfer
29 Announced Transfer
30 Conferenced
31 Duplicate Transfer
32 Unmonitored Device
33 Answering Machine
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
431
Constants and Status Codes
Disposition Code Values
53 Partial Call
60 Network Error
63 Task Transfer
64 Application Disconnected
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
432
Constants and Status Codes
Agent Service Request Masks
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
433
Constants and Status Codes
TaskState Values
TaskState Values
This table shows the TaskState values that may appear in SNAPSHOT_TASK_RESP messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
434
CHAPTER 7
Changes and Additions
• Protocol Version 24, on page 435
• Protocol Version 23, on page 436
• Protocol Version 22, on page 437
• Protocol Version 21, on page 437
• Protocol Version 20, on page 437
• Protocol Version 19, on page 438
• Protocol Version 18, on page 439
• Protocol Version 17, on page 439
• Protocol Version 16, on page 439
• Protocol Version 15, on page 439
• Protocol Version 14, on page 440
• Protocol Versions 10-13, on page 442
• Protocol Version 9, on page 443
• Protocol Version 8, on page 444
• Protocol Version 7, on page 445
• Protocol Version 6, on page 446
• Protocol Version 5, on page 448
Protocol Version 24
Following is a list of changes made in Protocol Version 24:
• Added STANDBY_ACTIVE_EVENT_MSG, ACTIVE_MAINTENANCE_REQ_MSG,
ACTIVE_MAINTENANCE_RESP_MSG, ACTIVE_MAINTENANCE_EVENT_MSG, and
STOPPING_REQUESTS_TO_THIS_SIDE_IND to Message Types.
• Updated OPEN_REQ and OPEN_CONF in Message Types
• Updated CONFIG_AGENT_SERVICE_EVENT, SET_AGENT_SERVICE_DATA_REQ and
SET_AGENT_SERVICE_DATA_CONF
in Message Types
• Added E_CTI_INVALID_CLIENT_FOR_STANDBY to the Failure Indication Message Status Codes
table.
• Added the following new messages:
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
435
Changes and Additions
Protocol Version 23
1. CONFIG_AGENT_SERVICE_EVENT
2. SET_AGENT_SERVICE_DATA_REQ
3. SET_AGENT_SERVICE_DATA_CONF
• Added the following values to the Tag Values, on page 328 table:
1. FLT_ENABLED_SERVICES for the messages CONFIG_AGENT_SERVICE_EVENT and
SET_AGENT_SERVICE_DATA_REQ.
2. NUM_OF_ENABLED_SERVICES for the messages CONFIG_AGENT_SERVICE_EVENT and
SET_AGENT_SERVICE_DATA_REQ.
3. CCAI_CONFIG_ID for the message AGENT_PRE_CALL_EVENT
4. NUM_POSITIVE_ANSWERS_SUGGESTIONS for the message
SET_AGENT_SERVICE_DATA_REQ
5. NUM_NEGATIVE_ANSWERS_SUGGESTIONS for the message
SET_AGENT_SERVICE_DATA_REQ
• Add a new row for the CONFIG_MSG_AGENT_SERVICE_MASK to Table 11: CTI Service Masks.
Protocol Version 23
Following is a list of changes made in Protocol Version 23:
• Added START_NETWORK_RECORDING_REQ and STOP_NETWORK_RECORDING_REQ to
Client Control Service.
• Added the following values to the Tag Values table:
• FLT_TASK_ID_TAG for the AGENT_TASKS_EVENT message
• CALL_VAR_1_TAG through CALL_VAR_10_TAG for the SNAPSHOT_TASK_EVENT message
• DESKTOP_CONNECTED_FLAG_TAG for the AGENT_TASKS_REQUEST_EVENT message
• TEXT_TAG for the AGENT_TASKS_END_EVENT message
• NUM_MRDS_TAG for the DESKTOP_CONNECTED_IND message
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
436
Changes and Additions
Protocol Version 22
• NETWORK_RECORDING_ENDED_EVENT
• NETWORK_RECORDING_FAILED_EVENT
• NETWORK_RECORDING_TARGET_INFO_EVENT
Protocol Version 22
Following is a list of changes made in Protocol Version 22:
• Added MaxBeyondTaskLimit under AGENT_STATE_EVENT and QUERY_AGENT_STATE_CONF.
• Added FltPrecisionQueueID and FltPrecisionQueueName under CONFIG_SKILL_GROUP_EVENT.
• Added AgentDeskSettingsID in CONFIG_AGENT_EVENT.
• Added CONFIG_AGENT_DESK_SETTINGS_EVENT and CONFIG_PERIPHERAL_EVENT.
• Added PeripheralConfigKey and AgentDeskSettingsConfigKey under CONFIG_KEY_EVENT and
CONFIG_BEGIN_EVENT.
• Changed the behavior of CALL_DATA_UPDATE_EVENT for ECC variables.
Protocol Version 21
Following is a list of changes made in Protocol Version 21:
• Added NumMRDs, FLTAgentMRDID, and FltAgentMRDState under CONFIG_AGENT_EVENT.
• Added a new Message with the type 259. This Message is reserved for internal use only.
• Changed the behavior of the PeripheralType field in the OPEN_CONF message.
Protocol Version 20
Following is a list of additional changes made in Protocol Version 20 (Unified CCE Release11.5(1)):
Important In the CTI Server Protocol Version 20 the floating field tag and length size changed from 1 byte to 2 byte
USHORT.
• Added the fixed AgentSkillTargetID and floating AgentID fields to the AGENT_PRE_CALL_EVENT
message.
• Added the CONFIG_MRD_EVENT message.
• Added bit mask value 32=Media Routing Domain Information to the CONFIG_REQUEST_EVENT
message ConfigInformation field. Added a cross-reference to this field from the OPEN_REQ
message ConfigMsgMask field.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
437
Changes and Additions
Protocol Version 19
• Added bit mask value 32=Media Routing Domain Information to the CONFIG_BEGIN_EVENT
message ConfigInformation field.
• Added the MR_DOMAIN_ID_TAG, DESCRIPTION_TAG, ENTERPRISE_NAME_TAG,
MAX_TASK_DURATION_TAG, AND INTERRUPTIBLE_TAG to the event
CONFIG_MRD_EVENT.
• Added that the AGENT_PRE_CALL_ABORT_ EVENT message is sent to the to ALL_EVENTS client.
• Added the following values to the Tag Values table:
• SSO_ENABLED_TAG for the CONFIG_AGENT_EVENT and SET_AGENT_STATE_REQ
• FLT_TASK_ID_TAG for the AGENT_TASKS_RESP message
• FLT_ICM_DISP_TAG and FLT_APP_DISP_TAG for the MEDIA_LOGOUT_IND message
• For the CONFIG_AGENT_EVENT message, the length of the LoginName field is increased to 255
Bytes.
• Floating field subfields have changed:
• The Tag subfield is a Data Type of USHORT and a Byte Size of 2.
• The FieldLength subfield is a Data Type of USHORT and a Byte Size of 2.
• Added or modified these tags in the Tag Values table for the SNAPSHOT_TASKS_RESP message:
SCRIPT_SELECTOR_TAG , APPLICATION_STRING1_TAG, APPLICATION_STRING2_TAG,
CALL_VAR_1_TAG through CALL_VAR_10_TAG, NAMED_VARIABLE_ TAG,
NAMED_ARRAY_TAG.
• Added new TaskState Values that may appear in SNAPSHOT_TASK_RESP messages.
• Added the following values to the Disposition Codes table for nonvoice tasks:
• 63=Task Transferred
• 64=Application Disconnected
• 65=Task Transferred on Agent Logout
Protocol Version 19
The following is a list of changes made for CTI Server in Protocol Version 19:
• Updated Message Types in Messaging Conventions chapter.
• Added Configuration Acquisition Messages section in Application Level Interfaces chapter.
• Added row containing INTERNAL_AGENT_STATE_TAG to Tag Values. Table Tag Values.
• Added values 27 to 37 for outbound call types to CallType Values CallType Values, on page 353.
• Added row containing InternalAgentState to QUERY_AGENT_STATE CONF Message Form to Table
Message Types.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
438
Changes and Additions
Protocol Version 18
• Added Agent’s Internal States and their Status Values to Table Agent Internal States Message Values.
• Removed the ClientAddressIPV6 and SendingAddressIPV6 elements and the
CLIENT_ADDRESS_IPV6_TAG (226) and SENDING_ADDRESS_IPV6_TAG(227) tags due to a
change in the handling of IPv6 addresses.
• Changed ClientAddress and SendingAddress elements’ size from 16 byte to 64 byte to support IPv6
addresses.
• Added the DepartmentID field to the following messages:
• OPEN_CONF
• AGENT_STATE_EVENT
• AGENT_TEAM_CONFIG_EVENT
• QUERY_AGENT_STATE_CONF
Protocol Version 18
The following is a list of changes made for CTI Server in Protocol Version 18 (Unified CCE version 10.0(1)
- internal use only):
• Added values 247 to 254 to Tag Values Table Tag Values.
Protocol Version 17
The following is a list of changes made for CTI Server in Protocol Version 17 (Unified CCE version 9.0(1)
- internal use only):
Added row containing OPTIONS_TAG to Tag Values Table Tag Values.
Protocol Version 16
The following is a list of changes made for CTI Server in Protocol Version 16 (Unified CCE verion 9.0(1)).
• Added Agent TeamName to AGENT_TEAM_CONFIG_EVENT Table Supervisor Service
Added AGENT_TEAM_NAME_TAG(243) to Table Tag Values
Added Direction to AGENT_STATE_EVENT Table Tag Values
Added DIRECTION_TAG(244) to Table Tag Values
Protocol Version 15
The following is a list of additions and changes made to the CTI Server in Protocol Version 15 (Unified CCE
Version 8.5(x)).
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
439
Changes and Additions
Protocol Version 14
Protocol Version 14
The following is a list of additions and changes made to the CTI Server in Protocol Version 14 (Unified CCE
Version 8.0(x)).
• Changed the VersionNumber field in OPEN_REQ to 14 from 13.
Added new floating field tags to Table Tag Values:
• REQUESTING_DEVICE_ID_TAG (219)
REQUESTING_DEVICE_ID_TYPE_TAG (220)
PRE_CALL_INVOKE_ID_TAG (221)
ENTERPRISE_QUEUE_TIME (222)
CALL_REFERENCE_ID_TAG (223)
MULTI_LINE_AGENT_CONTROL_TAG (224)
NETWORK_CONTROLLED_TAG (225)
CLIENT_ADDRESS_IPV6_TAG (226)
SENDING_ADDRESS_IPV6_TAG(227)
NUM_PERIPHERALS_TAG(228)
COC_CONNECTION_CALL_ID_TAG(229)
COC_CALL_CONNECTION_DEVICE_ID_TYPE_TAG(230)
COC_CALL_CONNECTION_DEVICE_ID_TYPE_TAG(231)
CALL_ORIGINATED_FROM_TAG(232)
SET_APPDATA_CALLID_TAG(233)
CLIENT_SHARE_KEY_TAG(234)
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
440
Changes and Additions
Protocol Version 14
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
441
Changes and Additions
Protocol Versions 10-13
CLIENT_SESSION_OPENED_EVENT
CLIENT_SESSION_CLOSED_EVENT
EMERGENCY_CALL_EVENT
START_RECORDING_REQ
START_RECORDING_CONF
STOP_RECORDING_REQ
STOP_RECORDING_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
442
Changes and Additions
Protocol Version 9
Protocol Version 9
The following is a list of additions and changes made to the CTI Server in Protocol Version 9 (ICM Version
5.0).
• Added Server Service. See the section “Server Service” in Chapter 5, “Application Level Interfaces.”
• Added the CampaignID and QueryRuleID fields to the SET_CALL_DATA_REQ and
CALL_DATA_UPDATE_EVENT messages.
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
443
Changes and Additions
Protocol Version 8
• During an OPEN_REQ of an ALL_EVENTS client session, additional SYSTEM_EVENTs are now sent
to the ALL_EVENTS client to indicate the status of each peripheral associated with the PG.
• Added AgentAvailabilityStatus and ICMAgentID fields to QUERY_AGENT_STATE_CONF and
AGENT_STATE_EVENT.
• Added field AgentsICMAvailable and AgentsApplicationAvailable to
QUERY_SKILL_GROUP_STATISTICS_CONF.
• Added fields ICMAvailableTimeSession, RoutableTimeSession, ICMAvailableTimeToday, and
RoutableTimeToday to QUERY_AGENT_STATISTICS_CONF.
• Added ICMAgentID, AgentExtension, AgentID, and AgentInstrument fields to
QUERY_AGENT_STATE_REQ.
• Updates to several tables in Chapter 6, “Constants and Status Codes.”
Protocol Version 8
The following is a list of additions and changes made to the CTI Server in Protocol Version 8 (ICM Version
4.6).
• Moved the RTP_STARTED_EVENT and RTP_STOPPED_EVENT messages to the ClientEvents
Service.
• Added AgentInstrument optional field to the following messages:
• ALTERNATE_CALL_REQ
• CLEAR_CALL_REQ
• CONFERENCE_CALL_REQ
• DEFLECT_CALL_REQ
• HOLD_CALL_REQ
• RECONNECT_CALL_REQ
• RETRIEVE_CALL_REQ
• TRANSFER_CALL_REQ
• SEND_DTMF_SIGNAL_REQ
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
444
Changes and Additions
Protocol Version 7
• Added the CustomerPhoneNumber, and CustomerAccountNumber fields. Developers may receive these
fields in the CALL_DATA_UPDATE_EVENT messages.
Protocol Version 7
The following is a list of additions and changes made to the CTI Server in Protocol Version 7 (ICM Version
4.5).
• Added the RTP_STARTED_EVENT and RTP_STOPPED_EVENT messages
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
445
Changes and Additions
Protocol Version 6
Protocol Version 6
The following is a list of additions and changes made to the CTI Server in Protocol Version 6 (ICM Version
4.1).
• Added the NAMEDVAR and NAMEDARRAY data types.
• Added ICRCentralControllerTime and SystemCapabilities fields to the OPEN_CONF and
SYSTEM_EVENT messages.
• System Events Service renamed to Miscellaneous Services.
• NamedVariable and NamedArray optional fields added to the following messages:
• BEGIN_CALL_EVENT
• CALL_DATA_UPDATE_EVENT
• CALL_TRANSLATION_ROUTE_EVENT
• SET_CALL_DATA_REQ
• CONFERENCE_CALL_REQ
• CONSULTATION_CALL_REQ
• MAKE_CALL_REQ
• MAKE_PREDICTIVE_CALL_REQ
• TRANSFER_CALL_REQ
• SNAPSHOT_CALL_CONF
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
446
Changes and Additions
Protocol Version 6
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
447
Changes and Additions
Protocol Version 5
• New LineTypes LINETYPE_OUTBOUND and LINETYPE_DID added to the LineTypes table (Table
6-14 LineType Values).
• Added ServiceNumber, ServiceID, SkillGroupNumber, SkillGroupID, and SkillGroupPriority fields to
AGENT_PRECALL_EVENT message.
• Added note for CALL_ESTABLISHED_EVENT for Spectrum ACDs.
• Added /CCT (Call Control Table) optional field to the MAKE_CALL_REQ and
MAKE_PREDICTIVE_CALL_REQ messages.
Protocol Version 5
The following is a list of additions and changes made to the CTI Server in Protocol Version 5 (ICM Version
4.0).
• Added Peripheral Monitor service and related messages.
• Added a new MonitorID field to all Call and Agent Event messages.
• Added Client Monitor service and related messages.
• Added CallingDeviceType and CallingDeviceID fields to the CALL_SERVICE_INITIATED_EVENT
message.
• Increased the maximum number of skill groups from 10 to 20.
• Added AlertRings, CallOption, AuthorizationCode, and AccountCode fields to the
CONSULTATION_CALL_REQ, MAKE_CALL_REQ, and TRANSFER_CALL_REQ messages.
• Readded MAKE_PREDICTIVE_CALL_REQ and MAKE_PREDICTIVE_CALL_CONF messages.
• Added new SYS_PERIPHERAL_GATEWAY_OFFLINE System Event ID to the SystemEventID Values
table (Table PeripheralType Values, on page 346).
• Added new AM_NONE, AM_NONE_NO_MODEM and AM_CONNECT_NO_MODEM
AnsweringMachine values to the AnsweringMachine Values table (Table AnsweringMachine Values,
on page 368).
• ANSWER_CALL_REQ message (Table SystemEventID Values, on page 326) revised for peripherals
that do not provide alerting call identification.
• Added fields for single step conference to the CONFERENCE_CALL_REQ message:
• CallPlacementType
• CallMannerType
• AlertRings
• CallOption
• FacilityType
• Priority
• PostRoute
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
448
Changes and Additions
Protocol Version 5
• DialedNumber
• UserToUserInfo
• CallVariable1 – CallVariable10
• CallWrapupData
• FacilityCode
• AuthorizationCode
• AccountCode
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
449
Changes and Additions
Protocol Version 5
CTI Server Message Reference Guide(Protocol Version 24) for Cisco Unified Contact Center Enterprise, Release 12.6(1)
450