[asterisk-bugs] [Asterisk 0017198]: Changing storm-prevention behaviour in logger.conf
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Apr 17 16:03:47 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17198
======================================================================
Reported By: rbressers
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17198
Category: Core/General
Reproducibility: always
Severity: feature
Priority: normal
Status: new
Asterisk Version: 1.4.30
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-04-17 08:41 CDT
Last Modified: 2010-04-17 16:03 CDT
======================================================================
Summary: Changing storm-prevention behaviour in logger.conf
Description:
According to https://issues.asterisk.org/view.php?id=14905 there is a storm
prevention mechanism in newer Asterisks. If i look in my logfile, i see :
[2010-04-17 15:12:01] NOTICE[1190] chan_sip.c: Registration from '"xxxx"
<sip:xxx at xxx.xxx.xxx.xxx>' failed for 'xx.xx.xx.xx' - Wrong password
[2010-04-17 15:12:01] NOTICE[1190] chan_sip.c: Last message repeated 3
times
This IS a good thing to do, but i want to disable this behaviour. We are
using fail2ban to ban scripts and people from the Asterisk system. On
version 1.4.23 this worked fine, but now this mechanism is in place, i
cannot use fail2ban anymore.
Is there any option to disable this behaviour, or even better, add it to
logger.conf so anybody can decide what to do?
======================================================================
----------------------------------------------------------------------
(0120563) pabelanger (manager) - 2010-04-17 16:03
https://issues.asterisk.org/view.php?id=17198#c120563
----------------------------------------------------------------------
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it would
make more sense to raise your question in the support tracker,
http://www.asterisk.org/support
Issue History
Date Modified Username Field Change
======================================================================
2010-04-17 16:03 pabelanger Note Added: 0120563
======================================================================
More information about the asterisk-bugs
mailing list