Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide

The All Events service is conceptually similar to the Client Events service, and uses many of the same 
messages. Unlike the Client Events service, however, the CTI client that has been granted All Events 
service is associated with a CTI Bridge application (see “Simplex/Duplex ConfigurationSection” in 
Chapter

). Such a  CTI Client receives messages for all call events, not just those associated with a 

specific teleset. Also, because there is no specific teleset association, this CTI client may receive call 
events that occur before any agent has been chosen by the peripheral for the call. The following messages 
describe these additional events. 

 lists the All Events service messages.

CALL_DELIVERED_EVENT

When an inbound ACD trunk is seized.

CALL_TRANSLATION_ 
ROUTE_ EVENT

When a call is routed to a peripheral 
monitored by the PG via a translation route.

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 (see 

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. The 
CALL_TRANSLATION_ROUTE_EVENT message is defined in 

.

MessageHeader

Standard message header. 
MessageType = 22.

MHDR

8

NumNamedVariables

The number of Named Variable 
floating fields present in the 
floating part of the message.

USHORT

2

NumNamedArrays

The number of NamedArray 
floating fields present in the 
floating part of the message.

USHORT

2