Cisco Cisco Unified Customer Voice Portal 11.0(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) 

 

 

 

 

 

62

found in the 

logs

 directory of the VoiceXML Server. Call log files are rotated daily. The file is 

organized in a comma-delimited format with 6 columns:

   

. This is a non-repeating value generated by the VoiceXML 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 VoiceXML 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 VoiceXML Server. 
Each part is delimited by dots and contains no spaces. For example: 
192.168.1.100.1024931901079.1. 

   

. 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. 

   

. This integer represents the total number of callers interacting with the system at the 

time the call was received (including the current call). 

   

. 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. 

   

. The name of the application visited. 

   

. A timestamp of the application visit in the format “MM/DD/YYYY HH:MM:SS” 

where the hour is in 24-hour time. This represents when the call was received or the 
application transfer occurred. 

There are a few isolated cases where an error occurs outside the realm of a particular application. 
There may also be an application-level error that encountered trouble logging the error and 
requires a backup location so that the information is not lost. In order to handle these situations, 
the Call Error Log is used. The error log file names are in the form “error_logYYYY-MM-
DD.txt” where YYYY, MM, and DD are the year, month, and day when the error log was first 
created and can be found in the 

logs

 directory of the VoiceXML Server. Call error log files are 

rotated daily. Note that if no error occurred on a particular day, no call error log will be created. 
The file is organized in a comma-delimited format with 2 columns:

 

   

. The time the error occurred. 

   

. The error description. One possible value can be max_ports, indicating the caller 

was put on hold because all the Unified CVP license ports were taken. While the call was 
eventually handled correctly, this is placed here as a notice that the license may not have 
enough Unified CVP ports to satisfy caller demand. Another value is bad_url:[URL], 
indicating that a request was made to the VoiceXML Server for a URL that could not be