[asterisk-users] sip extension compromised, need help blocking brute force attempts

[Dovid B]

----- Original Message ----- 
From: "spectro" <spectro at gmail.com>
To: "Asterisk Users Mailing List - Non-Commercial Discussion" 
<asterisk-users at lists.digium.com>
Sent: Tuesday, July 01, 2008 8:02 PM
Subject: Re: [asterisk-users] sip extension compromised,need help blocking 
brute force attempts


> On Tue, Jul 1, 2008 at 11:19 AM, Tzafrir Cohen <tzafrir.cohen at xorcom.com> 
> wrote:
>>
>> Fix your logger.conf, then.
>>
>> --
>>               Tzafrir Cohen
>
> What am I missing?
>
>
> [root at asterisk1 ~]# cat /etc/asterisk/logger.conf
> ;
> ; Logging Configuration
> ;
> ; In this file, you configure logging to files or to
> ; the syslog system.
> ;
> ; For each file, specify what to log.
> ;
> ; For console logging, you set options at start of
> ; Asterisk with -v for verbose and -d for debug
> ; See 'asterisk -h' for more information.
> ;
> ; Directory for log files is configures in asterisk.conf
> ; option astlogdir
> ;
> [logfiles]
> ;
> ; Format is "filename" and then "levels" of debugging to be included:
> ;    debug
> ;    notice
> ;    warning
> ;    error
> ;    verbose
> ;
> ; Special filename "console" represents the system console
> ;
> ;debug => debug
> ;console => notice,warning,error
> ;console => notice,warning,error,debug
> ;messages => notice,warning,error
> full => notice,warning,error,debug,verbose
>
> ;syslog keyword : This special keyword logs to syslog facility
> ;
> ;syslog.local0 => notice,warning,error
> ;
> [root at asterisk1 ~]#
>
The script seems to run off the messages log. Uncomment the messages line 
and the reload the logger in asterisk (logger reload from the CLI).