Cisco Cisco Unified Customer Voice Portal 10.0(1)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
A-21
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Appendix A Troubleshooting
Call Manager
Call Manager
describes how to resolve problems you might encounter with the Call Manager/ISN inter-
face.
Table A-8
Call Manager Troubleshooting
Symptom
Possible Cause and Solution
.asp errors occur on the Call
Manager and the Call
Manager does not function
normally.
Manager and the Call
Manager does not function
normally.
Possible Cause:
If you installed an Application Server on the same machine as the Call
Manager, and then you uninstalled the Application Server, some files
the Call Manager needs might have been deleted.
Manager, and then you uninstalled the Application Server, some files
the Call Manager needs might have been deleted.
Possible Solution:
Reinstall Call Manager.
Problem with IP Transfer.
Possible Cause:
Cisco Call Manager in not registered with the Gatekeeper because the
Gatekeeper information in Call Manager is incorrect.
Gatekeeper information in Call Manager is incorrect.
Possible Solution:
Change the Gatekeeper host name used during configuration to an IP
address.
address.
Possible Cause:
Cisco Call Manager in not registered with Gatekeeper because the Reset
and Restart buttons was not clicked after the Gatekeeper information
was updated.
and Restart buttons was not clicked after the Gatekeeper information
was updated.
Possible Solution:
Do the following:
1.
In ccmadmin, select Device > Gatekeeper.
2.
Add the Gatekeeper Device Information and select gateway as the
Terminal Type.
Terminal Type.
3.
Click Update, then Reset Gatekeeper.
4.
Finally click, Reset to apply the changes.
Possible Cause:
Cisco Call Manager in not registered with Gatekeeper because a
Gatekeeper registration port is not explicitly configured in Gatekeeper.
Gatekeeper registration port is not explicitly configured in Gatekeeper.
Possible Solution:
Do the following:
1.
Check the Gatekeeper configuration to verify that port 1719 is
explicitly defined for the local Gatekeeper zone. For example:
zone local gk1 cisco.com 10.86.137.146 1719.
explicitly defined for the local Gatekeeper zone. For example:
zone local gk1 cisco.com 10.86.137.146 1719.
2.
Verify the Call Manager registration in Gatekeeper by entering the
show gatekeeper endpoints command in the Gatekeeper CLI.
show gatekeeper endpoints command in the Gatekeeper CLI.