VoiceXML logging
Various levels of logging messages from the Avaya VXI process can be enabled (and disabled) in the default.cfg file. Logging levels are specified in the file by the parameter: client.log.diagTag.number, where number specifies the type of log messages to generate. There are several logging levels specified in default.cfg. The following logging levels are particularly useful for debugging and troubleshooting purposes:
- client.log.diagTag.3000 shows inet messages.
- client.log.diagTag.4000 shows ECMAscript messages.
- client.log.diagTag.5000 shows activity associated with spoken words (using text-to-speech), prompts, announcements, and other audio playback.
- client.log.diagTag.6000 shows activity associated with grammar loading, activation, and deactivation. Also provides best and value results, which show what was trying to be matched in the grammar (best) and what the end result was (value).
- client.log.diagTag.8000 shows errors associated with Avaya VXI activities, such as unsupported mime type.
- client.log.diagTag.8001 shows standard pre-defined VoiceXML errors thrown by the Avaya VXI process, such as error.badfetch.
- client.log.diagTag.8002 shows variable settings, fetch information, fetch errors, and parsing errors. This logging level is useful for tracing through application logic and finding any errors in the application syntax.
- client.log.diagTag.9000 shows object tag messages.
By default, all of the logging parameters are disabled. A disabled logging parameter is indicated by either or both of the following:
- The comment character ("#") at the beginning of the line specifying the parameter
- A tag value of zero ("0")
Following are examples of a disabled logging parameter:
client.log.diagTag.3000 VXIInteger 0
# client.log.diagTag.3000 VXIInteger 1
# client.log.diagTag.3000 VXIInteger 0
