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.

Other Considerations for High Availability<br />

Other Considerations for the Parent/Child Model<br />

3-50<br />

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

Chapter 3 Design Considerations for High Availability<br />

The parent/child model does not allow the child <strong>Unified</strong> CCE systems to use a local CVP at the child<br />

level. Only the parent can use CVP to perform network queuing across the entire system. Multi-channel<br />

components such as <strong>Cisco</strong> Email Manager or Web Collaboration and <strong>Unified</strong> OUTD may be installed<br />

only at the child <strong>Unified</strong> CCE level, not at the parent. They are treated as nodal implementations on a<br />

site-by-site basis.<br />

Other Considerations for High Availability<br />

A <strong>Unified</strong> CCE failover can affect other parts of the solution. Although <strong>Unified</strong> CCE may stay up and<br />

running, some data could be lost during its failover, or other products that depend on <strong>Unified</strong> CCE to<br />

function properly might not be able to handle a <strong>Unified</strong> CCE failover. This section examines what<br />

happens to other critical areas in the <strong>Unified</strong> CCE solution during and after failover.<br />

Reporting<br />

The <strong>Unified</strong> CCE reporting feature uses real-time, five-minute and half-hour intervals to build its<br />

reporting database. Therefore, at the end of each five-minute and half-hour interval, each Peripheral<br />

Gateway will gather the data it has kept locally and send it to the Call Routers. The Call Routers process<br />

the data and send it to their local Logger and Database Servers for historical data storage. If the<br />

deployment has the Historical Data Server (HDS) option, that data is then replicated to the HDS from<br />

the Logger as it is written to the Logger database.<br />

The Peripheral Gateways provide buffering (in memory and on disk) of the five-minute and half-hour<br />

data collected by the system to handle network connectivity failures or slow network response as well<br />

as automatic retransmission of data when the network service is restored. However, physical failure of<br />

both Peripheral Gateways in a redundant pair can result in loss of the half-hour or five-minute data that<br />

has not been transmitted to the Central Controller. <strong>Cisco</strong> recommends the use of redundant Peripheral<br />

Gateways to reduce the chance of losing both physical hardware devices and their associated data during<br />

an outage window.<br />

When agents log out, all their reporting statistics stop. The next time the agents log in, their real-time<br />

statistics start from zero. Typically, <strong>Unified</strong> ICM failover does not force the agents to log out; however,<br />

it does reset their agent statistics when the <strong>Unified</strong> ICM failover is complete, but their agent desktop<br />

functionality is restored back to its pre-failover state.<br />

For further information, refer to the Reporting Guide for <strong>Cisco</strong> IPCC <strong>Enterprise</strong> & Hosted Editions,<br />

Release 7.0(0), available at<br />

http://www.cisco.com/univercd/cc/td/doc/product/icm/icmentpr/icm70doc/report7/index.htm<br />

OL-8669-05

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

Saved successfully!

Ooh no, something went wrong!