Browse
 
Tools
Rss Categories

Important Logs

1 ASR Client Log

The client_asr.txt file contains information about the speech client (the Media Server) and its communication with the ASR server. Failures that are specific to ASR requests are indicated in this log. The log also contains information about voice activity…

2 Critical Logs

The most important LumenVox log file is one called lumenvox_critical.txt. This is a special log that only contains critical errors. These are errors that would be likely to cause serious problems for a production system, such as when the speech client cannot…

3 Exceptions Logs

The presence of any log that starts with the word "Exceptions" indicates that there was an exception in some piece of LumenVox code, and should be treated with concern. Since exceptions logs contain information intended only for LumenVox engineers, it is…

4 Media Server Log

The media_server_app.txt log (located in the Media Server logs directory) is one of the most useful logs in troubleshooting any kind of issue related to MRCP communication. With logging verbosity turned to 3 in the client_property.conf file, the Media Server…

5 Restart Logs

Each application writes out a special log file called appname_server_restart.txt (e.g. tts_server_restart.txt or media_server_restart.txt) when it restarts. These logs contain just the information about the startup sequence for an application. Usually, this…

6 Status Logs

Most LumenVox services have an associated status log that can be enabled using the enable_app_stat_logging setting in the corresponding configuration file. Selecting a value of 0 for this will disable the status logging for that service. The default value…

7 TTS Client Log

The client_tts.txt file contains information about the TTS client’s communication with the TTS server. Failures that are specific to TTS requests are indicated in this log. You can generally correlate SYNTHESIZE events in MRCP with activity in this log.…