mirror of https://github.com/asterisk/asterisk.git synced 2025-09-02 19:16:15 +00:00

Files

Alexei Gradinari 8a09a6ca6d app_queue: Add option to not log Restricted Caller ID to queue_log

Add a queue option log-restricted-caller-id to strip the Caller ID when storing the ENTERQUEUE event
in the queue log if the Caller ID is restricted.

Resolves: #765

UpgradeNote: Add a new column to the queues table:
queue_log_option_log_restricted ENUM('0','1','off','on','false','true','no','yes')
to control whether the Restricted Caller ID will be stored in the queue log.

UserNote: Add a Queue option log-restricted-caller-id to control whether the Restricted Caller ID
will be stored in the queue log.
If log-restricted-caller-id=no then the Caller ID will be stripped if the Caller ID is restricted.

(cherry picked from commit 192a848311)

2024-07-11 13:23:24 +00:00

cdr

Remove as much trailing whitespace as possible.

2017-12-22 09:23:22 -05:00

config

app_queue: Add option to not log Restricted Caller ID to queue_log

2024-07-11 13:23:24 +00:00

queue_log

ast-db-manage: Synchronize revisions between comments and code.

2023-06-12 14:40:15 +00:00

voicemail

app_voicemail_odbc: remove macrocontext from voicemail_messages table

2024-03-07 14:18:40 +00:00

.gitignore

alembic: Update list of TLS methods available on ps_transports.

2024-01-12 18:32:13 +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

env.py

alembic: Fix compatibility with SQLAlchemy 2.0+.

2024-05-09 13:48:09 +00:00

queue_log.ini.sample

queue_log: Add alembic script for generate db table for queue_log

2019-11-22 15:33:29 +00:00

README.md

contrib: Spelling fixes

2021-11-16 06:02:11 -06: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
queue_log - Table used for Asterisk to store Queue Log records
voicemail - Tables used for ODBC_STORAGE 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.