McDewey

Participant State (Caller) Participant State (Agent) Dialog State Event Method CTI Event Scenario DROPPED DROPPED DROPPED PUT CALL_CONNECTION_CLEARED Call is cleared DROPPED DROPPED DROPPED DELETE END_CALL_EVENT Call is removed The following table provides a list of CTI call events and their mapping to the Dialog state and Participant state for the call. This table is specifically oriented toward the caller making an outgoing call. If the recipient is also an agent, then the events go to the recipient. If the recipient is not an agent, events are not published to the recipient. Note Table 2: Outgoing Call Participant State(Recipient) Participant State (Caller) DialogState Event Method CTI Event Scenario Not a participant yet INITIATING INITIATING POST (Caller) BEGIN_CALL_EVENT Start of any call Not a participant yet INITIATING INITIATING POST (Caller) CALL_SERVICE_INITIATED_EVENT Caller takes phone off-hook Not a participant yet INITIATED INITIATED PUT (Caller) CALL_ORIGINATED_EVENT Caller dials number Not a participant yet FAILED FAILED PUT (Caller) CALL_FAILED_EVENT (BUSY) Destination is busy Not a participant yet FAILED FAILED PUT (Caller) CALL_FAILED_EVENT (BAD_DESTINATION) Destination is bad ALERTING INITIATED ALERTING PUT (Caller), POST (Recipient) (See the note that precedes this table.) CALL_DELIVERED Destination is recipient ACTIVE ACTIVE ACTIVE PUT CALL_ESTABLISHED Recipient answers call Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 128 Cisco Finesse Desktop APIs CTI Event Mappings for Dialog and Participant States