]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_pjsip_outbound_registration: registration stops due to fatal 4xx response 72/1472/6
authorKevin Harwell <kharwell@digium.com>
Wed, 21 Oct 2015 16:51:13 +0000 (11:51 -0500)
committerKevin Harwell <kharwell@digium.com>
Fri, 23 Oct 2015 14:43:20 +0000 (09:43 -0500)
commitc58091737da86e17cbad4d86ebf4f04055e505fa
tree46945aab48871c077dc07c6f7f871aee0d2f3134
parent04030b0dd09421d633f662d7c82efe0c3b554856
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
CHANGES
configs/samples/pjsip.conf.sample
contrib/ast-db-manage/config/versions/28ce1e718f05_add_fatal_response_interval.py [new file with mode: 0644]
res/res_pjsip_outbound_registration.c