19.07.2013 Views

Cisco Unified Contact Center Enterprise Solution Reference ...

Cisco Unified Contact Center Enterprise Solution Reference ...

Cisco Unified Contact Center Enterprise Solution Reference ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 11 Bandwidth Provisioning and QoS Considerations<br />

Traffic Flow<br />

Public Network Traffic Flow<br />

OL-8669-05<br />

Figure 11-2 Example of Different <strong>Cisco</strong> <strong>Unified</strong> CallManager Clusters<br />

IPT Cluster IPCC Cluster<br />

M M<br />

IP IP<br />

RSVP Agent<br />

RSVP Agent<br />

IP IP<br />

<strong>Unified</strong> CCE Network Architecture Overview<br />

For more information on CallManager 5.0 RSVP please refer to the <strong>Cisco</strong> <strong>Unified</strong> Communications<br />

SRND Based on <strong>Cisco</strong> <strong>Unified</strong> CallManager 5.0 at this URL: http://www.cisco.com/go/srnd<br />

This section briefly describes the traffic flows for the public and private networks.<br />

153157<br />

The active PG continuously updates the Central Controller call routers with state information related to<br />

agents, calls, queues, and so forth, at the respective call center sites. This type of PG-to-Central<br />

Controller traffic is real-time traffic. The PGs also send up historical data each half hour on the half hour.<br />

The historical data is low-priority, but it must complete its journey to the central site within the half hour<br />

(to get ready for the next half hour of data).<br />

When a PG starts, its configuration data is supplied from the central site so that it can know which agents,<br />

trunks, and so forth, it has to monitor. This configuration download can be a significant network<br />

bandwidth transient.<br />

In summary, traffic flows from PG to Central Controller can be classified into the following distinct<br />

flows:<br />

High-priority traffic — Includes routing and Device Management Protocol (DMP) control traffic. It<br />

is sent in TCP with the public high-priority IP address.<br />

Heartbeat traffic — UDP messages with the public high-priority IP address and in the port range of<br />

39500 to 39999. Heartbeats are transmitted at 400-ms intervals bidirectionally between the PG and<br />

the Central Controller. In <strong>Unified</strong> ICM Release 7.0, the UDP heartbeat is replaced with TCP<br />

keep-alive if QoS is enabled on the public network interface through the <strong>Unified</strong> ICM setup.<br />

Medium-priority traffic — Includes real-time traffic and configuration requests from the PG to the<br />

Central Controller. The medium-priority traffic is sent in TCP with the public high-priority IP<br />

address.<br />

<strong>Cisco</strong> <strong>Unified</strong> <strong>Contact</strong> <strong>Center</strong> <strong>Enterprise</strong> 7.x SRND<br />

11-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!