[Spce-user] 403 Try again later
agranig at sipwise.com
Wed Aug 29 04:55:54 EDT 2012
You ran into the DOS/DDOS protection. A client is blocked for X minutes
if it tries authentication with invalid credentials for Y times within Z
minutes (you can tune or turn it off in config.yml, search for
"security"). The other check is if you exceed X packets within Y seconds
from one single IP, and you get blocked for Z minutes.
To unblock the first, execute "ngcp-sercmd lb htable.dump auth" to check
which clients are blocked, then do "ngcp-sercmd lb htable.delete auth
To unblock a blocked IP, execute "ngcp-sercmd lb htable.dump ipban" to
check which clients are blocked, then do "ngcp-sercmd lb htable.delete
With the v2.6 released later today, there is a web interface in the
admin panel to do this :)
On 08/29/2012 10:47 AM, Mario Contreras wrote:
> Hi all,
> I am experiecing some troubles with asterisk. Until now, it worked
> perfectly, but since yesterday, when I did an upgrade, sipwise answer
> with 403 to registers from asterisk.
> An example:
> U 2012/08/29 10:43:44.820508 22.214.171.124:5060 -> 10.0.1.117:5060
> SIP/2.0 403 Try again later'
> Via: SIP/2.0/UDP 10.0.1.117:5060;branch=z9hG4bK5d588f89;rport=5060'
> From: <sip:centralitavv at sip.innovasur.es>;tag=as2315684b'
> <sip:centralitavv at sip.innovasur.es>;tag=e561cf6294b3b74fa2789cff4fa99e42.e19d'
> Call-ID: 236de70c7d0ed3e964a08e925aa71942 at 127.0.0.1'
> CSeq: 126 REGISTER'
> Server: Sipwise NGCP LB 2.X'
> Content-Length: 0'
> In asterisk appears like the password is incorrect, but it isn't. Any
> ideas?? Thanks.
> Spce-user mailing list
> Spce-user at lists.sipwise.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 900 bytes
Desc: OpenPGP digital signature
More information about the Spce-user