Cisco Cisco Unified Contact Center Enterprise 9.0(1)
New and Changed Information
Release Notes for Cisco Unified Contact Center Enterprise Release 9.0(1)
Page | 7
For more information about bulk upload functionality, see the
and online help.
Prioritization of Re-skilling Operations
You can configure Unified CCMP 9.0(1) to process re-skilling requests ahead of other provisioning request
types such as agent creation. To access this setting; which is enabled by default, use the ICE Tool.
types such as agent creation. To access this setting; which is enabled by default, use the ICE Tool.
Activity Monitor
In Release 9.0(1), the Activity Monitor Tool replaces Unified CCMP Audit Reports. You can use the
Activity Monitor to view the outcome of historical provisioning activity as well as the status of current
operations.
Activity Monitor to view the outcome of historical provisioning activity as well as the status of current
operations.
For more information about Activity Monitor functionality, see the
Folder Tree Changes
Beginning with Release 9.0(1), the Unified CCMP folder tree interface supports drag and drop
functionality to move folders and has a context menu that you can use to create, edit, and delete folders.
functionality to move folders and has a context menu that you can use to create, edit, and delete folders.
The sort order for folders has changed. System folders are displayed first, in alphabetical order, followed by
tenant folders.
tenant folders.
Users with large numbers of folders can use a paged folder view for improved performance.
For more information about the changes to folder tree functionality, see the
SQL Server 2008 R2 64-Bit Support
For Unified CCMP 9.0(1), Microsoft SQL Server 2008 R2 64-bit is supported. Microsoft SQL Server 2005
32-bit is not supported in Unified CCMP 9.0(1).
32-bit is not supported in Unified CCMP 9.0(1).
Browser Support
Unified CCMP 9.0(1) supports Microsoft Internet Explorer versions 7, 8 and 9.
Congestion Control
In Unified CCE Release 9.0(1), a new Congestion Control feature is available to protect against
overloading the Central Controller during high call volume. When you enable Congestion Control, new
calls that exceed thecalls per second (CPS) capacity of the contact center are rejected and treated by the
routing clients at call-entry point. This avoids overload on the call router and ensures as designed call-
processing throughput.
overloading the Central Controller during high call volume. When you enable Congestion Control, new
calls that exceed thecalls per second (CPS) capacity of the contact center are rejected and treated by the
routing clients at call-entry point. This avoids overload on the call router and ensures as designed call-
processing throughput.
The measured CPS at the router is the trigger to identify congestion in the system. For a given deployment,
the supported capacity is set when the deployment type is selected. The router measures the incoming new
call requests from all the routing clients and computes a moving weighted average over the sample
duration. The congestion control algorithm uses three congestion levels and rejects and treats the incoming
calls as per the reduction percentage for that level. The change in congestion level is communicated to the
the supported capacity is set when the deployment type is selected. The router measures the incoming new
call requests from all the routing clients and computes a moving weighted average over the sample
duration. The congestion control algorithm uses three congestion levels and rejects and treats the incoming
calls as per the reduction percentage for that level. The change in congestion level is communicated to the