Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
2:
V
OICE
XML
S
ERVER
C
OMPONENTS IN
D
ETAIL
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)
23
Every application deployed on Unified CVP VoiceXML Server has the ability to define any
number of start and end of application actions that are executed in the order in which they appear
in the application settings.
number of start and end of application actions that are executed in the order in which they appear
in the application settings.
Loggers
The act of logging information about callers to the system is performed by loggers. An
application can reference any number of loggers that “listen” for logging events that occur.
These events range from events triggered by a call, such as a caller entering an element or
activating a hotlink to administration events such as an application being updated to errors that
may have been encountered. Loggers can take the information on these events and do whatever
desired with them. Typically the logger will store that information somewhere such as a log file,
database or reporting system.
application can reference any number of loggers that “listen” for logging events that occur.
These events range from events triggered by a call, such as a caller entering an element or
activating a hotlink to administration events such as an application being updated to errors that
may have been encountered. Loggers can take the information on these events and do whatever
desired with them. Typically the logger will store that information somewhere such as a log file,
database or reporting system.
Unified CVP VoiceXML Server includes default loggers that store the information obtained
from logging events to parse-able text log files, SNMP systems, and logging databases. A need
may exist, however, for a logger with functionality not available in the default installation or a
logger that takes the same data and stores it using a different mechanism.
from logging events to parse-able text log files, SNMP systems, and logging databases. A need
may exist, however, for a logger with functionality not available in the default installation or a
logger that takes the same data and stores it using a different mechanism.
To satisfy these concerns, a developer can construct custom loggers that listen for logger events
and report them in their own way. The developer can design the logger to use a configuration to
customize how the logger functions, depending on how flexible it needs to be. Due to the level
of integration with the Unified CVP software required, only the Java API provides the means for
building loggers.
and report them in their own way. The developer can design the logger to use a configuration to
customize how the logger functions, depending on how flexible it needs to be. Due to the level
of integration with the Unified CVP software required, only the Java API provides the means for
building loggers.
Refer to Chapter 5: VoiceXML Server Logging in the section entitled Application Logging for
descriptions of the loggers included with Unified CVP VoiceXML Server. Refer to the
Programming Guide for Cisco Unified Customer Voice Portal for a description of the process of
building custom loggers.
descriptions of the loggers included with Unified CVP VoiceXML Server. Refer to the
Programming Guide for Cisco Unified Customer Voice Portal for a description of the process of
building custom loggers.
On Error Notification
When errors occur on the Unified CVP VoiceXML Server, the application-specific error voice
element will handle how to handle the caller. If specified, the on error notification Java class can
be configured to be activated when an error occurs. The class is given information about the
application and some basic call information to allow the developer to specify the action
accordingly. The developer can write this class to perform whatever they wish.
element will handle how to handle the caller. If specified, the on error notification Java class can
be configured to be activated when an error occurs. The class is given information about the
application and some basic call information to allow the developer to specify the action
accordingly. The developer can write this class to perform whatever they wish.
The most common purpose for the on error notification class is to perform some custom
notification, something to indicate at runtime that an error occurred. This could involve paging
an administrator or integrating with a third-party trouble ticket and notification process. Since the
notification usually involves an administrator whose responsibility is the entire Unified CVP
VoiceXML Server, the Java class, once specified, will apply to any error that prematurely ends a
call on any Unified CVP application.
notification, something to indicate at runtime that an error occurred. This could involve paging
an administrator or integrating with a third-party trouble ticket and notification process. Since the
notification usually involves an administrator whose responsibility is the entire Unified CVP
VoiceXML Server, the Java class, once specified, will apply to any error that prematurely ends a
call on any Unified CVP application.