Avaya VXI log messages

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 the comment character ("#") at the beginning of the line specifying the parameter.

Enabling logging levels

To enable Avaya VXI logging levels:

1. Type vi /vs/data/vxml/default.cfg and press Enter.
2. Using the vi editing commands, remove the comment character (#) from the lines that specify the logging levels you want to enable.
3. Save and close the file.

Note:
Any changes you make to the default.cfg file are not effective until the Avaya VXI process has been restarted. The easiest way to restart the Avaya VXI process is to stop the voice system (using the stop_vs command) and start it again (using the start_vs command). For more information on how to use these commands, see start_vs (command) and stop_vs (command).

Viewing log messages

Log messages are written to the /voice1/vxml/log.txt file or the file specified by the client.log.filename parameter in the default.cfg file.

Using the log tag

You can use the log tag in VoiceXML documents to generate logging or debug messages that may be helpful in troubleshooting problems with applications. Logging can also be used to monitor events and take action in applications using asynchronous event nodes.

For example, the command:

<log>Error: <value expr='_event'/>, <value expr='_message'/></log>

could be used to generate errors based on evaluating the _event and _message variables in an application.

Complete information on the log tag is in the VoiceXML 2.0 draft specification at the W3C Web site.

Messages generated by using the <log> tag are written to the same log file used by Avaya IR. The are viewable using the Message Log Report screen under the Reports Administration menu. All log tag messages are written at as AVB013 messages in the Message Log Report.

� 2002 Avaya Inc. All Rights Reserved.