Cisco Cisco Unified Customer Voice Portal 10.5(1) User Guide
C
HAPTER
5:
V
OICE
XML
S
ERVER
L
OGGING
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)
81
The Administration History Logger does not utilize a configuration.
The Application Debug Logger
At times when debugging an application it would be advantageous to see information concerning
the HTTP requests made by the voice browser and the corresponding HTTP responses of Unified
CVP VoiceXML Server. The Debug Logger creates a single file per call that contains all HTTP
requests and responses that occurred within that call session. The log files are named
“debug_logYYYY-MM-DD-HH-SESSIONID.txt” where YYYY is the year, MM is the month,
DD is the day, and HH is the hour (in 24-hour time) that the file is created and SESSIONID is
the Unified CVP VoiceXML Server session ID (e.g. “debug_log2000-01-01-17-
192.168.1.100.1024931901079.1.MyApp.txt”). The session ID is included in the filename to
ensure uniqueness of the files. The debug log contains:
the HTTP requests made by the voice browser and the corresponding HTTP responses of Unified
CVP VoiceXML Server. The Debug Logger creates a single file per call that contains all HTTP
requests and responses that occurred within that call session. The log files are named
“debug_logYYYY-MM-DD-HH-SESSIONID.txt” where YYYY is the year, MM is the month,
DD is the day, and HH is the hour (in 24-hour time) that the file is created and SESSIONID is
the Unified CVP VoiceXML Server session ID (e.g. “debug_log2000-01-01-17-
192.168.1.100.1024931901079.1.MyApp.txt”). The session ID is included in the filename to
ensure uniqueness of the files. The debug log contains:
A timestamp of when each HTTP request was received from the voice browser as well as
when the response was sent back by Unified CVP VoiceXML Server.
All headers of the HTTP request.
All arguments passed with the HTTP request, whether they be set via GET or POST.
The entire VoiceXML page returned in the HTTP response.
It is recommended to use the Debug Logger only when performing debugging and not in a
production environment as it incurs overhead on the system in creating and managing file IO and
replicating the HTTP response, which must be generated once for the voice browser and once for
each Debug Logger instance. Note the Debug Logger does not require the enforce call event
order to be turned on, however without it there could be situations where under load the HTTP
requests and responses are out of order or mixed together in the file.
production environment as it incurs overhead on the system in creating and managing file IO and
replicating the HTTP response, which must be generated once for the voice browser and once for
each Debug Logger instance. Note the Debug Logger does not require the enforce call event
order to be turned on, however without it there could be situations where under load the HTTP
requests and responses are out of order or mixed together in the file.
The Data Feed Logger
This logger listens for logging events and provides a data feed to the CVP Reporting Server via
the CVP VXML subsystem. The CVP Reporting Server stores this information in a reporting
database so that it is available for later review.
the CVP VXML subsystem. The CVP Reporting Server stores this information in a reporting
database so that it is available for later review.
The data feed includes call summary and application session summary data. Call summary data
includes call identifiers, call start and end timestamps, ANIs, DNISs, etc. Application session
data includes application names, session IDs and various session variables. The data feed also
includes element access histories, activities within elements, element variables and element exit
states. Finally, custom logging data (i.e. specified by voice application designers in the “Add to
log” table of an element) is also part of the data feed.
includes call identifiers, call start and end timestamps, ANIs, DNISs, etc. Application session
data includes application names, session IDs and various session variables. The data feed also
includes element access histories, activities within elements, element variables and element exit
states. Finally, custom logging data (i.e. specified by voice application designers in the “Add to
log” table of an element) is also part of the data feed.
The Data Feed Logger uses a configuration file called CVPDatafeedLoggerConfig.properties, of
which the following is an example:
which the following is an example: