Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide
5-46
CTI OS Developer’s Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted
Release 8.0(1)
Chapter 5 CTI OS ActiveX Controls
The Silent Monitor StandAlone ActiveX Control
Following is a brief description of each event. These events are described in detail in the Session Object
and Silent Monitor Object sections of
and Silent Monitor Object sections of
Deployment
The StandAlone Com Object is a COM dll that needs to be registered on the client system via the
Regsvr32 Silentmonitorctl.dll. In addition, ccnsmt.dll and the two standard CTI OS COM dlls
(CTIOSClient.dll and Arguments.dll) are also required.
Regsvr32 Silentmonitorctl.dll. In addition, ccnsmt.dll and the two standard CTI OS COM dlls
(CTIOSClient.dll and Arguments.dll) are also required.
Sample Usage in Visual Basic 6.0
The following sample code assumes a VB 6.0 form with 4 buttons (Connect, Disconnect,
StartMonitoring and StopMonitoring. If the parameters are based on edit fields, the source code below
is all that is needed to silent monitor via CTI OS. It is important to note, that this control does not require
supervisor privileges or even any login. The only event handler shown below (OnSessionDisconnected)
is the one for a timed out Silent Monitor session. Other event handlers.
StartMonitoring and StopMonitoring. If the parameters are based on edit fields, the source code below
is all that is needed to silent monitor via CTI OS. It is important to note, that this control does not require
supervisor privileges or even any login. The only event handler shown below (OnSessionDisconnected)
is the one for a timed out Silent Monitor session. Other event handlers.
Dim WithEvents SilentMonitorCtl As SILENTMONITORCTLLib.SilentMonitor
Dim m_Args As New Arguments
Const CIL_OK = 1
Table 5-10
SilentMonitor Com Object Events
Event
Description
OnConnection
Indicates that the connect method was
successful in establishing a connection.
successful in establishing a connection.
OnConnectionFailure
Indicates that an active connection has failed.
Can also indicate a bad parameter in the
Connect method.
Can also indicate a bad parameter in the
Connect method.
OnMonitorModeEstablished
Signals a successful call to SetMsgFilte. The
call to Setmsgfilter is hidden by the
Standalone control.
call to Setmsgfilter is hidden by the
Standalone control.
OnConnectionClosed
Disconnect was called and the connection is
now closed.
now closed.
OnControlFailureConf
A ControlFailureConf was received and can
be handled.
be handled.
OnCtiOsFailure
A CtiosFailure event was received. This could
be Silent Monitor specific error code.
be Silent Monitor specific error code.
OnCallRTPStartedEvent,
OnCallRTPStoppedEvent
OnCallRTPStoppedEvent
RTP events have been received signaling the
start and stop of the RTP streams.
start and stop of the RTP streams.
OnSilentMonitorStatusReport
Event
Event
This event is used to report status from a
monitored client to the monitoring
application.
monitored client to the monitoring
application.
OnStartSilentMonitorConf,
OnStopSilentMonitorConf
OnStopSilentMonitorConf
These confs acknowledge that CTI OS
handled the StartMonitoring and
StopMonitoring request, respectively.
handled the StartMonitoring and
StopMonitoring request, respectively.
OnSilentMonitorSession
Disconnected
Disconnected
Indicates that the Silent Monitor session has
timed out on the monitoring side.
timed out on the monitoring side.