Cisco Cisco Customer Voice Portal 8.0(1) User Guide

Page of 107
C
HAPTER 
3:
 
A
DMINISTRATION
 
 
V
OICE
XML
 
S
ERVER 
U
SER 
G
UIDE 
 
 
 
FOR 
C
ISCO 
U
NIFIED 
C
USTOMER 
V
OICE 
P
ORTAL 
R
ELEASE 
4.0(1) 
 
 
 
 
 
43
Chapter 3:
 Administration 
Setting up and maintaining Unified CVP VoiceXML Server is designed to be simple, quick, and 
painless. Minimizing downtime is the goal and this chapter explains the processes used to setup 
and maintain the system to achieve that goal. This chapter details administration activities 
possible on Unified CVP VoiceXML Server that are useful to developers as well as 
administrators.  Additionally, refer to the Configuration and Administration Guide for Cisco 
Unified Customer Voice Portal
 for detailed information about how to configure and administer 
Unified CVP VoiceXML Server using the Operations Console. 
 
From the VoiceXML Server Configuration tab of the Operations Console, you can enable 
reporting of VoiceXML Server script and call activities to the Reporting Server. When enabled, 
the VoiceXML Server reports on call and application session summary data. Call summary data 
includes call identifier, start and end timestamp of calls, ANI, and DNIS. Application session 
data includes application names, session ID, and session variables. You can also create report 
filters that define which data are included and excluded from being reported. 
 
Note that in order for voice-application-level reporting information to be available to the 
Reporting Server, each application that is expected to report this data should have a Data Feed 
logger configured. Similarly, for SNMP information to be available to the SNMP server, ensure 
that each application has a SNMP logger configured. See Chapter 5 for information about these 
loggers and their configurations. 
Running VoiceXML Server 
The VoiceXML Server starts up automatically when the Java application server is started or the 
application server starts the VoiceXML Server web application archive. Assuming the 
AUDIUM_HOME environment variable is set and the license files are valid, the VoiceXML 
Server will first display all of the Gateway Adapters installed, followed by loading all the voice 
applications deployed on it. As each application is loaded, the VoiceXML Server will report it in 
the application server console window (which will not be seen if the application server was 
started in the background or a service, or when using some application servers that pipe this 
content to a log file). If any application encounters problems with its XML files, missing Java 
classes, problems with its loggers, or issues encountered with the start of application classes, a 
brief message will be displayed in the console window and the full description is sent to an error 
logger. The loading of just that particular voice application will be aborted and other correctly 
configured applications will load normally. Once all applications are loaded, the VoiceXML 
Server is ready to start handling calls. 
Shutting down the application server will stop all calls on the system at the time. Shutting down 
the application server will also prompt each application to be unloaded – end of application 
classes will be run and loggers will be destroyed. If the voice browser requests a document while 
the application server is down, it will be unable to reach Unified CVP VoiceXML Server, 
prompting the voice browser to play an error message to the caller. It is important, especially for 
production systems, to prevent accidental or intentional shutdowns of the application server.