Developer's Guide

5-42
CTI Server Message Reference Guide (Protocol Version 15) for Cisco Unified Contact Center Enterprise
Release 8.5(1)
Chapter 5 Application Level Interfaces
Peripheral Monitor Service
Peripheral Monitor Service
Peripheral Monitor service is similar to All Events service, and uses many of the same messages. Unlike
All Events service, however, the CTI client that has been granted Peripheral Monitor service must
specify for which devices and/or calls it wishes to receive events. The CTI client does this by establishing
a separate monitor for each device (Trunk, Trunk Group, or Agent Device) or call. The CTI client can
add or remove monitors at any time after it opens the session without closing and re-opening the session
or affecting any other established monitors. When a Peripheral Monitor client has multiple monitors that
are relevant to an event message, the client receives a corresponding number of event messages. The
MonitorID in each event message indicates which monitor is associated with that message. Peripheral
Monitor service clients also receive the CALL_TRANSLATION_ROUTE event described in Table 5-28.
Monitors are not preserved across CTI Server failures or client session failures. All monitors that a CTI
client creates are automatically terminated when the session is terminated. In addition, call monitors are
automatically terminated when the corresponding call ends. CTI clients must re-create monitors when
opening a new CTI session following a failure or loss of connection. No messages are received for any
events that may have occurred during the intervening time interval.
Table 5-29 lists the Peripheral Monitor service messages.
MONITOR_START_REQ
Use this message to create a new monitor for the given call or device.
Figure 5-2 depicts the Monitor Start message flow. The MONITOR_START_REQ and
MONITOR_START_CONF messages are defined in Table 5-30 and Table 5-31.
NamedVariable (optional) Call-related variable data that has a variable name
defined in the Unified CCE. There may be an
arbitrary number of Named Variable and
NamedArray fields in the message, subject to a
combined total limit of 2000 bytes. See Table 3-4
for the format of this field.
NAMED
VA R
251
NamedArray (optional) Call-related variable data that has an array variable
name defined in the Unified CCE. There may be an
arbitrary number of Named Variable and
NamedArray fields in the message, subject to a
combined total limit of 2000 bytes. See Table 3-5
for the format of this field.
NAMED
ARRAY
252
Maximum message size (including header): 3245
Table 5-28 CALL_TRANSLATION_ROUTE_EVENT Message Format (continued)
Table 5-29 Peripheral Monitor Service Messages
Message When Sent to CTI Client
MONITOR_START_REQ When a new monitor is created for a call or device.
MONITOR_STOP_REQ When a call or device monitor is terminated.
CHANGE_MONITOR_MASK_ REQ When a call and agent state event mask is changed.