Cisco Cisco Unified Customer Voice Portal 10.5(1)

 describes how to resolve problems you might encounter with the Voice Browser interface.

Windows 2000 Application 
Log fills up. Clearing the log 
only remedies this 
temporarily.

Event log settings are not set to roll over.

Change the Event setting so that the Application Log rolls over by doing 
the following:

Select Start > Programs > Administrative Tools > Event Viewer.

Right-click Application Log and select Properties from the menu.

Select the Overwrite events as needed option.

Click Apply and OK.

Some unnecessary protocols might have been installed. For example, 
NetBEUI has been known to fill the event log.

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.

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.

Check the latest Voice Browser EMS logs for problems with a registry 
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.

Depending on the configuration, the Voice Browser contacts the 
Application Server both by hostname and IP Address. 

Each of the alarms will be cleared independently when the Voice 
Browser successfully contacts the Application Server.