The Developer Log

You can choose to have WTE generate an additional log, called the developer log, which provides details about WTE events beyond those available from the WTE logging file. For example, the developer log tracks every event connected with the WTEActiveConnection debugging object. Other activities recorded in this log include:

• Calls answered by WTE.
• Any tag parsed by WTE.
• Audio-items gathered by WTE.
• Menus rendered.
• DTMFs detected and used.
• Any session variables that were edited and saved.

Each line in the developer log file has its session name as a prefix. Each session name is guaranteed to be unique on a particular server. Although events relating to two or more concurrent sessions may be interleaved in the log, you can identify the call associated with any event.

To enable developer logging on your WTE server, edit the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
mswtesrv\Parameters\DevLogFile

Set the string value for this entry to the path and file name for the developer log (for example, "D:\WTElogs\SalesServer.log"). When WTE starts running, it checks for the DevLogFile registry key and, if it exists, automatically creates the specified developer log file.