Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide
4-31
CTI OS Developer’s Guide for Cisco Unified Contact Center Enterprise
Release 8.5(3)
Chapter 4 Building Your Application
Logging In and Logging Out an Agent
Note
It is the client application’s responsibility to keep track of whether the log in attempt is the first
attempt or during failover, and branch accordingly in the SetAgentMode() event to avoid calling the
Login() method during failover.
attempt or during failover, and branch accordingly in the SetAgentMode() event to avoid calling the
Login() method during failover.
The Login() method generates the following events:
•
QueryAgentStateConf()
•
AgentStateEvent(), if the agent is unknown or is logged out.
Note
The client application receiving the these events must check both the ENABLE_LOGOUT and
ENABLE_LOGOUT_WITH_REASON bitmasks. For more information, see
ENABLE_LOGOUT_WITH_REASON bitmasks. For more information, see
When not successful, the Login() method generates the eControlFailureConf() event.
How to Handle Duplicate Log In Attempts
Overview
A duplicate log in attempt occurs when an agent who is already logged in tries to log in a second time
using the same ID. Desktop applications must account for such a possible situation and have a plan for
dealing with it.
using the same ID. Desktop applications must account for such a possible situation and have a plan for
dealing with it.
You can handle duplicate log in attempts in three ways:
•
Allow the Duplicate Log In with No Warning
•
Allow the Duplicate Log In with a Warning
•
Do not allow a duplicate log in
You control how duplicate log in attempts are handled in two ways:
•
By configuring how duplicate log in attempts are handled on a global basis by creating custom
values in the CTI OS Server Registry. By using custom values in the CTI OS Server registry to
control how duplicate log in attempts are handled and downloading these settings to your desktop
application as described on page 4-35, you can enable flexibility without having to modify your
desktop application code.
values in the CTI OS Server Registry. By using custom values in the CTI OS Server registry to
control how duplicate log in attempts are handled and downloading these settings to your desktop
application as described on page 4-35, you can enable flexibility without having to modify your
desktop application code.
•
By implementing code in your desktop application to detect and to handle the duplicate log in
attempt error according to the custom values in the CTI OS Server Registry. You can write code to
handle duplicate log in attempts in each of the three ways listed above. When you need to change
how such attempts are handled, you simply change the registry settings; you would not have to
change the desktop application code.
attempt error according to the custom values in the CTI OS Server Registry. You can write code to
handle duplicate log in attempts in each of the three ways listed above. When you need to change
how such attempts are handled, you simply change the registry settings; you would not have to
change the desktop application code.
How to Create Values in the CTI OS Server Registry to Control Duplicate Log In Attempts
You can create keys in the CTI OS Server Registry that instruct desktop applications to handle duplicate
log in attempts in a specific way.
log in attempts in a specific way.