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.

Traditional IVR Integration<br />

Using <strong>Cisco</strong> <strong>Unified</strong> CallManager Transfer and IVR Double Trunking<br />

2-46<br />

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

Chapter 2 Deployment Models<br />

Over time, it might become desirable to migrate the traditional IVR applications to the <strong>Unified</strong> CVP or<br />

<strong>Unified</strong> IP IVR. However, if a small percentage of traditional IVR applications still exist for very<br />

specific scenarios, then the IVR could be connected to a second voice gateway. (See Figure 2-20.) Calls<br />

arriving at the voice gateway from the PSTN would be routed by <strong>Cisco</strong> <strong>Unified</strong> CallManager.<br />

<strong>Cisco</strong> <strong>Unified</strong> CallManager could route specific DNs to the traditional IVR or let the <strong>Unified</strong> ICM or<br />

<strong>Unified</strong> CVP or <strong>Unified</strong> IP IVR determine when to transfer calls to the traditional IVR. If calls in the<br />

traditional IVR need to be transferred to a <strong>Unified</strong> CCE agent, then a second IVR port, trunk, and voice<br />

gateway port would be used for the duration of the call. Care should be taken to ensure that transfer<br />

scenarios do not allow multiple loops to be created because voice quality could suffer.<br />

Figure 2-20 Traditional IVR Integration Using <strong>Cisco</strong> <strong>Unified</strong> CallManager Transfer and IVR Double<br />

Trunking<br />

PSTN<br />

V<br />

IP voice<br />

TDM voice<br />

CTI/Call<br />

control data<br />

IVR PG<br />

IP IVR<br />

M<br />

CallManager<br />

IP<br />

PG/CTI<br />

server<br />

ICM Central<br />

Controller<br />

IP phones and IPCC agent desktops<br />

In this model, the TDM IVR is front-ended by either the <strong>Unified</strong> CVP using the voice gateway or the<br />

<strong>Unified</strong> IP IVR and <strong>Cisco</strong> <strong>Unified</strong> CallManager with <strong>Unified</strong> CCE to determine the location to provide<br />

call treatment.<br />

With <strong>Unified</strong> CVP, calls coming into the voice gateway would immediately start a routing dialog with<br />

the <strong>Unified</strong> ICM using the Service Control Interface (SCI). Based upon the initial dialed number or<br />

prompting in the <strong>Unified</strong> CVP, the <strong>Unified</strong> ICM would decide if the call needs to be sent to the TDM<br />

IVR for a specific self-service application or if the <strong>Unified</strong> CVP has the application available for the<br />

caller. If the call was sent to the TDM IVR, the TDM IVR sends a route request to the <strong>Unified</strong> ICM when<br />

the caller opts out. The reply is not sent back to the TDM IVR but back to the <strong>Unified</strong> CVP as the original<br />

routing client. <strong>Unified</strong> CVP would then take the call leg away from the TDM IVR and transfer it to the<br />

<strong>Unified</strong> CCE agent over the VoIP network or hold it in queue locally in the voice gateway.<br />

IP<br />

IP<br />

76616<br />

OL-8669-05

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

Saved successfully!

Ooh no, something went wrong!