PDF(598.7 KB) View with Adobe Reader on a variety of devices
ePub(544.1 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(681.1 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 12, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes an issue found when a Cisco Customer Voice Portal (CVP) Call Server is added via CVP Cisco Operations Console (OAMP) and also provides a feasible solution to it.
Cisco recommends that you have knowledge of these topics:
CVP Call Server
The information in this document is based on CVP version 10.0.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Error is Reported when CVP Call Server is Added to CVP OAMP
When CVP Call Server is added to the CVP OAMP, an error is reported. This error is seen when you click on Save and Deploy.
Step 1. In order to add the CVP Call Server into CVP OAMP, sign in to CVP OAMP and navigate to Device Management > Unified CVP Call Server as shown in this image.
Step 2. Click Save and Deploy. You get an error which indicates that the CVP Call Server cannot be created because it already exist in another CVP Operations Console (OPSConsole) as seen in this image.
The target CVP Call Server has an OAMP id in its configuration and hence it will not let the second OAMP deploy it as seen in this image.
Step 3. Open the file C:\Cisco\CVP\conf\orm.properties. You can verify the OAMP Id as shown in this image.
Step 1. Stop the Cisco CVP Resource Manager Service in the CVP Call Server.
Step 2. Comment out the orm.oamp.id line in C:\Cisco\CVP\conf\orm.properties as shown in this image.
Step 3. Start the Cisco CVP Resource Manager Service in the CVP Call Server.
Step 4. Click Save and Deploy as shown in this image.