Showing 6 results.
Items per Page 50
of 1

CVP Forum

« Back to General Discussion - All Versions

CVP 4.x- Ops Console- VXML/Call Servers 'Not Reachable'

Combination View Flat View Tree View
Threads [ Previous | Next ]
CVP 4.0.2/ICM 7.2.5/A&B Side VXML and Call Servers (2 each/side)

I can access the VXML and Call Servers, log in, services are running. The B side VXML and Call Servers are showing "Not Reachable" in the Status column of the Ops Console. Ops Console lives on the A side. There was a 2nd Ops Console on the B side and the same behavior existed there. The B side OC was shut down and items were added to the A side OC. The reimage.bat file located under C:\Cisco\CVP\bin\TAC was run on each of the boxes that were configured on the other disabled Ops Console.

Pings are good, DNS entries are good, hosts/lmhosts files are good.

Looking for answers. Have 2 tac cases open on this.

Is it possible Ops Console required/specific ports are being blocked?

Hi,

The discussion about A and B sides worry me a bit. CVP does not support redundant Ops Console (aka OAMP). I would absolutely expect odd behavior by configuring a set of CVP devices with one Ops Console sometimes and another some other time. As far as I know, the A/B side business is an ICM concept only. Before going down the network analysis path, I would first reconfigure using a single Ops Console.

BTW, CVP and ICM can co-exist on the same box in some limited fashion. There is what is known as the PG combo box, where the CVP Call Server and the ICM PG reside on the same device. But this is not valid for the CVP Ops Console due to the uniqueness requirement described above.

regards,
JP

I would second to what JP also mentioned, the Operations Console is like the dashboard from which an entire Unified CVP deployment can be managed.

The Operations Console Server is not a redundant component. So the Operations Console Server cannot be and should not be duplicated within a deployment.