Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide

To stop the failover procedure, call the Disconnect(args) method, with the Arguments instance 
containing the CTIOS_FORCEDDISCONNECT keyword as a parameter.

After the session is created, you must specify the connection mode for the session. You must use one of 
two modes:

Agent mode

Monitor mode

To ensure that you only try to set the connection mode on valid connections, you should place the code 
to set the connection mode within the OnConnection() event handler. The OnConnection() event is 
generated by a successful Connect() method.

The application should contain logic within the OnConnection() event handler to ensure it attempts 
to set the connection mode only during the initial connection, and not in an OnConnection() event 
due to failover.

You use Agent mode for connections when the client application must log in and control a specific agent. 
When in Agent mode, the connection also receives call events for calls on that agent’s instrument, as 
well as system events.

To select Agent mode for the connection, in the OnConnection() event:

Set properties for the agent.

The properties required for the agent depend on the type of ACD you are using. The 
following example demonstrates the required properties for IPCC users.

Set the agent for the Session object to that Agent object.

In the Java CIL only: If the SetAgent() method is called on a session in which the current 
agent is different than the agent parameter in the SetAgent() method, the Java CIL 
automatically calls the Disconnect() method on the current session instance, generating an 
OnCloseConnection() event, then attempts to reconnect, generating an OnConnection() 
event. Then the new agent is set as the current agent.