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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2 Deployment Models<br />

Parent/Child<br />

OL-8669-05<br />

General Deployment Options<br />

However, if the deployment that is being installed falls within the parameters required by System <strong>Unified</strong><br />

CCE, there are several benefits:<br />

Streamlined installation — You can install and configure System <strong>Unified</strong> CCE as a single unit rather<br />

than having to install and configure each component separately.<br />

Web-based administration for both registry and database configuration — All configuration is done<br />

through the web interface, so it is no longer necessary to run local setup to change registry<br />

configuration.<br />

Certified configurations that have been tested to work together<br />

For a large number of <strong>Unified</strong> CCE customers, System <strong>Unified</strong> CCE will meet their requirements and<br />

provide benefits of simpler installation and administration. For customers with more complex<br />

requirements, traditional <strong>Unified</strong> CCE is supported with manual installation and administration using<br />

<strong>Unified</strong> ICM Setup and <strong>Unified</strong> ICM Configuration Manager. For those configurations that System<br />

<strong>Unified</strong> CCE does fit, the reduced deployment time and ease of administration provide significant<br />

benefits.<br />

<strong>Unified</strong> CCE Gateway PG allows <strong>Unified</strong> CCE or <strong>Unified</strong> CCX to appear as a traditional ACD connected<br />

to the <strong>Unified</strong> ICM system. <strong>Unified</strong> CCE Gateway PG does this by providing a PG to the <strong>Unified</strong> ICM<br />

system that communicates to the CTI interface of <strong>Unified</strong> CCE System PG or <strong>Unified</strong> CCX/CRS.<br />

When <strong>Unified</strong> CCE Gateway PG is used in a deployment, its relationship of <strong>Unified</strong> ICM is termed a<br />

parent and <strong>Unified</strong> CCE is called the child:<br />

Parent<br />

The <strong>Unified</strong> ICM system that serves as the network or enterprise routing point. The child looks like<br />

an ACD to the parent, which uses the appropriate <strong>Unified</strong> CCE Gateway PG (<strong>Enterprise</strong> or Express)<br />

to communicate to the CTI interface on the child <strong>Unified</strong> CCE. The parent can perform all functions<br />

that a <strong>Unified</strong> ICM can usually perform, including pre- and post-routing and end-to-end call tracking<br />

using translation routes.<br />

Child<br />

The <strong>Unified</strong> CCE System PG or <strong>Unified</strong> CCX system that is set up to function as an ACD. The child<br />

can receive calls that are translation-routed from the parent, but it is not aware of any other<br />

peripherals attached to the parent. The child can also post-route calls from the <strong>Unified</strong> CCE to the<br />

parent, where the call can be handled like any other <strong>Unified</strong> ICM call. For example, the call could<br />

be translation-routed to any (TDM or IP) ACD controlled by the <strong>Unified</strong> ICM or queued in the<br />

<strong>Unified</strong> ICM network queue point with <strong>Unified</strong> CVP.<br />

In the parent/child model, the child <strong>Unified</strong> CCE is configured to function completely on its own and<br />

does not need the connection to the parent to route calls to agents. This independence provides complete<br />

local survivability for mission-critical contact centers if the network between the child and parent goes<br />

down or if there is a problem with the parent or the <strong>Unified</strong> CCE Gateway PG connection. Configuration<br />

objects entered into the child system can automatically be sent to the parent <strong>Unified</strong> ICM and inserted<br />

into the <strong>Unified</strong> ICM configuration, thus eliminating the need to configure objects twice, once in the<br />

local ACD and again to match the configuration in the <strong>Unified</strong> ICM itself for routing and reporting. This<br />

functionality can also be turned off for situations where the customer does not want automatic<br />

configuration updates, such as with an outsourcer using the <strong>Unified</strong> CCE child system where not all of<br />

the agents, skill groups, and call types on that child system apply to the customer's <strong>Unified</strong> ICM system.<br />

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

2-5

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

Saved successfully!

Ooh no, something went wrong!