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 />

Using IVR Double Trunking<br />

OL-8669-05<br />

Traditional IVR Integration<br />

If your traditional IVR application has a very high success rate, where most callers are completely<br />

self-served in the traditional IVR and only a very small percentage of callers ever need to be transferred<br />

to an agent, then it might be acceptable to double-trunk the calls in the traditional IVR for that small<br />

percentage of calls. (See Figure 2-19.) Unlike the previous model, if the traditional IVR has a Service<br />

Control Interface (SCI), then the initial call queuing could be done on the traditional IVR. The reason<br />

this is beneficial is that, in order to queue the call on the <strong>Unified</strong> IP IVR, a second traditional IVR port<br />

would be used to transfer the call to the <strong>Unified</strong> IP IVR. By performing the initial queuing on the<br />

traditional IVR, only one traditional IVR port is used during the initial queuing of the call. However, any<br />

subsequent queuing as a result of transfers or RONA treatment must be done on the <strong>Unified</strong> IP IVR to<br />

avoid any double trunking. If the traditional IVR does not have an SCI interface, then the IVR will just<br />

generate a post-route request to the <strong>Unified</strong> ICM to determine where the call should be transferred. All<br />

queuing in that scenario would have to be done on the <strong>Unified</strong> IP IVR.<br />

Figure 2-19 Traditional IVR Integration Using IVR Double 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 set up as a farm of IVR platforms that have direct PSTN connections for<br />

inbound calls. The IVR has a PG connection to the <strong>Unified</strong> ICM, which tracks all calls in the system.<br />

When a caller opts out of the IVR treatment, the IVR sends a post-route request to the <strong>Unified</strong> ICM,<br />

which returns a label that will either direct the call to an agent or queue the call locally on the TDM IVR<br />

using the Service Control Interface (SCI). The transfer to the agent is done by the TDM IVR selecting a<br />

second port to hairpin the call to the voice gateway and to the <strong>Unified</strong> CCE agent. This takes up two ports<br />

for the time the call is at the agent.<br />

IP<br />

IP<br />

76615<br />

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

2-45

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

Saved successfully!

Ooh no, something went wrong!