Cisco Cisco Computer Telephony Integration Option 8.5 開発者ガイド

ページ / 668
 
Chapter 1      Introduction
Leveraging CTI Application Event Flow
1-4
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1) 
Figure 1-1
Typical Inbound Call Events Flow
The following events are generated, based on the state of the call:
  •
OnCallBegin event indicates that the call has entered the setup phase.
  •
OnCallDelivered event is generated when the call starts ringing. 
  •
OnCallEstablished event is generated when the call is answered.
  •
OnCallCleared event is generated when the voice connection is terminated 
(e.g. call hung up).
  •
OnCallEnd event 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:
  •
OnCallHeld event is generated when the call transitions from the active to 
held state.
  •
OnCallRetrieved event is generated when the call is removed from hold.
  •
OnCallTransferred event indicates that the call has been transferred to 
another party.
  •
OnCallConferenced 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 E
TALKING
WRAP UP
RINGING
CALL SETUP