From c58091737da86e17cbad4d86ebf4f04055e505fa Mon Sep 17 00:00:00 2001 From: Kevin Harwell Date: Wed, 21 Oct 2015 11:51:13 -0500 Subject: 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 | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'CHANGES') diff --git a/CHANGES b/CHANGES index 1a0f7db8c..1deba235d 100644 --- a/CHANGES +++ b/CHANGES @@ -20,6 +20,13 @@ Dialplan Functions the 'hold' raised by a channel to be intercepted and converted into an event instead. +res_pjsip_outbound_registration +------------------------------- +* A new 'fatal_retry_interval' option has been added to outbound registration. + When set (default is zero), and upon receiving a failure response to an + outbound registration, registration is retried at the given interval up to + 'max_retries'. + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 13.5.0 to Asterisk 13.6.0 ------------ ------------------------------------------------------------------------------ -- cgit v1.2.3