Paul Kyzivat <pkyzi...@alum.mit.edu> writes: > Strategies for preventing registration storms (e.g., after a major power > outage and recovery) have been discussed from time to time. > > Can anyone point me to specific documentation of such schemes? Ideally a > spec that can be referenced, but failing that I'll be happy with > pointers to thorough email discussions or non-standard implementations.
There is draft-shen-sipping-avalanche-restart-overload, but I don't know to what degree that mechanism was ever implemented. Pjsip had randomization of its reregistration interval. See https://trac.pjsip.org/repos/ticket/1802 In the sipX open-source system, we had the registrar hand out randomized registration intervals because otherwise, load-dependent delays in registrar processing would cause all of the phones in the system to gradually converge to reregistering in synchrony. But I can't find much discussion of the topic anywhere. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
