Cisco Cisco Unified Customer Voice Portal 10.0(1)
A-7
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Appendix A Troubleshooting
Voice Browser
Voice Browser
describes how to resolve problems you might encounter with the Voice Browser interface.
App Server doesn’t stop
when the machine restarts.
when the machine restarts.
Possible Cause
If the App Server and DC Directory Services start types are set to
automatic, after installing ISN, when the machine restarts, the DC
Directory is in a starting state, and the App Server can’t be stopped.
automatic, after installing ISN, when the machine restarts, the DC
Directory is in a starting state, and the App Server can’t be stopped.
Possible Solution
Change the DC Directory and App Server start type from “automatic” to
“manual”.
“manual”.
Note
You must remember to manually start the services each time you
restart the machine. Start the DC Directory first.
restart the machine. Start the DC Directory first.
Table A-2
Application Server Troubleshooting (continued)
Symptom
Possible Cause and Solution
Table A-3
Voice Browser Troubleshooting
Symptom
Possible Cause and Solution
Windows 2000 Application
Log fills up. Clearing the log
only remedies this
temporarily.
Log fills up. Clearing the log
only remedies this
temporarily.
Possible Cause:
Event log settings are not set to roll over.
Possible Solution:
Change the Event setting so that the Application Log rolls over by doing
the following:
the following:
1.
Select Start > Programs > Administrative Tools > Event Viewer.
2.
Right-click Application Log and select Properties from the menu.
3.
Select the Overwrite events as needed option.
4.
Click Apply and OK.
Possible Cause:
Some unnecessary protocols might have been installed. For example,
NetBEUI has been known to fill the event log.
NetBEUI has been known to fill the event log.
Possible Solution:
Uninstall protocols that are not required by this application.
The Voice Browser does not
appear to be running and no
Voice Browser console
window is present. Attempts
to run VBAdmin generate a
“Failure to Connect” error
message, followed by
termination of VBAdmin.
appear to be running and no
Voice Browser console
window is present. Attempts
to run VBAdmin generate a
“Failure to Connect” error
message, followed by
termination of VBAdmin.
Possible Cause:
The Voice Browser service has started, meaning the Node Manager is
running, however, the Voice Browser program itself is not running. The
Voice Browser might not be able to start because of a bad registry
setting.
running, however, the Voice Browser program itself is not running. The
Voice Browser might not be able to start because of a bad registry
setting.
Possible Solution:
Check the latest Voice Browser EMS logs for problems with a registry
entry.
entry.
The “Voice Browser to
Application Server
Connection Unsuccessful”
alarm is generated twice for a
given Application Server.
One alarm references the
Application Server by
hostname; the other
references the IP Address.
Application Server
Connection Unsuccessful”
alarm is generated twice for a
given Application Server.
One alarm references the
Application Server by
hostname; the other
references the IP Address.
Possible Cause:
Depending on the configuration, the Voice Browser contacts the
Application Server both by hostname and IP Address.
Application Server both by hostname and IP Address.
Possible Solution:
Each of the alarms will be cleared independently when the Voice
Browser successfully contacts the Application Server.
Browser successfully contacts the Application Server.