Cisco Cisco Unified Customer Voice Portal 10.5(1)

–

Choose a Physical model.

•

Work out the network topology for your system, including addresses and names of the solution
components.

•

Determine a failover strategy for all the components of your Unified CVP solution.

•

In non-SIP environments, determine your strategy for inbound call routing (that is, dial peers
versus Gatekeeper).

•

Decide on a naming resolution system for Gateways (DNS versus configured on the Gateway).

•

If using a VRU other than Unified CVP, determine the VRU trunk group number and number
of trunks.

•

If ASR and/or TTS are part of your solution, determine the locale values to be used.

•

Decide whether the same set of VRUs are to be used for all cases, or whether that will be
determined separately for each customer (dialed number).

Note: If all dialed numbers will use the same VRUs, it is easiest to use a default Network
VRU, rather than to configure multiple Network VRUs. For more information, see the
“Common Configuration for Differentiating VRUs (Customer Voice Portals) Based on Dialed
Number” section in the Configuration and Administration Guide for Cisco Unified Customer
Voice Portal.

•

Plan how you will be routing calls through the network to the VRU.

–

For Comprehensive deployment models and for deployment models with a NIC (Network
Interface Controller):

Determine the Network Routing Number. This number is the base for routing calls
through the network to the VRU; a correlation ID is appended to this number to transfer
calls to a Network VRU through the network. The Network Routing Number should be
at least as long as the longest dialed number on which Unified CVP will receive incoming
calls.

–

For deployments with a Customer VRU and in Unified ICMH/CICM environments and
for NIC Type 2 or 8 deployments:

Determine the translation route pools to use for each VRU. Determine the labels to be
sent to the network to connect the call to the VRU and the corresponding DNIS (Dialed
Number Identification Service) that will be seen by the VRU. For example, the label for
the network might be 18008889999 and the DNIS received by the VRU and sent back to
the ICM to identify the call might be 9999. The pool must contain as many independent
DNISs as the number of new call arrivals that might occur during the longest time it takes
to get any to the VRU, that is, the time to execute a Translation Route to VRU node. This
time needs to include the network delays and the possibility that alternate endpoints are
used in the VoIP network. In practice, make sure the number is significantly larger than
this to ensure there are always enough. For example, if the time to get to the VRU is 3

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