sysmocom/asterisk
11
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
asterisk/contrib/ast-db-manage
History
Alexei Gradinari f0546d1d87 res_pjsip: add option to enable ContactStatus event when contact is updated 
The commit I2f97ebfa79969a36a97bb7b9afd5b6268cf1a07d removed sending out
the ContactStatus AMI event when a contact is updated.
Thist change broke things which rely on old behavior.

This patch adds a new PJSIP global configuration option
'send_contact_status_on_update_registration' to be able to preserve old
ContactStatus behavior.
By default new behavior, i.e. the ContactStatus event will not be sent when a
device refreshes its registration.

Change-Id: I706adf7584e7077eb6bde6d9799ca408bc82ce46
2019-01-11 10:52:18 -05:00
..
cdr Remove as much trailing whitespace as possible. 2017-12-22 09:23:22 -05:00
config res_pjsip: add option to enable ContactStatus event when contact is updated 2019-01-11 10:52:18 -05:00
voicemail Remove as much trailing whitespace as possible. 2017-12-22 09:23:22 -05:00
cdr.ini.sample alembic: Adjust sippeers, queue_members, and voicemail_messages tables. 2014-08-06 17:04:08 +00:00
config.ini.sample alembic: Adjust sippeers, queue_members, and voicemail_messages tables. 2014-08-06 17:04:08 +00:00
env.py Remove as much trailing whitespace as possible. 2017-12-22 09:23:22 -05:00
README.md Add text of cdr directory into README.md for ast-db-manage 2016-09-30 18:32:19 -03:00
voicemail.ini.sample alembic: Adjust sippeers, queue_members, and voicemail_messages tables. 2014-08-06 17:04:08 +00:00

README.md

Asterisk Database Manager

Asterisk includes optional database integration for a variety of features. The purpose of this effort is to assist in managing the database schema for Asterisk database integration.

This is implemented as a set of repositories that contain database schema migrations, using Alembic. The existing repositories include:

  • cdr - Table used for Asterisk to store CDR records
  • config - Tables used for Asterisk realtime configuration
  • voicemail - Tables used for ODBC_STOARGE of voicemail messages

Alembic uses SQLAlchemy, which has support for many databases.

IMPORTANT NOTE: This is brand new and the initial migrations are still subject to change. Only use this for testing purposes for now.

Example Usage

First, create an ini file that contains database connection details. For help with connection string details, see the SQLAlchemy docs.

$ cp config.ini.sample config.ini
... edit config.ini and change sqlalchemy.url ...

Next, bring the database up to date with the current schema.

$ alembic -c config.ini upgrade head

In the future, as additional database migrations are added, you can run alembic again to migrate the existing tables to the latest schema.

$ alembic -c config.ini upgrade head

The migrations support both upgrading and downgrading. You could go all the way back to where you started with no tables by downgrading back to the base revision.

$ alembic -c config.ini downgrade base

base and head are special revisions. You can refer to specific revisions to upgrade or downgrade to, as well.

$ alembic -c config.ini upgrade 4da0c5f79a9c

Offline Mode

If you would like to just generate the SQL statements that would have been executed, you can use alembic's offline mode.

$ alembic -c config.ini upgrade head --sql

Adding Database Migrations

The best way to learn about how to add additional database migrations is to refer to the Alembic documentation.