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 2 Deployment Models<br />

Traditional ACD Integration<br />

OL-8669-05<br />

Traditional ACD Integration<br />

For enterprises that want to integrate traditional ACDs with their <strong>Unified</strong> CCE deployment, several<br />

options exist. For enterprises that want to load-balance calls between a traditional ACD site and a<br />

<strong>Unified</strong> CCE site, a pre-routing Network Interface Controller (NIC) could be added. (See Figure 2-14.)<br />

This requires that the <strong>Unified</strong> ICM have a NIC that supports the PSTN service provider. In this scenario,<br />

the PSTN will query the <strong>Unified</strong> ICM Central Controller (via the NIC) to determine which site is best,<br />

and the <strong>Unified</strong> ICM response back to the PSTN will instruct the PSTN where (which site) to deliver the<br />

call. Any call data provided by the PSTN to the <strong>Unified</strong> ICM will be passed to the agent desktop<br />

(traditional ACD or <strong>Unified</strong> CCE).<br />

In order to transfer calls between the two sites (ACD site and <strong>Unified</strong> CCE site), a PSTN transfer service<br />

could be used. Use of a PSTN transfer service avoids any double trunking of calls at either site. An<br />

alternative to using a PSTN transfer service is to deploy TDM voice circuits between the traditional ACD<br />

and <strong>Unified</strong> CCE voice gateways. In that environment, any transfer of a call back to the original site will<br />

result in double trunking between the two sites. Each additional transfer between sites will result in an<br />

additional TDM voice circuit being utilized.<br />

Figure 2-14 Integrating a Traditional ACD with a <strong>Unified</strong> CCE Site<br />

PSTN<br />

V<br />

IP voice<br />

TDM voice<br />

CTI/Call<br />

control data<br />

ACD<br />

IP IVR<br />

NIC<br />

M<br />

CallManager<br />

IP<br />

PG/CTI<br />

server<br />

PG/CTI<br />

server<br />

ICM Central<br />

Controller<br />

IP phones and IPCC agent desktops<br />

An alternative to pre-routing calls from the PSTN is to have the PSTN deliver calls to just one site or to<br />

split the calls across the two sites according to some set of static rules provisioned in the PSTN. When<br />

the call arrives at either site, either the traditional ACD or the <strong>Cisco</strong> <strong>Unified</strong> CallManager will generate<br />

a route request to the <strong>Unified</strong> ICM to determine which site is best for this call. If the call needs to be<br />

delivered to an agent at the opposite site from where the call was originally routed, then TDM circuits<br />

IP<br />

IP<br />

76612<br />

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

2-39

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

Saved successfully!

Ooh no, something went wrong!