[asterisk-bugs] [Asterisk 0019287]: inverse / incorrect behavior for CLI / console logging of DTMF

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19287 
====================================================================== 
Reported By:                luckman212
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   19287
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.4 
JIRA:                       SWP-3468 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-05-12 23:54 CDT
Last Modified:              2011-05-13 09:30 CDT
====================================================================== 
Summary:                    inverse / incorrect behavior for CLI / console
logging of DTMF
Description: 
try this:

set /etc/asterisk/logger.conf as so:
[general]
dateformat=%F %T

[logfiles]
messages => notice,warning,error
full => dtmf,notice,warning,error,debug,verbose
console => dtmf,notice,warning,error


Now, start Asterisk CLI and try to play some DTMF tones, you won't see
them logged to the console (but they ARE logged to /var/log/asterisk/full)

now,
type 'logger set level DTMF off'   (yes, OFF)

and test again, now DTMF is being logged to console! 
so it seems the switch is somehow 'backwards'
====================================================================== 

---------------------------------------------------------------------- 
 (0134896) luckman212 (reporter) - 2011-05-13 09:30
 https://issues.asterisk.org/view.php?id=19287#c134896 
---------------------------------------------------------------------- 
Interesting!  yes I was fumbling and stumbling through the code and it
seemed to me like that's what was happening too-  somehow the inital value
was being set wrong during initial load, so if argv[4] should == 1 to cause
messages to be printed to the console, then perhaps it was being set to -1,
or 2 etc and then setting the loglevel to 'off' caused it to flip back to 1
somehow.  But I couldn't understand why the messages were still being
correctly written to the FILES.  So I thought there might be some problems
in the logger_print_normal() func around line  of 897 logger.c as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-13 09:30 luckman212     Note Added: 0134896                          
======================================================================