Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide
6-20
CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise
Release 8.5(3)
Chapter 6 Event Interfaces and Events
ICallEvents Interface
ICallEvents Interface
The Call object fires events on the ICallEvents interface. The following events are published to
subscribers of the ICallEvents interface.
subscribers of the ICallEvents interface.
Note
Many of the parameters that CTI OS receives from the CTI Server are inconsequential to most
customer applications. The most important parameters for doing a screenpop are included with the
events described in this section. The more inconsequential parameters are suppressed at the CTI OS
Server, to minimize network traffic to the clients. However, you can enable the complete set of
available event arguments by setting the following registry setting:
customer applications. The most important parameters for doing a screenpop are included with the
events described in this section. The more inconsequential parameters are suppressed at the CTI OS
Server, to minimize network traffic to the clients. However, you can enable the complete set of
available event arguments by setting the following registry setting:
[HKLM\Cisco Systems\CTIOS\Server\CallObject\MinimizeEventArgs = 0].
OnAgentPrecallEvent
Note
The OnAgentPrecallEvent event is applicable to Unified CCE only. The equivalent on all other TDM
events is TranslationRouteEvent.
events is TranslationRouteEvent.
The OnAgentPrecallEvent event is a pre-call indication that indicates the pending arrival of a call and
provides early access to the call context information. From a call flow perspective, this event can be used
to begin an application or database lookup for the call context data before the call actually arrives at the
agent’s teleset.
provides early access to the call context information. From a call flow perspective, this event can be used
to begin an application or database lookup for the call context data before the call actually arrives at the
agent’s teleset.
The contact is uniquely identified by the ICMEnterpriseUniqueID, which is a field based on the
Unified ICM’s 64-bit unique key (RouterCallKeyDay and RouterCallKeyCallID). This event
does not indicate the creation of a Call object on the CTI OS server – only that the contact is being
tracked. This is sufficient to get and set data, which enables some powerful data-prefetching
applications. When an OnCallBeginEvent follows for this same contact, the
ICMEnterpriseUniqueID
Unified ICM’s 64-bit unique key (RouterCallKeyDay and RouterCallKeyCallID). This event
does not indicate the creation of a Call object on the CTI OS server – only that the contact is being
tracked. This is sufficient to get and set data, which enables some powerful data-prefetching
applications. When an OnCallBeginEvent follows for this same contact, the
ICMEnterpriseUniqueID
field will be send along with the call data. At that point, a custom
application can set the call data on the appropriate call object.
Syntax
C++:
void OnAgentPrecallEvent(Arguments& args)
COM:
void OnAgentPrecallEvent (IArguments * args)
VB:
session_OnAgentPrecallEvent (ByVal args As CtiosCLIENTLib.IArguments)