Skip to content

Troubleshooting

Administration › Maintenance › Troubleshooting hosts the recorder diagnostic tools. The one you will use in practice is the Trace Log — detailed trace output from the recording service, the primary evidence to collect when investigating recording problems.

Recorder trace log

The recording service can write detailed trace information to text files. Tracing is configured centrally from the Troubleshooting page: click Edit Configuration next to Trace Log. The settings are stored as recorder settings, so they apply to your recorder servers (per-server overrides are possible through the recorder settings tree — see Recorder servers).

Configuration options:

  • Enable — turn trace-file writing on or off.
  • Trace log file name — full path to the trace file. Defaults: /var/log/miarec/trace/trace.log on Linux, Data\log\trace\trace.log on Windows.
  • Trace level — depth of trace information, 1 to 5. Use 5 (the default) when troubleshooting; it is the level MiaRec support expects in collected traces.
  • File rotation — hourly, daily, weekly, or monthly rotation, with a rotate day and time where applicable.

The trace files themselves are read from the server's file system (see Log files); they are not viewable in the web portal.

Warning

Trace level 5 is verbose. Leave tracing enabled only while reproducing a problem, and keep rotation on so trace files do not fill the log volume.

A troubleshooting workflow

  1. Reproduce the problem with tracing enabled at level 5.
  2. Note the time and, if possible, the affected extension or phone number.
  3. Collect the trace file(s) covering that window, plus any matching system log entries.
  4. Attach both to your support case, or analyze the SIP/protocol exchange in the trace directly.