Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide
C
HAPTER
5:
S
ERVER
L
OGGING
C
ISCO
CVP
V
OICE
XML
User Guide
The Call Log
The call log records a single line for every application visit handled by an install of CVP
VoiceXML Server. Most calls will be to a single application so in this case a line in the call log
is equivalent to a physical phone call. For situations where one CVP VoiceXML application
performs and application transfer to another CVP VoiceXML application, a separate line will be
added to the call log for each application visit, despite the fact that they all occur in the same
physical call. Since each application visit is logged separately in each application’s own log file,
the call log provides a way to stitch together a call session that spans multiple applications. The
rotated call log file names begin with “call_log” and can be found in the
VoiceXML Server. Most calls will be to a single application so in this case a line in the call log
is equivalent to a physical phone call. For situations where one CVP VoiceXML application
performs and application transfer to another CVP VoiceXML application, a separate line will be
added to the call log for each application visit, despite the fact that they all occur in the same
physical call. Since each application visit is logged separately in each application’s own log file,
the call log provides a way to stitch together a call session that spans multiple applications. The
rotated call log file names begin with “call_log” and can be found in the
logs
directory of
Server. The columns of the data are:
•
CallID
. This is a non-repeating value generated by the Server to uniquely identify calls. It is
designed to be unique even across machines, as the log files of multiple machines running the
same applications may be combined for analyses. The format of the session ID is
IP.SECS.INCR where IP is the IP address of the machine on which the Server is installed,
SECS is a large integer number representing the time the application visit was made and
INCR is an automatically incremented number managed by the Server. Each part is delimited
by dots and contains no spaces. For example: 192.168.1.100.1024931901079.1.
same applications may be combined for analyses. The format of the session ID is
IP.SECS.INCR where IP is the IP address of the machine on which the Server is installed,
SECS is a large integer number representing the time the application visit was made and
INCR is an automatically incremented number managed by the Server. Each part is delimited
by dots and contains no spaces. For example: 192.168.1.100.1024931901079.1.
•
SessionID
. The session ID is used to track a visit to a specific application. Therefore, with
application transfers, one call ID may be associated with multiple session IDs. For this
reason, session IDs are simply the call ID with the application name appended to the end. For
example: 192.168.1.100.1024931901079.1.MyApp.
reason, session IDs are simply the call ID with the application name appended to the end. For
example: 192.168.1.100.1024931901079.1.MyApp.
•
callers
. This integer represents the total number of callers interacting with the system at the
time the call was received (including the current call).
•
order
. A number indicating the order of each application visited in a call. The order begins at
1. This column exists to report the order in which a caller visited each application should the
data be imported to a database.
data be imported to a database.
•
Application
. The name of the application visited.
•
Time
. A timestamp of the application visit in a readable format. This represents when the call
was received or the application transfer occurred.
The Application Activity Log
The activity log is the main log managed by CVP VoiceXML Server. It contains 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 rotated activity log
names begin with “activity_log” and are stored in the
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 rotated activity log
names begin with “activity_log” and are stored in the
logs
directory of the specific application it
applies to.
©2000 - 2005 Audium Corporation. All Rights Reserved. 1/14/05
65