Cisco Cisco Computer Telephony Integration Option 8.5 Developer's Guide

When CCM based silent monitor is configured, this event tells the monitored application, for example an 
agent desktop, that it is being monitored. This event in addition to call events for the silent monitor call tells 
the monitoring application, for example a supervisor desktop, that silent monitor of the agent has begun.

At failover, the desktop may receive multiple OnSilentMonitorStartedEvents.

 void OnSilentMonitorStartedEvent(Arguments & args);

HRESULT OnSilentMonitorStartedEvent([in] Arguments* args);

  

Session_ OnSilentMonitorStartedEvent(ByVal args as CTIOSCLIENTLIB.IArguments)

args

Arguments array containing the following fields.

The OnSilentMonitorStartRequestedEvent event is fired to the subscriber to indicate that a silent 
monitor session request has arrived and that it will be established on its behalf if the 
DoDefaultMessageHandling parameter is set to True. The default behavior is to start sending audio and 

MonitoringIPAddress

STRING

TCP/IP address of the monitoring application 

MonitoringIPPort

INT

TCP/IP port of the monitoring application

SMSessionKey

UNSIGNED 
SHORT

Unique identifier for the Silent Monitor Session.

HeartbeatInterval

INT

Heartbeat interval for the silent monitor session

HeartbeatTimeout

INT

Timeout for no activity.

OriginatingServerID

STRING

TCP/IP Address:Port of the CTI OS server from which the 
request originated

OriginatingClientID

STRING

Client Identification of the monitoring application

SilentMonitorInitiatingAgentUID

STRING

Unique object ID of the agent that initiated silent 
monitor.

SilentMonitorInitiatingDeviceID

STRING

ID of the device that initiated silent monitor.

SilentMonitorTargetAgentUID

STRING

Unique object ID of the silently monitored agent.

SilentMonitorTargetDeviceID

STRING

ID of the silently monitored device.

SilentMonitorCallUID

STRING

Unique object ID of the silent monitor call.