mirror of https://github.com/asterisk/asterisk.git synced 2025-09-05 04:11:08 +00:00

Files

Kevin Harwell 93ac45d3bd res_pjsip: Add option to force G.726 to be treated as AAL2 packed.

Some phones send g.726 audio packed for AAL2, which differs from what is
recommended by RFC 3351. If Asterisk receives audio formatted as such when
negotiating g.726 then it sounds a bit distorted. Added an option to
res_pjsip_endpoint that allows g.726 negotiated audio to be treated as g.726
AAL2 packed.

ASTERISK-25158 #close
Reported by: Steve Pitts

Change-Id: Ie7e21f75493d7fe53e75e12c971e72f5afa33615

2015-06-15 12:40:03 -05:00

cdr

ast-db-manage/cdr/env.py: Don't fail if a config file can't be loaded

2014-05-28 17:44:49 +00:00

config

res_pjsip: Add option to force G.726 to be treated as AAL2 packed.

2015-06-15 12:40:03 -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.