[Spce-user] 403 Try again later
Jon Bonilla (Manwe)
jbonilla at sipwise.com
Wed Aug 29 04:58:09 EDT 2012
El Wed, 29 Aug 2012 10:47:32 +0200
Mario Contreras <mario.contreras at innovasur.es> escribió:
> 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 126.96.36.199: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.
Yes. Most probably your user is banned because it has incorrectly authenticated
3 times in a period of time.
This may happen either because the password is wrong or because the
registration process is being done in periods of less than 5 minutes. A patch
for this cause will be ready in some minutes.
You can check if the user is banned via the command:
ngcp-kamctl lb htable.dump auth
We've added a web frontend for this in 2.6 btw. I'll inform you as soon as I
release the patch for short-period register configurations.
More information about the Spce-user