Unified CVP deployments are logically divided so that call paths only traverse
subsets of CVP servers. These logical groupings of servers are referred to as
a CVP unit. A CVP unit is comprises VXML Servers, Call Servers,
and Reporting Servers. These servers can be involved in processing of a call. A Unified CVP deployment includes
failover machines, other CVP units that a VXML gateway could transfer
the call to, and VXML Servers that house VXML applications that are called by
Unified CVP deployments that have multiple CVP units
can upgrade one unit at a time. This deployment may be useful for call
centers using H.323 protocol and need to migrate to SIP protocol to continue call processing and
minimize the risks. The CVP unit must remain offline until you upgrade all the components in a unit.
An example of a Unified CVP deployment
(VXML Servers, Call Servers, Reporting Servers, and call paths) is
Figure 1. Example: Unified CVP Deployment Showing Two CVP Units
The figure depicts two logical CVP units. They are logical
units because there is no path for the call to move from one unit to the other.
The VXML Server and Call Server are referred as VS and CS respectively.
CVP unit 1 - VS1, VS2, CS1, CS2, RS1
CVP unit 2 - VS3, VS4, CS3, CS4,
Multiphased approach refers to the ability to
upgrade a subset of Unified CVP servers and resume call processing. Using the
multiphased upgrade approach, you can divide your
upgrades in phases over time. If a CVP deployment has multiple CVP units, you can upgrade each unit using the multiphased approach.
upgrades must upgrade all components in the following order:
Operations Console (OAMP)
Figure 2. CVP Servers and Call Paths
It is not necessary to upgrade all servers in a category in a single maintenance window. However, you must upgrade
all CVP components of one type before moving to the next set of components in
the Unified CVP deployment or the CVP unit.