Call Server: Call Server Is Not Reachable

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Call Server Is Not Reachable)
(Call Server Is Not Reachable)
Line 18: Line 18:
</td></tr><tr><td> '''Release''' </td><td>Release 7.0(2)</td></tr><tr><td> '''Associated CDETS #''' </td><td> None. </td></tr></table>
</td></tr><tr><td> '''Release''' </td><td>Release 7.0(2)</td></tr><tr><td> '''Associated CDETS #''' </td><td> None. </td></tr></table>
-
[[Category:Unified CVP, Release 7.0(2)]]
+
[[Category:Unified CVP, Release 7,8,9,10x]]

Revision as of 09:03, 15 January 2015

Call Server Is Not Reachable

Problem Summary After a forced delete of the Reporting Server, the Call Server state did not change from the Down state to the Partial or Up state.
Error Message Opsconsole Control Center: Call Server status is down.
Possible Cause The Call Server messageAdapter.properties file is corrupt.
Recommended Action To resolve this issue:
  1. From the command line, run CVP_HOME\bin\tac\reimage.bat on the Call Server.
  2. Restart the Operations Console Resource Manager (ORM) service.
  3. Log in to the Operations Console, and choose Device Management > CVP Call Server.
  4. Click Save & Deploy to save the changes and apply them to the Call Server.
    Note: All co-located devices—including VXML Server, Reporting Server, and Video Media Server—must be deployed after reimage.bat is run. You must repeat these steps for each co-located device.

Note: Optionally, you can reinstall the CVP device.

Release Release 7.0(2)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools