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

Files

Mark Michelson 10fa49e327 Add rtcp-mux support

This commit adds support for RFC 5761: Multiplexing RTP Data and Control
Packets on a Single Port. Specifically, it enables the feature when
using chan_pjsip.

A new option, "rtcp_mux" has been added to endpoint configuration in
pjsip.conf. If set, then Asterisk will attempt to use rtcp-mux with
whatever it communicates with. Asterisk follows the rules set forth in
RFC 5761 with regards to falling back to standard RTCP behavior if the
far end does not indicate support for rtcp-mux.

The lion's share of the changes in this commit are in
res_rtp_asterisk.c. This is because it was pretty much hard wired to
have an RTP and an RTCP transport. The strategy used here is that when
rtcp-mux is enabled, the current RTCP transport and its trappings (such
as DTLS SSL session) are freed, and the RTCP session instead just
mooches off the RTP session. This leads to a lot of specialized if
statements throughout.

ASTERISK-26732 #close
Reported by Dan Jenkins

Change-Id: If46a93ba1282418d2803e3fd7869374da8b77ab5

2017-03-15 16:34:13 -05:00

cdr

alembic: Allow cdr, config and voicemail to exist in the same schema

2016-10-07 07:49:42 -05:00

config

Add rtcp-mux support

2017-03-15 16:34:13 -05:00

voicemail

alembic: Allow cdr, config and voicemail to exist in the same schema

2016-10-07 07:49:42 -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

alembic: Allow cdr, config and voicemail to exist in the same schema

2016-10-07 07:49:42 -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.