Cisco Cisco Unified Contact Center Management Portal 11.0(1) Release Note
Chapter 11 Bandwidth Provisioning and QoS Considerations
Cisco Unified Contact Center Enterprise 8.x SRND
348
Application Name
Message Types
Call status information
Monitoring agent states
Silent monitoring
Finesse Desktop Bandwidth Usage
The bandwidth requirement for Cisco Finesse is a linear relationship based on the following:
• The number of agents active on the Finesse server
• The number of configured call and ECC variables
• The number of configured call and ECC variables
Table 26 shows the average bandwidth requirements on a per agent basis. This information is derived from
bandwidth testing and extrapolation of bandwidth data. Because there are many variables that can affect
bandwidth, a configuration that results in higher bandwidth usage was chosen to provide near worst-case
scenarios. If the agent’s WAN link meets or exceeds the bandwidth requirements shown in Table 26, the
Finesse Desktop can run without delays in message passing.
bandwidth testing and extrapolation of bandwidth data. Because there are many variables that can affect
bandwidth, a configuration that results in higher bandwidth usage was chosen to provide near worst-case
scenarios. If the agent’s WAN link meets or exceeds the bandwidth requirements shown in Table 26, the
Finesse Desktop can run without delays in message passing.
The most expensive operation from a network perspective is the agent/supervisor login. This operation
involves the web page load and includes the CTI login and display of the initial agent state. After the
desktop web page loads, the required bandwidth is significantly smaller. The data presented is based on the
load generated by the default Finesse desktop layout. Additional custom gadgets increase the network
bandwidth requirement based on the content contained in the custom gadget.
involves the web page load and includes the CTI login and display of the initial agent state. After the
desktop web page loads, the required bandwidth is significantly smaller. The data presented is based on the
load generated by the default Finesse desktop layout. Additional custom gadgets increase the network
bandwidth requirement based on the content contained in the custom gadget.
The login bandwidth is split between the following scenarios:
• No web browsing caching involved: This scenario typically only occurs on the first Finesse login
from a specific client PC and is presented to provide the worst case scenario. This value is the
minimum value to ensure that 2000 users can log in over a 5-minute period.
minimum value to ensure that 2000 users can log in over a 5-minute period.
• Login with browser caching: This scenario is the typical case for a user login. This value is the
minimum value to ensure that 2000 users can log in over a 5-minute period.
• Cached login with full user login completed within 10 seconds.
The bandwidth of the RTP streams for the call, recording, or monitoring sessions from the user’s phone
device is not included.
device is not included.
Table 26 Average Bandwidth Requirements for Cisco Finesse Agent
Activity
Average Download
Bandwidth (Kilobytes per
second)
Bandwidth (Kilobytes per
second)
Average Upload Bandwidth
(Kilobytes per second)
(Kilobytes per second)
Agent Login (no cache)
66.0
2.4
Agent login (cached)
24.6
1.6