Cisco Cisco IPCC Web Option Leaflet
12-22
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 12 Bandwidth Provisioning and QoS Considerations
Bandwidth Provisioning
Bandwidth Requirements for Unified CCE Gateway PG to System PG
illustrates the connection between the parent PG/PIM and the child system PG.
Figure 12-3
Connection Between Gateway PG and System PG
Note
Cisco does not recommend deploying the gateway PG remote from the system PG that it is monitoring.
The following factors affect the amount of data coming over the link once it is initialized:
•
Message sizes can vary depending upon their content (such as the size of extensions, agent IDs, and
call data). A Route Request with no data, for example, can be a very small message. If all call
variables and ECC variables are populated with large values, this will drastically affect the size of
the message.
call data). A Route Request with no data, for example, can be a very small message. If all call
variables and ECC variables are populated with large values, this will drastically affect the size of
the message.
•
Call scenarios can cause great variation in the number of messages per call that are transmitted over
the line. A simple call scenario might cause 21 messages to be transmitted over the line. More
complex call scenarios involving queuing, hold retrieves, conferences, or transfers will add greatly
to the number of messages per call that are transmitted over the line.
the line. A simple call scenario might cause 21 messages to be transmitted over the line. More
complex call scenarios involving queuing, hold retrieves, conferences, or transfers will add greatly
to the number of messages per call that are transmitted over the line.
•
The more skill groups to which an agent belongs, the more messages are transmitted over the line.
In a simple call scenario, each additional skill group adds two messages per call. These messages
are approximately 110 bytes each, depending on field sizes.
In a simple call scenario, each additional skill group adds two messages per call. These messages
are approximately 110 bytes each, depending on field sizes.
Basic Numbers (Where to Start:)
A basic call flow (simple ACD call with no hold, retrieve, conference, or transfer) with a single skill
group will be typically generate 21 messages, and you should plan a minimum of approximately
2700 bytes for the required bandwidth for it.
group will be typically generate 21 messages, and you should plan a minimum of approximately
2700 bytes for the required bandwidth for it.
In a basic call flow, there are four places where call variables and ECC data can be sent. Thus, if you use
call data and/or ECC variables, they will all be sent four times during the call flow. Using a lot of call
data could easily increase (by double, triple, or more) the 2700 bytes of estimated bandwidth per call.
call data and/or ECC variables, they will all be sent four times during the call flow. Using a lot of call
data could easily increase (by double, triple, or more) the 2700 bytes of estimated bandwidth per call.
143808
PG to CC Connection is
expected to be deployed
over a WAN
Unified CCE
with
System PG
(7.0) (Child)
GED-188
V11
Gateway to CTI-Server
connection is Highly
recommended to be local
connection is Highly
recommended to be local
Unified CM
IP IVR
Gateway
PG
Enterprise ICM
Router/Logger
Customer Legacy
ACD PG
Enterprise
ICM 7.0
(Parent)
IP IVR
System
PG
Customer Legacy
ACD PG
Router/Logger
CTI
SVR