Cisco Cisco E-Mail Manager Unity Integration Option Dépliant
12-36
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 12 Bandwidth Provisioning and QoS Considerations
Bandwidth Provisioning
Calculating bandwidth requirements for servers that have only one network interface card (NIC) requires
adding the totals for each link entering the system. For example, for a standard reporting deployment
with an Administrative Workstation (AW), an Historical Data Server (HDS), and one NIC, you would
calculate the required bandwidth as follows:
adding the totals for each link entering the system. For example, for a standard reporting deployment
with an Administrative Workstation (AW), an Historical Data Server (HDS), and one NIC, you would
calculate the required bandwidth as follows:
Total bandwidth for reporting = Report data bandwidth + Reports bandwidth
However, for a large reporting deployment, the bandwidth is calculated as follows:
Total bandwidth for reporting = Report data bandwidth + WebView sever bandwidth
Note
Due to the nature of the recovery process, it is possible to experience a period of network slowdown
during periods of recovery.
during periods of recovery.
The following sections describe the calculations necessary to determine bandwidth requirements for
each network path shown in
each network path shown in
Report Data Bandwidth
The factors that affect the bandwidth between the Central Controller and a Distributor AW with an HDS
are calls per second (cps), the number of agents, and the use of Extended Call Context (ECC) variables.
Test result indicate the following general guidelines:
are calls per second (cps), the number of agents, and the use of Extended Call Context (ECC) variables.
Test result indicate the following general guidelines:
•
For every 10 cps, bandwidth consumption is about 42,000 bytes per second.
•
10 agents require approximately 12,000 bytes per second.
•
For each 1000 ECC bytes and 50 cps, the bandwidth consumption is 1,200,000 bytes per second.
Unified CCE provides a bandwidth calculator that aids in determining the bandwidth requirements for
report data. This calculator is available at
report data. This calculator is available at
http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html
WebView Server Bandwidth
WebView bandwidth becomes a factor only in large reporting deployments where the WebView servers
are not co-resident with the Distributor AW.
are not co-resident with the Distributor AW.
If WebView is deployed on separate servers, some configurations support up to four WebView Servers
per Distributor AW with an HDS. For more specific information on the number of supported WebView
servers, refer to the Hardware & System Software Specification (Bill of Materials) for Cisco ICM/IPCC
Enterprise & Hosted Editions, available at
per Distributor AW with an HDS. For more specific information on the number of supported WebView
servers, refer to the Hardware & System Software Specification (Bill of Materials) for Cisco ICM/IPCC
Enterprise & Hosted Editions, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_technical_reference_list.html
The factor that affects the bandwidth between the Distributor AW and a WebView server is the total
amount of reporting users that connect to the WebView server(s). Test results indicate that 50 reporting
users require approximately 314,573 bytes per second. A reporting user is defined as someone running:
amount of reporting users that connect to the WebView server(s). Test results indicate that 50 reporting
users require approximately 314,573 bytes per second. A reporting user is defined as someone running:
•
Two real-time reports refreshing every 20 seconds, with each report returning 50 or fewer rows. This
is equivalent to running a monitoring script.
is equivalent to running a monitoring script.
•
One historical report per hour
–
Half-hour historical reports are run for an 8-hour period
–
Daily historical reports run for a 40-hour period