I remember a discussion a while about about this being randomized so that after a restart, everyone doesn't expire at the same time bogging the system down.
This is in the wiki - The sipXecs registrar attempts to spread registrations over time to smooth load (both on itself and on the network) caused by registration refreshes. It does this by shortening the granted registration time from the requested time by a random factor: . Normal length requests (for >= twice the allowed minimum) are randomized between twice the minimum and the configured maximum. . Short requests (for < twice the minimum) are randomized between the minimum and the requested amount. . Minimum length requests are not shortened (that would be hypocritical, since we would not accept a request that short). . Requests less than the minimum are rejected (with a header that tells the phone what the minimum allowed value is). When a phone requests a registration, it asks for a specific duration (the 'expires' time) in seconds. In a successful registration response, the 'expires' field parameter on the Contact header is set to the actual time the server has granted for the registration, which may (at the servers option) be less than the requested duration. If the phone does not refresh by that time, the registration will become inactive (it may still be visible in the database for other reasons, but will be marked 'expired' on the registrations display and will not be used to route calls). From: [email protected] [mailto:[email protected]] On Behalf Of Jan Fricke Sent: Wednesday, June 27, 2012 11:57 PM To: [email protected] Subject: [sipx-users] SipX registration expires value I'm doing some SIPp tests with an SipX 4.4 installation. My scenario registers 1000 extensions. The expires value in the register messages is set to 3600. I know that the expires value in the 200 OK response can be 3600 or less (RFC3261). In some cases it is ~2500 seconds in other cases just 600 seconds. In some situations I'm having trouble with my scenarios because registrations expire before the following call scenarios is done. I'll have to reregister regularly. But for interest I'd like to know how SipX decides how much registration time is gives to a registration. Can somebody explain please? Sincerely Jan _____________________________ Jan Fricke (B.Sc.) IANT - APPLIED NGN-TECHNOLOGIES Turn-Key VoIP/UC Solutions and More... Fon: +49 (5331) 6794 0 Fax: +49 (5331) 6794 499 Mail: <mailto:[email protected]> [email protected] Web: <http://www.iant.de/en/startseite> www.iant.de IANT is eZuce <http://www.ezuce.com/> Elite Partner for EMEA IANT is Member of GROUPLINK <http://www.grouplink.de/>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
