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.

<strong>Cisco</strong> <strong>Unified</strong> Intelligent <strong>Contact</strong> Management (<strong>Unified</strong> ICM) Software<br />

1-8<br />

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

Chapter 1 Architecture Overview<br />

application. During a failure, the surviving side is said to be running in simplex mode and will continue<br />

to function this way until the redundant/duplex side is restored to service, then it will automatically<br />

return to duplex operation.<br />

The ICM software uses the concept of a customer instance to group all of the components under a single<br />

Call Router and Logger or Central Controller. The instance relationship ensures that all of the<br />

components related to the same system are joined under a single logical <strong>Unified</strong> CCE IP ACD. This<br />

concept is used only to support multiple customer instances in the <strong>Unified</strong> <strong>Contact</strong> <strong>Center</strong> Hosted<br />

(<strong>Unified</strong> CCH) that supports multi-tenant or shared servers that manage multiple customer instances. All<br />

<strong>Unified</strong> CCE systems are deployed as a single instance (using the same instance number in ICM Setup)<br />

across all the ICM components.<br />

Combined Routers and Loggers are often called the ICM Central Controller.When the Router and Logger<br />

modules run on the same server, the server is referred to as a Rogger. When the Call Router, Logger, and<br />

Peripheral Gateway modules run on the same server, the server is referred to as a Progger. In lab<br />

environments, the system Administrative Workstation (AW) can also be loaded onto the Progger to<br />

create a server known as a Sprawler configuration; however, this configuration is approved only for lab<br />

use and is not supported in customer production environments.<br />

For each <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster in your <strong>Unified</strong> CCE environment, you need a <strong>Cisco</strong> <strong>Unified</strong><br />

CallManager PIM on a separate Peripheral Gateway and physical server. For deployments requiring<br />

multiple PIMs for the same <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster, you need a separate PG and physical<br />

server for each PIM.<br />

For each <strong>Cisco</strong> <strong>Unified</strong> CallManager Peripheral Gateway, you need one CTI Server and one CTI OS to<br />

communicate with the desktops associated with the phones for that <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster.<br />

For each <strong>Unified</strong> IP IVR, you need one <strong>Unified</strong> IP IVR PIM. The server that runs the <strong>Cisco</strong> <strong>Unified</strong><br />

CallManager PIM, the CTI Server, the CTI OS, and the <strong>Unified</strong> IP IVR PIMs, is referred to as an Agent<br />

Peripheral Gateway (APG). Often, the <strong>Cisco</strong> <strong>Unified</strong> CallManager PIM, the CTI Server, the CTI OS, and<br />

multiple <strong>Unified</strong> IP IVR PIMs will run on the same server. Internal to the PG is a process called the PG<br />

Agent, which communicates from the PG to the Central Controller. Another internal PG process is the<br />

Open Peripheral Controller (OPC), which enables the other processes to communicate with each other<br />

and is also involved in synchronizing PGs in redundant PG deployments. Figure 1-4 shows the<br />

communications among the various PG software processes.<br />

OL-8669-05

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

Saved successfully!

Ooh no, something went wrong!