Cisco Cisco Unified Customer Voice Portal 11.0(1)

Call Server on VRU PG

Standalone with ICM Lookup and no
Reporting

•

VRU PIM connects to Localhost

•

VoiceXML Server connects to VRU
PG

Call Server on VRU PG

Standalone with ICM Lookup and
Reporting—reporting data flow is not
large

•

VRU PIM connects to Localhost

•

VoiceXML Server connects to VRU
PG

•

Reporting Server connects to VRU
PG

Call Server on dedicated machine

Standalone with ICM Lookup and
Reporting—reporting data flow is large

•

VRU PIM connects to dedicated Call
Server

•

VoiceXML Server connects to
dedicated Call Server

•

Reporting Server connects to
dedicated Call Server

Call Server on Reporting Server
machine

Standalone with Reporting and no ICM
Lookup

•

VoiceXML Server connects to
Reporting Server

Note: As the table above indicates in the first row, if Standalone is not using the Request ICM
Label capability, a Call Server is not required from the Standalone perspective. However, since
the Reporting Server is connected to the Call Server, you must install a Call Server—even if its
Services are inactive—in order to be able to use reporting.

Geographic Models

This section presents the options available in terms of the geographic distribution required. That
is, we present choices according to where components are physically positioned, and what kind
of network connection links them together.

In discussing geographic distribution, we consider the location of call centers (where agents are
positioned), of data centers (where Unified CallManagers and Unified ICME and Unified CVP
solution components are located), and of ingress points (where Ingress Gateways are located).
However, generally speaking, the locations of the call centers are not relevant to Unified CVP,
except in terms of network provisioning, which is beyond the scope of this discussion.

Planning Guide for Cisco Unified Customer Voice Portal 4.0(1)