Cisco Cisco IPCC Web Option Design Guide
12-23
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 12 Bandwidth Provisioning and QoS Considerations
Bandwidth Provisioning
Note
Call variables used on the child PG are transmitted to the parent PG regardless of their use or the setting
of the MAPVAR parameter. For example, if call variables 1 through 8 are used on the child PG but are
never referenced on the parent PG (and assume MAPVAR = EEEEEEEEEE, meaning Export all but
Import nothing), they will still be transmitted to the PG where the filtering takes place, therefore
bandwidth is still required. For the reverse situation, bandwidth is spared. For example, if the map setting
is MAPVAR = IIIIIIIIII (Import all but Export nothing), then bandwidth is spared. Call variable data will
not be transmitted to the child PG on a ROUTE_SELECT response.
of the MAPVAR parameter. For example, if call variables 1 through 8 are used on the child PG but are
never referenced on the parent PG (and assume MAPVAR = EEEEEEEEEE, meaning Export all but
Import nothing), they will still be transmitted to the PG where the filtering takes place, therefore
bandwidth is still required. For the reverse situation, bandwidth is spared. For example, if the map setting
is MAPVAR = IIIIIIIIII (Import all but Export nothing), then bandwidth is spared. Call variable data will
not be transmitted to the child PG on a ROUTE_SELECT response.
Basic Call Flow Example
Assume a call rate of 300 simple calls per minute (5 calls per second) and the agents are all in a single
skill group with no passing of call variables or ECC data. The required bandwidth in this case is:
skill group with no passing of call variables or ECC data. The required bandwidth in this case is:
5
2700 = 13,500 bytes per second = 108 kbps of required bandwidth
Note that a more complex call flow or a call flow involving call data could easily increase this bandwidth
requirement.
requirement.
Autoconfiguration
If autoconfiguration is used, it is possible that the entire agent, skill group, and route-point configuration
could be transmitted from the child PG to the parent PG. If not much bandwidth is available, it could
take considerable time for this data to be transmitted.
could be transmitted from the child PG to the parent PG. If not much bandwidth is available, it could
take considerable time for this data to be transmitted.
lists the approximate number of bytes (worst case) that are transmitted for each of the data
entities. If you know the size of the configuration on a child PG, you can calculate the total number of
bytes of configuration data that will be transmitted. Note that the values in are worse-case estimates that
assume transmitting only one item per record with each field having the maximum possible size (which
is extremely unlikely).
bytes of configuration data that will be transmitted. Note that the values in are worse-case estimates that
assume transmitting only one item per record with each field having the maximum possible size (which
is extremely unlikely).
For example, if the child PG has 100 agents, 10 call types, 5 skill groups, and 20 route points, then the
amount of configuration data transmitted could be estimated as follows:
amount of configuration data transmitted could be estimated as follows:
100 agents
500 bytes = 50,000 bytes
10 call types
250 bytes = 2,500 bytes
5 skill groups
625 bytes = 3,125 bytes
20 route points
315 bytes = 6,300 bytes
50,000 + 2,500 + 3,125 + 6,300 = 61,925 bytes
The total amount of data (approximate maximum) transmitted for this configuration is 61,925 bytes.
Table 12-7
Bytes Transmitted per Data Item Under Worst-Case Conditions
Data Item Transmitted
Size
Agent
500 bytes
Call type
250 bytes
Skill group
625 bytes
Device (route point, device target, and so forth)
315 bytes