Cisco Cisco Customer Voice Portal 8.0(1) Guía Del Usuario

with the name of the logger instance is created and all logs generated by the logger instance are
stored there.

By default, VXML Server utilizes three loggers to create text log files containing VXML
Server-specific information: a log that keeps track of calls made to the system, a log for tracking
VXML Server administration activity, and an log that shows errors that occur on the VXML
Server level (as opposed to the application level). The global error logger requires a configuration
that allows for detailed control over how the logger operates.

The following sections describe these three pre-built global loggers, their configurations (if
any), and the information stored in their logs.

The Global Call Logger

The global call logger records a single line for every application visit handled by VXML Server
into a text call log. Most calls will begin and end in a single application so in that case a line in
the call log is equivalent to a physical phone call. For situations where one application performs
an application transfer to another 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 call log file names are in the format call_logYYYY-MM-DD.txt where YYYY, MM, and
DD are the year, month, and day when the call log was first created. By default, the log folder
for is named GlobalCallLogger (though the name is set in the 

 file and

can be changed by the administrator). Call log files are rotated daily. The file is organized in a
comma-delimited format with 6 columns:

•

CallID – This is a non-repeating value generated by VXML 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 VXML Server instance on which the call
originated, SECS is a large integer number representing the time the application visit was
made and INCR is an automatically incremented number managed by VXML Server. Each
part is delimited by dots and contains no spaces. For example:
192.168.1.100.1024931901079.1.

Note: If a voice application uses a Subdialog Invoke element to transfer across multiple
VXML Server instances, the IP address included in the CallID is the IP address of the instance
the call started on. Because of this, it is possible that a CallID in log files on one machine
may contain an IP address for another machine. This allows a physical call to be traced across
multiple servers (from a logging standpoint), even if Subdialog Invoke is used to transfer to
between various voice applications.

•

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.

•

callers – This integer represents the total number of callers interacting with the system at the
time the call was received (including the current call).

User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)