mirror of https://github.com/asterisk/asterisk.git synced 2025-09-04 20:04:50 +00:00

Files

Kevin Harwell 0ddbf6bc45 res_pjsip: allow TLS verification of wildcard cert-bearing servers

Rightly the use of wildcards in certificates is disallowed in accordance
with RFC5922. However, RFC2818 does make some allowances with regards to
their use when using subject alt names with DNS name types.

As such this patch creates a new setting for TLS transports called
'allow_wildcard_certs', which when it and 'verify_server' are both enabled
allows DNS name types, as well as the common name that start with '*.'
to match as a wildcard.

For instance: *.example.com
will match for: foo.example.com

Partial matching is not allowed, e.g. f*.example.com, foo.*.com, etc...
And the starting wildcard only matches for a single level.

For instance: *.example.com
will NOT match for: foo.bar.example.com

The new setting is disabled by default.

ASTERISK-30072 #close

Change-Id: If0be3fdab2e09c2a66bb54824fca406ebaac3da4

2022-06-30 16:54:16 -05:00

cdr

Remove as much trailing whitespace as possible.

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

config

res_pjsip: allow TLS verification of wildcard cert-bearing servers

2022-06-30 16:54:16 -05:00

queue_log

queue_log: Add alembic script for generate db table for queue_log

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

voicemail

contrib: Spelling fixes

2021-11-16 05:36:24 -06: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

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 05:36:24 -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.