Comment 3 for bug 1909816

Thank you for taking the time to report a bug, and sorry for not getting back to you sooner. This must have fallen through the cracks and we didn't process it during our daily triages.

I can confirm here that asterisk will output its logs to two places:

- The console (which is what ends up in journalctl)
- The /var/log/asterisk/messages file

I also agree that it is somewhat annoying to have an application dump its logs into journalctl, especially when it already logs things elsewhere.

I noticed that you don't actually need to tweak asterisk's service file; all you need to do is edit /etc/asterisk/logger.conf and comment the following line:

console => notice,warning,error

Once you do that, you will stop seeing the logs on journalctl (but they will keep being log on /var/log/asterisk/messages).

I think this is a valid request. Given that the "fix" to this problem is easy and well documented, I am marking this as Low priority. Would you like to try submitting this request to the Debian asterisk package as well? This way, if they fix it in Debian, Ubuntu will automatically pick up the change.

Thank you.