This document describes how to troubleshoot connectivity issues between Cisco Voice Portal (CVP) Operation Console (OAMP) server with CVP call server.
Here is the list of common connectivity issues between these two servers:
1. What does it happen when Save and Deploy button pressed in CVP OAMP page?
2. What components do we need to verify if OAMP server can't reach CVP call server?
3. Which files are changed in re-image process?
Contributed by Mingze Yan, Cisco TAC Engineer.
Edited by Sahar Modares, Cisco TAC Engineer.
Cisco recommends that you have knowledge of these topics:
CVP Call Server 11.5
CVP OAMP 11.5
What does it happen when Save and Deploy button pressed in CVP OAMP page?
In order to understand the what happens when Save and Deploy button is pressed, you need to see what is shown when new call server was installed. After CVP Call Server is installed, there is no CVP subsystem defined and OAMP server does not allocate any message bus.
In order to verify the configuration, navigate to \Cisco\CVP\conf\system.properties file. The file does not include subsystem information.
From CVP logs, this is what it shows when there is no subsystem defined:
16: 10.66.75.101: Jul 07 2017 09:28:27.726 +1000: %CVP_11_5_Infrastructure-0-START: No Subsystems have been started. Have you configured your server yet? ; Make sure <CVP_HOME>\conf\propFileList.properties is loading "system" and that <CVP_HOME>\conf\system.properties lists at least one subsystem to load. [id:1033]
When CVP Call server is configured in OAMP GUI page, these changes happen:
1. The OAMP server pushes message bus information to CVP call server, also adds subsystem and plug-in.
2. These files are modified after the changes were applied:
3. From system.properties file, message bus is allocated by OAMP server, which is globally significant. Each CVP call server uses different message bus to communicate with OAMP:
CSCve32007 -Firewall in between Operations Console Server and CVP Components
In order to find rmi random number, use these steps:
Step1. Use 2099 to find PID number.
Step 2. Use the PID number to find out all the ports which are used.
Note: The connection between OAMP and call server is bi-directional. Same command can be used for local ports on OAMP servers.
Which files are changed in re-image process?
After reimage process, four files are changed:
Here are the changes for these four files:
In messageAdapter.properies, plugins that was added in previous section are deleted
In orm.propeties, orm.controller.adapterName = CVPCTL3 is removed
In orm.xml, all subsystem added in previous section are deleted
In system.propeties, the subsystem was added in previous section is deleted
If you click save and deployment from OAMP page, CVP call server isn't updated, as OAMP still in use with the message bus ID communicate with Call Server, but call server has no such message bus information.
After CVP call server deletion from OAMP, three files are changed:
messageAdaptor file is empty
Orm adds this line orm.controller.adapterName =
System file adds this line MessagingLayer.adapterName =
When you re-add the CVP call server in OAMP, then the configuration is updated in the CVP call server.
The updated files are almost the same as first time deployment, except for the file orm_jmx.