Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide
6-9
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions
Cisco CTI OS Release 7.2(1)
Chapter 6 Event Interfaces and Events
ISessionEvents Interface
The custom element hierarchy format is as follows:
“Grid”, <Arguments array>
“AgentStatistics”, <Arguments array>
“Columns”, <Arguments array>
“1”, <Arguments array>
“Type”, “Var1”
“Header”, “MyVar1”
Custom, CustomValue
...
“CallAppearance”, <Arguments array>
“SkillGroupStatistics”, <Arguments array>
...
...
“CustomGridData”, <Arguments array>
...
...
•
IPCCSilentMonitor – Arguments array that contains configuration information from the CTI
OS server registry’s IPCCSilentMonitor/ Name subtree.
OS server registry’s IPCCSilentMonitor/ Name subtree.
The IPCCSilentMonitor Arguments array contains a nested Arguments array with
key=”settings.” This array contains the following key-value pairs:
key=”settings.” This array contains the following key-value pairs:
Keyword
Value
MediaTerminationPort
integer
HeartBeatInterval
integer
TOS
boolean
MonitoringIPPort
integer
HeartbeatTimeout
integer
CCMBasedSilentMonitor
boolean
Configuration information for registry values added to the IPCCSilentMonitor/Settings registry
key is passed to the client in the OnGlobalSettingsConf event. Configuration information for
subkeys added to the Settings registry key is not passed in this event.
key is passed to the client in the OnGlobalSettingsConf event. Configuration information for
subkeys added to the Settings registry key is not passed in this event.
You can add custom keys to the CTI OS registry in the IPCCSilentMonitor subtree at the same
level as the Settings key. The IPCCSilentMonitor Arguments array within this event will contain
items corresponding to these custom keys. Any custom element that you add must follow the
same hierarchy in the registry as that used by the existing top level elements.
level as the Settings key. The IPCCSilentMonitor Arguments array within this event will contain
items corresponding to these custom keys. Any custom element that you add must follow the
same hierarchy in the registry as that used by the existing top level elements.