Re: [Sipping] recover from avalance registrations

[Jonathan Rosenberg <[e-mail]>]

There is currently active working in defining overload mechanisms to 
address this. See:

http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-overload-reqs-02.txt
http://www.ietf.org/internet-drafts/draft-hilt-sipping-overload-00.txt

-Jonathan R.

[e-mail] wrote:

> Consider the following circumstances:
> 500000 users connected to a proxy-registrar configured as active/active
> each proxy registrar is capable of handling 500 registrations/s
> The phones register once every hour, in normal circumstances, which the 
> server
> can easily handle.
> However under double failures, in short time, the rate of registrations
> builds up massively, due to the cumulation of failed registrations which
> reattempt once per minute iso once per hour  and the  retransmissions  
> generated  for
> each of them.
> Successful registration of a user requires 2 cycles since the first 
> registration is challenged
> in the 401 response. Coming up after 10min, the first server is hit by 
> around 28000 registers/s
> After short time the chances for both register cycles to succeed, drops 
> to such small
> value, that it would take too much time to from the registration storm.
> Are there any recommendations concerning this.
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [e-mail] for questions on current sip
> Use [e-mail] for new developments of core SIP
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
[e-mail]                              FAX:   [phone]
http://www.jdrosen.net                         PHONE: [phone]
http://www.cisco.com

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP