Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide
4-28
CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise
Release 8.5(3)
Chapter 4 Building Your Application
Connecting to the CTI OS Server
To deal with failover in Monitor Mode:
Step 1
When the application detects a failover, for example, in a CTIOSFailure() event indicating a connection
failure or an offline component, wait until the CIL has failed over and everything is back online and the
CIL is connected to CTI OS.
failure or an offline component, wait until the CIL has failed over and everything is back online and the
CIL is connected to CTI OS.
The Monitor Mode application determines when all required servers are online. You can do this by
monitoring OnCtiosFailure() events and keeping track of system status changes as they occur.
monitoring OnCtiosFailure() events and keeping track of system status changes as they occur.
Step 2
Use the Disconnect() method to disconnect the session from CTI OS.
Step 3
Follow the steps starting at the beginning of the section
to:
a.
Create a session instance.
b.
Set the event listener.
c.
Set connection parameters.
d.
Call the Connect() method.
e.
Set the connection mode in the OnConnection() event handler.
Settings Download
One of the many useful features of CTI OS is the ability to configure Agent Desktop settings once on
the server and have them available to all agent desktops via the RequestDesktopSettings()
method. You can make any changes once on the server instead of changing each and every desktop.
Settings download are considered as part of the process of setting up a connection that the client
application uses.
the server and have them available to all agent desktops via the RequestDesktopSettings()
method. You can make any changes once on the server instead of changing each and every desktop.
Settings download are considered as part of the process of setting up a connection that the client
application uses.
Desktop settings are stored in the registries on the machines running CTI OS Server. Centralizing the
desktop settings on the server streamlines the process of changing or updating the agent desktop. A
settings download occurs every time a client application connects and ensures that all the desktops are
based on the same settings.
desktop settings on the server streamlines the process of changing or updating the agent desktop. A
settings download occurs every time a client application connects and ensures that all the desktops are
based on the same settings.
You can downloading settings from CTI OS Server after connecting and setting the mode via the
RequestDesktopSettings()
RequestDesktopSettings()
method on the Session object. The
OnGlobalSettingsDownloadConf
event indicates success and also returns the settings which are
now available to the client application in the form of properties on the Session object. You can access
these properties via the GetValue() methods. Refer to Chapter 9 for a list of all the properties of the
Session object.
these properties via the GetValue() methods. Refer to Chapter 9 for a list of all the properties of the
Session object.
You can make the request for desktop settings either in the OnConnection event or in the
OnSetAgentModeEvent
OnSetAgentModeEvent
event (if Agent mode has been specified). Sample code:
Private Sub m_Session_OnConnection(ByVal pDispParam As Object)
'Issue a request to the server to send us all the Desktop 'Settings
m_Session.RequestDesktopSettings eAgentDesktop
End Sub
The OnGlobalSettingsDownloadConf event passes back the settings and you can access them
via the Session object. For example, the following snippet checks for Sound Preferences and specifically
to see if the Dial Tone is Mute or not:
via the Session object. For example, the following snippet checks for Sound Preferences and specifically
to see if the Dial Tone is Mute or not:
Private Sub m_session_OnGlobalSettingsDownloadConf(ByVal pDispParam As Object)
Dim SoundArgs As CTIOSARGUMENTSLib.Arguments
' check if "SoundPreferences is a valid property