Cisco Cisco Agent Desktop 8.5
3
Release Notes for Cisco Agent Desktop 8.0(1)
Limitations and Workarounds
Description: The agent’s multi-line phone is configured with more than the supported number of lines.
The correct error message to be displayed in this situation is, “The number of configured extensions for
the agent device exceeds the maximum allowed.”
The correct error message to be displayed in this situation is, “The number of configured extensions for
the agent device exceeds the maximum allowed.”
Workaround: In Cisco Unified Communications Manager, find the agent device and reconfigure it so
that it has no more than 1 ACD and 3 non-ACD lines. The agent then will be able to log in to CAD-BE.
that it has no more than 1 ACD and 3 non-ACD lines. The agent then will be able to log in to CAD-BE.
First Unified Outbound Dialer call on a dialer port results in Agent Desktop becoming stuck in the Hold state
Symptom: The first Unified Outbound Dialer call on a dialer port results in Agent Desktop becoming
stuck in the Hold state, and all the Outbound Dialer toolbar buttons becoming disabled.
stuck in the Hold state, and all the Outbound Dialer toolbar buttons becoming disabled.
Description: This occurs when the CTI OS service does not send all the necessary data to the Cisco
Desktop Enterprise service.
Desktop Enterprise service.
Workaround: Answer the call manually. If Agent Desktop does not start working, restart it.
Agent Desktop Login Dialog not completely visible when screen font size changed to 150%
Symptom: The Agent Desktop login dialog box is not completely visible the screen font size is changed
to 150% on a computer running Windows 7.
to 150% on a computer running Windows 7.
Description: This problem occurs because the dynamic nature of the login dialog box.
Workaround: Do one of the following to work around this problem:
•
Use 125% screen font size
•
Use the Tab key to move through all fields and buttons in the dialog box
•
Use key equivalents for buttons that are covered by the fields
No data available for the Last Queue Time enterprise variable
Symptom: The Last Queue Time enterprise variable is included in a macro action, but no data is ever
displayed for it.
displayed for it.
Description: No data is available for the Last Queue Time variable from ICM.
Workaround: The variable has been removed from CAD since it is not used.
Newer CAD version does not run in older Unified CCE environment
Symptom: CAD-BE does not start.
Description: CAD 8.0 is running in a Unified CCE 8.0 environment that includes Unified ICM 7.5(8).
Workaround: CAD 8.0 cannot run correctly in a mixed environment when components of that
environment are at an older version. Upgrade Unified ICM to 8.0 or roll back CAD to version 7.5(8).
environment are at an older version. Upgrade Unified ICM to 8.0 or roll back CAD to version 7.5(8).
CAD Configuration Setup entries overwritten after data restored
Symptom: Agents cannot log in to CAD.
Description: An older CAD system is backed up. A newer CAD system is installed on different servers,
and the data from the older CAD system is restored via CAD Configuration Setup. When CAD
Configuration Setup is run again, it is noted that the data from the previous CAD system has overwritten
the information that was entered for the new CAD system, so that IP addresses, passwords, and so on are
incorrect for the new system.
and the data from the older CAD system is restored via CAD Configuration Setup. When CAD
Configuration Setup is run again, it is noted that the data from the previous CAD system has overwritten
the information that was entered for the new CAD system, so that IP addresses, passwords, and so on are
incorrect for the new system.
Workaround: Re-enter the information for the new CAD system in CAD Configuration Setup.