Cisco Cisco Customer Response Solution Downloads Design Guide
6-8
Cisco Unified Contact Center Express Solution Reference Network Design, Release 4.1
Chapter 6 Bandwidth, Security, and QoS Considerations
Estimating Bandwidth Consumption
Both monitoring and recording packets are real RTP streams and are not tagged with QoS marking by
default. Silent monitoring sessions are time sensitive because of the real-time nature. Tag the packets in
the network infrastructure to the same QoS marking as other real-time voice traffic. Properly provision
the priority queue to include silent monitoring traffic. Recording packets can be tagged with QoS
marking that is lower priority than the real-time voice traffic, because the packets do not need to be
delivered in real time. The ports used for monitoring and recording are listed in
default. Silent monitoring sessions are time sensitive because of the real-time nature. Tag the packets in
the network infrastructure to the same QoS marking as other real-time voice traffic. Properly provision
the priority queue to include silent monitoring traffic. Recording packets can be tagged with QoS
marking that is lower priority than the real-time voice traffic, because the packets do not need to be
delivered in real time. The ports used for monitoring and recording are listed in
, and can be used to classify monitoring or recording traffic.
For more information about QoS traffic classification, see
For provisioning guidelines for centralized call processing deployments, see the Cisco IP Telephony
Solution Reference Network Design (SRND) Cisco CallManager Releases 4.3 documentation, available
online at:
Solution Reference Network Design (SRND) Cisco CallManager Releases 4.3 documentation, available
online at:
CAD Desktop Applications Bandwidth Usage
The CAD desktop applications include the following:
•
Cisco Agent Desktop
•
Cisco Supervisor Desktop
•
Cisco Desktop Administrator
These applications also require a certain amount of bandwidth, although far less than the Desktop
Monitor service. In addition, the type of communication across the network is bursty. In general,
bandwidth usage is low when the agents are not performing any actions. When features or actions are
requested, the bandwidth increases for the time it takes to perform the action, which is usually less than
one second, then drop down to the steady state level. From a provisioning standpoint, one must determine
the probability of all the CAD agents performing a particular action at the same time. It might be more
helpful to characterize the call center and determine the maximum number of simultaneous actions (in
the worst case) to determine instantaneous bandwidth requirements, then determine what amount of
delay is tolerable for a percentage of the requested actions.
Monitor service. In addition, the type of communication across the network is bursty. In general,
bandwidth usage is low when the agents are not performing any actions. When features or actions are
requested, the bandwidth increases for the time it takes to perform the action, which is usually less than
one second, then drop down to the steady state level. From a provisioning standpoint, one must determine
the probability of all the CAD agents performing a particular action at the same time. It might be more
helpful to characterize the call center and determine the maximum number of simultaneous actions (in
the worst case) to determine instantaneous bandwidth requirements, then determine what amount of
delay is tolerable for a percentage of the requested actions.
For example, the raw bandwidth requirement for 300 CAD agents logging in simultaneously is about 4.5
Kilobytes/second and the login time is about 9 seconds (with no network delay) for each agent. If the
WAN link did not have this much bandwidth, logins would take longer as packets were queued before
being sent and received. If this caused the login attempts to take twice as long (18 seconds), would this
delay be acceptable? If not, more bandwidth should be provisioned.
Kilobytes/second and the login time is about 9 seconds (with no network delay) for each agent. If the
WAN link did not have this much bandwidth, logins would take longer as packets were queued before
being sent and received. If this caused the login attempts to take twice as long (18 seconds), would this
delay be acceptable? If not, more bandwidth should be provisioned.
Each of these applications communicates with the base CAD services running on server machines. In
addition, the agent desktop application communicates with the CTI server for call control actions and
state changes.
addition, the agent desktop application communicates with the CTI server for call control actions and
state changes.
displays the types of messaging for each application.