Cisco Cisco Customer Voice Portal 8.0(1) Developer's Guide
Application-level events are associated only with an application and not a call session.
Currently, the only application-level events are the application administration event
(
Currently, the only application-level events are the application administration event
(
ApplicationAdminEvent
) that reports on administration activity performed on the
application and the application administration error event
(
(
ApplicationAdminErrorEvent
) that reports any errors encountered while performing
administration activities.
–
The events extending
ActivityEvent
are all the events that can occur in a call: a new
call, a call ending, an element being entered, an element exiting, an element storing data,
a flag element being triggered, an element interacting with the caller, a hotevent being
activated, a hotlink being activated, a custom event caused by calling the
a flag element being triggered, an element interacting with the caller, a hotevent being
activated, a hotlink being activated, a custom event caused by calling the
addToLog
method of the Session API or entering data in an element’s configuration pane in Builder
for Call Studio, a warning event, an error event, and an HTTP event signifying a new
HTTP request made to VXML Server.
for Call Studio, a warning event, an error event, and an HTTP event signifying a new
HTTP request made to VXML Server.
–
Error events are defined in a hierarchy to define different types of errors. This allows a
logger developer to act on certain types of errors or to do different tasks based on the error
type.
logger developer to act on certain types of errors or to do different tasks based on the error
type.
–
Currently, when a voice element returns interaction data, VXML Server sends loggers a
DefaultInteractionEvent
, which extends from
ElementInteractionEvent
. This
design will allow for different interaction content in the future without affecting the existing
class hierarchy.
class hierarchy.
•
void doPreLogActivity(ApplicationEvent event)
void doPostLogActivity(ApplicationEvent event)
These two methods can be optionally overridden to perform any activity desired before and
after the
after the
log
method is called. By default these methods are defined in the
ApplicationLoggerBase class to do nothing.
Utility Methods
These utility methods provide important information to the logger.
Common Utility Methods
These methods are defined in the
LoggerBase
class and are therefore applicable to both
application and global loggers.
•
int getLoggerType()
This method returns the type of the logger, and is for future use. Currently, it returns
APPLICATION_LOGGER
or
GLOBAL_LOGGER
.
•
String getLoggerInstanceName()
This method returns the name of the logger instance as defined in either VXML Server’s
configuration or the settings of the application.
configuration or the settings of the application.
Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)
89
Chapter 13: Loggers
Utility Methods