Hi, I have a SIP registrar with a policy-based registration interval floor of 60 seconds.
One would expect that this means most devices would register with such an expiry time, and then refresh the registration a few seconds before it expires. However, there are numerous endpoints out there which refresh the registration at much higher frequencies, sometimes as low as every few seconds. That is to say, they request an interval of 60 seconds or more, but re-register every 2-5 seconds. I am putting in a mechanism to stop this, as it generates unnecessary load and is generally poor form. I am not sure, however, what the appropriate SIP response to these endpoints should be. My best guess is that '480 Temporarily Unavailable' with a 'Retry-After' header would make the most sense, but the language in the RFC is ambiguous as to whether this response is only contemplated in the context of a 'call' as opposed to a registration flow. Your insight is as always appreciated! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
