Cisco Cisco Customer Voice Portal 8.0(1) User Guide
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
VXML Server session ID (for example,
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.
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
VXML Server session ID (for example,
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 VXML Server.
when the response was sent back by VXML 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.
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.
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.
Correlating Unified CVP Call Server Logs with the VXML Server Logs
Starting in Release 8.0(1), VXML Server (by default) receives callid (which contains the call
GUID), _dnis, and _ani as session variables in comprehensive mode even if the variables are
not explicitly configured as parameters in the ToExtVXML array. If the variables are configured
in ToExtVXML then those values are used. These variables are available to VXML applications
as session variables and they are displayed in the VXML server log.
GUID), _dnis, and _ani as session variables in comprehensive mode even if the variables are
not explicitly configured as parameters in the ToExtVXML array. If the variables are configured
in ToExtVXML then those values are used. These variables are available to VXML applications
as session variables and they are displayed in the VXML server log.
User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)
121
Chapter 5: VXML Server Logging
Correlating Unified CVP Call Server Logs with the VXML Server Logs