Enabling Asterisk full logging

WHY?

When calls are not progressing as expected, the CLI call trace is a very useful tool in diagnosing and troubleshooting.

On busier systems, there are often several calls on the go simultaneously, making it almost impossible to follow the progress of a single call.

What does it do?

With full logging enabled, Asterisk writes all of the logging that you'd see in real time on the CLI, to a log file at /var/log/asterisk/full

The full log is disabled by default, as it tends to become a very very large log file if left running.

Enabling full log

Full logging can be enabled by editing the /etc/asterisk/logger_logfiles_additional.conf file to reflect: full => debug,error,notice,verbose,warning

The number after verbose is the verbosity degree represented by a number within parenthesis eg. "(4)"

> sudo jed /etc/asterisk/logger_logfiles_additional.conf

> sudo asterisk -rx "logger reload"

After reloading the logger on Asterisk, logging of type notice, warning,error,debug and verbose will be written to /var/log/asterisk/full

Disabling full logging

If you want to disable full logging, adding a semi colon ';' before "full" comments out the line pertaining to "full", then saving the file, and reloading the logger on Asterisk will stop full logging.