Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide

Page of 546
 
1-4
Cisco ICM Software CTI OS Developer’s Guide Release 6.0(0)
 
Chapter 1      Introduction
Leveraging CTI Application Event Flow
Figure 1-1
Typical Inbound Call Events Flow
The following events are generated, based on the state of the call:
BEGIN_CALL event indicates that the call has entered the setup phase.
CALL_DELIVERED event is generated when the call starts ringing. 
CALL_ESTABLISHED event is generated when the call is answered.
CALL_CLEARED event is generated when the voice connection is 
terminated (e.g. call hung up).
END_CALL even is generated when the logical call appearance (including 
call data) is complete.
In addition to the events and states shown in 
, the following are typical 
call events used for CTI applications:
CALL_HELD event is generated when the call transitions from the active to 
held state.
CALL_RETRIEVED event is generated when the call is removed from hold.
CALL_TRANSFERRED event indicates that the call has been transferred to 
another party.
CALL_CONFERENCED event indicates that a new party has been added to 
the call.
The foregoing is only a brief sample of the events available via CTI OS. The 
complete set of events available for CTI developers is detailed in later chapters in 
this guide.
Request-Response Paradigm
In addition to being able to respond to asynchronous events, a CTI enabled 
application can make programmatic requests for services via the CTI interface. 
Specifically, the CTI application uses the request-response mechanism to perform 
agent state and third-party call control, and to set call context data.
CALL
BEGIN
CALL
DELIVERED
CALL
ESTABLISHED
(answered)
CALL
CLEARED
CALL EN
TALKING
WRAP UP
RINGING
CALL SETUP