[sr-dev] [tracker] Task opened: default_expires_range should be applied to all expire times, not only to default
bugtracker at sip-router.org
Mon Sep 24 17:10:35 CEST 2012
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - P. Wojke (pwojke)
Attached to Project - sip-router
Summary - default_expires_range should be applied to all expire times, not only to default
Task Type - Improvement
Category - registrar (k)
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.3
Due in Version - Undecided
Due Date - Undecided
Details - The intention of the default_expires_range parameter is to distribute registrations over time. This should prevent registration bulks after a failure, where initial many registrations come in a short period, and if expire times are fix, reregistration will also come in a short period.
At the moment randomization is only done for the default value. This value is only used if no expires header is set. But many devices, e.g. Fritz!Box, will always send an expire header. This makes the default_expires_range parameter useless.
Randomization should be done regardless of source of expire value. The randomization code should be moved from get_expire_val function to calc_contact_expires.
More information can be found at the following URL:
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the sr-dev