diff options
| author | Kevin Harwell <kharwell@digium.com> | 2015-10-21 11:51:13 -0500 |
|---|---|---|
| committer | Kevin Harwell <kharwell@digium.com> | 2015-10-23 09:43:20 -0500 |
| commit | c58091737da86e17cbad4d86ebf4f04055e505fa (patch) | |
| tree | 46945aab48871c077dc07c6f7f871aee0d2f3134 /contrib/ast-db-manage | |
| parent | 04030b0dd09421d633f662d7c82efe0c3b554856 (diff) | |
res_pjsip_outbound_registration: registration stops due to fatal 4xx response
During outbound registration it is possible to receive a fatal (any permanent/
non-temporary 4xx, 5xx, 6xx) response from the registrar that is simply due
to a problem with the registrar itself. Upon receiving the failure response
Asterisk terminates outbound registration for the given endpoint.
This patch adds an option, 'fatal_retry_interval', that when set continues
outbound registration at the given interval up to 'max_retries' upon receiving
a fatal response.
ASTERISK-25485 #close
Change-Id: Ibc2c7b47164ac89cc803433c0bbe7063bfa143a2
Diffstat (limited to 'contrib/ast-db-manage')
| -rw-r--r-- | contrib/ast-db-manage/config/versions/28ce1e718f05_add_fatal_response_interval.py | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/contrib/ast-db-manage/config/versions/28ce1e718f05_add_fatal_response_interval.py b/contrib/ast-db-manage/config/versions/28ce1e718f05_add_fatal_response_interval.py new file mode 100644 index 000000000..8c499aee8 --- /dev/null +++ b/contrib/ast-db-manage/config/versions/28ce1e718f05_add_fatal_response_interval.py @@ -0,0 +1,22 @@ +"""add fatal_response_interval + +Revision ID: 28ce1e718f05 +Revises: 154177371065 +Create Date: 2015-10-20 17:57:45.560585 + +""" + +# revision identifiers, used by Alembic. +revision = '28ce1e718f05' +down_revision = '154177371065' + +from alembic import op +import sqlalchemy as sa + + +def upgrade(): + op.add_column('ps_registrations', sa.Column('fatal_retry_interval', sa.Integer)) + + +def downgrade(): + op.drop_column('ps_registrations', 'fatal_retry_interval') |