Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide

Page of 640
 
Chapter 4      Building Your Application
Connecting to the CTI OS Server
4-40
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
  •
OnSnapshotDeviceConf() for each device
  •
OnSnapshotCallConf
()
  •
OnMonitorModeEstablished()
How to Deal with Failover In Monitor Mode
The CTI OS CIL does not support failover for Monitor mode. Agents in monitor 
mode cannot recover their state after a failover. Furthermore, after a failover, the 
CTI OS CIL may leak Call objects.
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. 
The Monitor mode application is responsible for determining when all required 
servers are online. You can do this by 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.
Disconnecting from CTI OS Server
Disconnecting from CTI OS Server (via the Disconnect() method) before 
shutting down is an important part of the client application functionality. The 
Disconnect()
 method closes the socket connection between the client 
application and CTI OS. On most switches, it does not log the agent out. If no