[Spce-user] registration problems after upgrade to 2.6

[Joan Cifre (ibred)]

Hello all,
I think it's SOLVED! You can see attached the graph of registered 
devices in the last minutes, how it grows.
Now I've disabled the banning in the server and we will disable the keep 
alive message in the ATAs.
One question, was the banning process changed from 2.5 to 2.6? In 2.5 
users were not banned!

Thanks to all specially Lorenzo and Jon for the great support
Joan


El 05/01/2013 10:30, Jon Bonilla (Manwe) escribió:
> El Sat, 5 Jan 2013 10:21:17 +0100
> Lorenzo Mangani <lorenzo.mangani at gmail.com> escribió:
>
>> 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,
>>
>>
> Disabling the keepalive could also be a good idea. No need to send NOTIFY or
> REGISTER as the spce takes care of sending keepalives every 30 seconds to all
> nated registered devices.
>
> This interval can be changed in config.yml:
>
> kamailio_proxy_natping_interval
>
>
>
>
> _______________________________________________
> 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/f4da1c74/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: registered_solved.JPG
Type: image/jpeg
Size: 38340 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130105/f4da1c74/attachment-0001.JPG>