History

Richard Mudgett ba362822f3 res_pjsip: Add ignore_uri_user_options option. This implements the chan_sip legacy_useroption_parsing option but with a better name. * Made the caller-id number and redirecting number strings obtained from incoming SIP URI user fields always truncated at the first semicolon. People don't care about anything after the semicolon showing up on their displays even though the RFC allows the semicolon. ASTERISK-26316 #close Reported by: Kevin Harwell Change-Id: Ib42b0e940dd34d84c7b14bc2e90d1ba392624f62		2016-09-09 17:13:02 -05:00
..
cdr	Increase account code maximum length to 80.	2015-11-05 10:20:34 -05:00
config	res_pjsip: Add ignore_uri_user_options option.	2016-09-09 17:13:02 -05:00
voicemail	alembic: Adjust sippeers, queue_members, and voicemail_messages tables.	2014-08-06 17:04:08 +00: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
README.md	Actually add the database schema management utilities	2013-08-29 12:30:07 +00: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:

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.