Ticket #3169 (closed Feature Requests: duplicate)

Opened 4 months ago

Last modified 2 months ago

store user/device settings in DB

Reported by: lazytt Assigned to: p_lindheimer
Priority: minor Milestone: 2.6
Component: Core Version: SVN-HEAD
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by lazytt)

Move user/device settings to sql database (mysql/sqlite). This will provide for simpler/cleaner backups and easer clusterin/HA situations. The info can be written to the astDB when the orange bar is pressed. The easiest way to prevent duplicate entries (assuming asterisk will even allow it) and to prevent/fix/heal corruption is by deleting the AMPUSER and DEVICE keytree every time and re-writing the values.
Q. Can we just read/write straight to the db and skip the astDB total?

Change History

09/07/08 13:48:18 changed by lazytt

  • description changed.

09/07/08 15:03:27 changed by p_lindheimer

we can't just write to sql and copy, and many settings are dynamic and can change based on feature codes, xml scripts and other programs.

func_odbc has been something discussed for this. The problem is, although it would not be hard to make all the changes in FreePBX, there is a large eco-system of other web apps, xml apps, etc. that expect them to be in astdb.

what we have discussed is to put a very lite wrapper in Asterisk that would effectively use func_odbc for all the astdb calls. Then you would bring the whole eco-system with you, without having to change anything initially and then over time, you can get smart in external apps and change the settings in the database vs. through the manager like today.

11/23/08 09:37:32 changed by lazytt

  • status changed from new to closed.
  • resolution set to duplicate.

superseded by #3365