6 Commits (efb520db4059ff6eff46ae7e30ea308435de9331)

Author	SHA1	Message	Date
Stefan Sayer	04039d909d	b/f: cleaner shutdown of registration timer thread	14 years ago
Stefan Sayer	015c2e3f3c	b/f: further safety precautions on timer buckets	14 years ago
Stefan Sayer	7a6126210d	b/f: fix index search for search from the past	14 years ago
Stefan Sayer	526678f013	b/f: fix registration refresh if calculated in the past ... for restarts with expired registrations and with minimum_register_interval set, this could lead to lost registrations	14 years ago
Stefan Sayer	acb2338dff	b/f: deadlock on timer too far in the future	14 years ago
Stefan Sayer	7ae3ca4d4d	initial checkin of db_reg_agent module ... Purpose ------- The db_reg_agent module allows SEMS to read SIP accounts from a database and register the accounts to SIP a registrar. In that it serves a similar purpose as the reg_agent/registrar_client modules, with the differences that it reads accounts from mysql DB instead of the file system, and that it is built to support many (up to several 10k) subscription. Additionally, accounts may be added, changed and removed while SEMS is running; the db_reg_agent then can be triggered via DI interface (XMLRPC/json-rpc) to pick up the new registration. Features - configurable subscription query - configurable desired expires - flatten out re-register spikes by intelligently planning registration refresh - ratelimiting (x new REGISTER requests per y seconds) - seamless restart of SEMS server possible; registration status is restored from DB.	14 years ago