[asterisk-bugs] [Asterisk 0019287]: inverse / incorrect behavior for CLI / console logging of DTMF
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 1 17:40:09 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-01 17:40 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'
======================================================================
----------------------------------------------------------------------
(0135632) luckman212 (reporter) - 2011-06-01 17:40
https://issues.asterisk.org/view.php?id=19287#c135632
----------------------------------------------------------------------
Thanks for the patch jrose. I installed this on my * system running SVN
1.8-r321537M
While there is progress towards a working patch, there is more to be done
afaik. The "gotcha" with this patch, I now have to exclusively turn ON the
channels via the CLI before I see anything. The only thing I see in the
console now is DTMF. This appears to be because the other channels are
defaulting to "off" at startup.
I tried defining (in cli.conf) that I want the various channels to be 'ON'
when I start asterisk. e.g. I put the following in cli.conf
[startup_commands]
logger set level NOTICE on = yes
logger set level WARNING on = yes
logger set level ERROR on = yes
logger set level VERBOSE on = yes
logger set level DTMF on = yes
but even with those commands in, nothing gets logged to the console (well,
actually **ONLY** DTMF does!) when I first attach to it. Then I type
'logger set level VERBOSE on' for example, and I start to see the normal
logging.
The strangeness continues!
Issue History
Date Modified Username Field Change
======================================================================
2011-06-01 17:40 luckman212 Note Added: 0135632
======================================================================
More information about the asterisk-bugs
mailing list