[Spce-user] registration problems after upgrade to 2.6

[Lorenzo Mangani]

Joan,

If this is the case as Jon seems to also suggest and the ban is caused by
the NOTIFY messages getting rejected, try to switch off you ATA
"keep-alive" behavior or alternatively, change it from $NOTIFY to $REGISTER
and it should have better luck,

Best,

Lorenzo Mangani

HOMER DEV TEAM
QXIP - Network Engineering

On Sat, Jan 5, 2013 at 10:14 AM, Jon Bonilla <jbonilla at sipwise.com> wrote:

> El Sat, 5 Jan 2013 10:10:11 +0100
> Lorenzo Mangani <lorenzo.mangani at gmail.com> escribió:
>
> > Joan,
> >
> > I might be wrong but I think your clients are getting blacklisted/banned
> by
> > the SPCE (maybe triggered by all those broken NOTIFY messages exceed the
> > set limits)
> > You can check from the web UI [System Administration > Security Bans] if
> > either the user or the IP are indeed getting blocked.
> > Alternatively I believe the command to check is "ngcp-sercmd lb
> htable.dump
> > auth"
> >
> >
>
> Good guess Lorenzo.
>
> There are two hashtables to check "auth" for the authentication bans, where
> the user is banned and "ipban" for banned ips due to too many requests per
> second (50 requests in 10 seconds by default)
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130105/fc95ba9d/attachment-0001.html>