Cisco Cisco Unified Customer Voice Portal 11.0(1) Installation Guide

Page of 96
Split Call Flow among Multiple Unified CVP Call Control Servers
In all releases prior to 4.0, Comprehensive Model calls could have their two call legs processed
in different Call Control Servers. The Switch leg might go through one server, while the
VRU leg might find itself in another. Even if the “combo boxes” configuration was used (VB
and AS in the same machine), it was possible for a call to use one machine’s VB and another
machine’s AS, even for the same call leg. In CVP 4.x this situation does not typically occur.
When a call enters one Call Server, all pieces of that call use the same Call Server. No
remnants of the call are found on another Call Server. If you are upgrading to Unified CVP
7.0 and staying with H.323, it is likely that you will need to make configuration changes to
ensure that calls entering the Voice Browser on one Call Server are delivered only to the IVR
Subsystem on the same Call Server, on both the Switch and the VRU call legs. Depending
on the configuration you started with, this may involve changing setAppServerList (in
VBAdmin) to localhost only, removing any other application servers in the list.
License Enforcement
CVP Release 3.1 and earlier versions did not enforce licenses. In Unified CVP Release 4.x
and later, licensing is more stringently enforced. For example, a Unified CVP Call Server
license is required for all CVP Call Server machines on which Call Server services are
required. CVP 7.0 Call Server provisions a two port evaluation license for all CVP Call
Server installations that have no license file. The evaluation license does not expire; however,
it limits the number of calls you can place simultaneously to two. It is recommended that
you review 
 for
information about Unified CVP Server licenses. The Configuration and Administration Guide
for Cisco Unified Customer Voice Portal 
 contains detailed information about Unified CVP
licensing.
Special Considerations for CVP 3.1 Migrations
This section provides advice for users migrating from CVP 3.1, in terms of how their migration
process differs from the upgrade steps listed in the 
 section. The notes in this section do not apply to users
upgrading from Unified CVP 4.x.
Prior to upgrading, use CVP Studio 3.1 to confirm whether there are any CVP 3.1 voice
applications using Subdialog Start elements with values specified on the General, Audio, or
Data tabs of each respective Element Configuration view.
Typically, values are set on the Data tab; the Audio tab does not usually contain values since
this element does not play audio.
Note: The Subdialog Start element in Unified CVP Release 4.x and higher does not include
the General, Data, or Audio tabs. If Subdialog Start elements were configured with values
on any of these tabs, you need to copy the value settings to a temporary location such as a
text file. Once your migration is complete, you can reapply the settings to any subsequent
Action, Decision, or Voice element in the call flow as is appropriate per desired functionality.
For example, if a Digits element depends on data previously defined via a Subdialog Start
Installation and Upgrade Guide for Cisco Unified Customer Voice Portal Release 7.0(2)
69
Chapter 10: Upgrading to Unified CVP 7.0
Upgrade Changes Affecting Unified CVP Release 3.1 SR2 Deployments