Call Server Troubleshooting

From DocWiki

Revision as of 16:24, 12 September 2012 by Dosproul (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Problem Summary

The earlier section Common Audio Responses, Error Messages, and Issues with Solutions contains error indications that include problems with the call server. The following information supplements that section.

Error Message


Possible Cause


Recommended Action

Call server status is partial:

  • An immediate busy signal usually indicates an issue with the gateway or a call server that is down.
  • This is normal status for the standalone applications because the call server is not connected to ICM.
  • In the comprehensive exercise, a status of partial usually indicates a problem with the configuration of the PG connecting CVP to ICM. Refer to Troubleshooting the PG Installed on the Unified CVP Server.

Note: You do not need a license file for the test implementation of the call server. However, the test implementation is limited to thirty simultaneous calls. This means that, if, for some reason, calls are not being completed and are "stuck" in the system, additional calls (over 30) will not go through and will be logged as errors.



Associated CDETS #


Back: Troubleshooting Tips for Getting Started with CVP

Rating: 0.0/5 (0 votes cast)

Personal tools