[asterisk-bugs] [Asterisk 0019287]: inverse / incorrect behavior for CLI / console logging of DTMF
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Jun 4 18:56:59 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=19287
======================================================================
Reported By: luckman212
Assigned To:
======================================================================
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-06-04 18:56 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'
======================================================================
----------------------------------------------------------------------
(0135715) luckman212 (reporter) - 2011-06-04 18:56
https://issues.asterisk.org/view.php?id=19287#c135715
----------------------------------------------------------------------
I was poking around in the '/include/asterisk/logger.h' code and it appears
(to my untrained eye at least) that on line 168:
#define LOG_VERBOSE __LOG_VERBOSE, _A_
..should actually be..
#define AST_LOG_VERBOSE __LOG_VERBOSE, _A_
I only say this because that would follow the structure of the other
variable declarations. AST_LOG seems to be some sort of macro but I admit
I do not really understand the code here. I don't know if this relates at
all but I noticed it and thought I would comment since we're on the subject
of logger.
Issue History
Date Modified Username Field Change
======================================================================
2011-06-04 18:56 luckman212 Note Added: 0135715
======================================================================
More information about the asterisk-bugs
mailing list