Summary:ASTERISK-21222: Behavior of 'logger set level' With Respect To Entries in logger.conf
Reporter:Daniel McElveen (dmcelveen)Labels:
Date Opened:2013-03-07 14:44:36.000-0600Date Closed:2013-03-11 20:37:22
Versions: 11.2.1 Frequency of
Environment:Ubuntu Linux 12.04 LTEAttachments:
Description:Customer types 'logger set level DTMF on', console doesn't begin to show any DTMF messages. 'logger show channels' also does not show DTMF as a channel for the console log, but rather what is set in the logger.conf file.

I've done some experimentation on various versions and builds of Asterisk and this is what I've come up with as it pertains to your wanted behavior:

1) The command 'logger show channels' shows only what was parsed from the logger.conf (and various #includes) file on the last logger module start. It does not update with executions of the 'logger set level' command. Is it possible that we can have this update to show what is currently being logged (and where it is being logged to) after the user toggles a logging state with 'logger set level'?

2) The command 'logger set level DTMF on' seems to have different behavior to other possible parameters of 'logger set level'. In order to see DTMF events in the console log, the line 'console =>' in logger.conf *must* contain the 'dtmf' parameter in order for the 'logger set level DTMF' toggle to work. However, the VERBOSE parameter of 'logger set level' can be toggled on/off whether the 'verbose' parameter is set in logger.conf or not. Is it possible to make this behavior more consistent?
Comments:By: Michael L. Young (elguero) 2013-03-11 20:36:01.830-0500

Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals.

[1] http://www.asterisk.org/support/mailing-lists