Professional Documents
Culture Documents
Tracker
STEPS
Collecting Debug Information for the Asterisk Issue Tracker
STEPS
Configure Asterisk logging
Configure verbosity levels and rotate logs
Enable channel tech or feature specific debug
Issue reproduction and clean up
Provide debug to the developers
logger.conf
[logfiles]
debug_log_123456 => notice,warning,error,debug,verbose,dtmf
Asterisk 13+
In Asterisk 13 and later, you can dynamically create log channels from the CLI using the logger
add channel command. For example, to create the log file above, you would enter:
The new log channel persists until Asterisk is restarted, the logger module is reloaded, or the log
files are rotated. If using this CLI command, do not reload/restart/rotate the log files in Step 2.
2. From the Asterisk CLI, set the verbose and debug levels for logging (this affects CLI and log
output) and then restart the logger module:
*CLI> core set verbose 5
*CLI> core set debug 5
*CLI> module reload logger
Optionally, if you've used this file to record data previously, then rotate the logs:
*CLI> logger rotate
2.1. Depending on your issue and if a protocol level trace is requested, be sure to enable logging for
the channel driver or other module.
3. Now that logging is configured, enabled and verbosity is turned up you should reproduce your
issue.
4. Once finished, be sure to disable the extra debugging:
4.1. Again, remember to disable any extra logging for channel drivers or features.
SIP (1.4 or higher)
logger.conf
[logfiles]
;debug_log_123456 => notice,warning,error,debug,verbose,dtmf
Then reload the logger module (or restart Asterisk) as you did in step 2:
*CLI> module reload logger
1. Do NOT post the output of your file as a comment. This clutters the issue and will only result
in your comment being deleted.
2. Attach the file with a .txt extension to make it easy for the developers to quickly open the file
without downloading.
Files are attached on the issue page with following menu items: ( More > Attach files )