Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide
C
HAPTER
5:
VXML Server
L
OGGING
U
SER
G
UIDE FOR
C
ISCO
U
NIFIED
CVP
VXML
S
ERVER
AND
C
ISCO
U
NIFIED
C
ALL
S
TUDIO
100
creating and debugging a new application. The activity logger and error logger require
configurations that allow for detailed control over how the loggers operate.
configurations that allow for detailed control over how the loggers operate.
The following sections describe these four pre-built application loggers, their configurations (if
any), and the information stored in their logs.
any), and the information stored in their logs.
The Application Activity Logger
The Activity Logger is the main application logger included with VXML Server. It records into
text log files all the activity taken by callers when they visit an application. It stores information
about the call itself such as its ANI, what elements the caller encountered and in what order, and
even detailed actions such as the values entered by the caller or the confidences of their
utterances. The names of the log files created by the Activity Logger begin with “activity_log”
and are delimited for easy importing into spreadsheets and databases. These logs have a fixed
number of columns:
text log files all the activity taken by callers when they visit an application. It stores information
about the call itself such as its ANI, what elements the caller encountered and in what order, and
even detailed actions such as the values entered by the caller or the confidences of their
utterances. The names of the log files created by the Activity Logger begin with “activity_log”
and are delimited for easy importing into spreadsheets and databases. These logs have a fixed
number of columns:
•
SessionID
. The session ID of the application visit as described in the VXML Server Call Log
section.
•
Time
. A timestamp of the event in a readable format.
•
[Element name]
. The name of the current element the activity belongs to. Only functional
elements (voice elements, action elements, decision elements, and insert elements) can
appear here. This column would be empty if the activity does not apply to an element.
appear here. This column would be empty if the activity does not apply to an element.
•
Category
. The category of the action. A list of categories is given below:
o
start
. Information on new visits to the application.
o
end
. Information on how the application visit ended.
o
element
. Information on the element visited and how the element was exited. The element
column is empty for the
start
and
end
categories.
o
interaction
. Detailed information about what a caller did within a voice element.
o
data
. Element data to be logged.
o
custom
. Custom developer-specified data to log.
•
Action
. A keyword indicating the action taken. A list of actions is given in Table 5-1.
•
Description
. Some qualifier or description of the action.
The following table lists all possible category and actions that can appear in the activity log and
descriptions on what they represent.
descriptions on what they represent.