From 1949d828b7d39b26aa474d94ab64bc8cc5ff3c5c Mon Sep 17 00:00:00 2001 From: Asterisk Development Team <asteriskteam@digium.com> Date: Thu, 29 Apr 2021 10:25:55 -0500 Subject: [PATCH] Update CHANGES and UPGRADE.txt for 18.4.0 --- CHANGES | 61 +++++++++++++++++++ UPGRADE.txt | 10 +++ doc/CHANGES-staging/logger_dateformat.txt | 47 -------------- ...pjsip_endpoint_unauthenticated_options.txt | 5 -- .../pjsip_transport_partial_reload.txt | 4 -- doc/UPGRADE-staging/menuselect-could-fail.txt | 5 -- 6 files changed, 71 insertions(+), 61 deletions(-) delete mode 100644 doc/CHANGES-staging/logger_dateformat.txt delete mode 100644 doc/CHANGES-staging/pjsip_endpoint_unauthenticated_options.txt delete mode 100644 doc/CHANGES-staging/pjsip_transport_partial_reload.txt delete mode 100644 doc/UPGRADE-staging/menuselect-could-fail.txt diff --git a/CHANGES b/CHANGES index 460f6f5af1..276b149c8f 100644 --- a/CHANGES +++ b/CHANGES @@ -12,6 +12,67 @@ === ============================================================================== +------------------------------------------------------------------------------ +--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------ +------------------------------------------------------------------------------ + +logger +------------------ + * The dateformat option in logger.conf will now control the remote + console (asterisk -r -T) timestamp format. Previously, dateformat only + controlled the formatting of the timestamp going to log files and the + main console (asterisk -c) but only for non-verbose messages. + + Internally, Asterisk does not send the logging timestamp with verbose + messages to console clients. It's up to the Asterisk remote consoles + to format verbose messages. Asterisk remote consoles previously did + not load dateformat from logger.conf. + + Previously there was a non-configurable and hard-coded "%b %e %T" + dateformat that would be used no matter what on all verbose console + messages printed on remote consoles. + + Example: + logger.conf + dateformat=%F %T.%3q + + # asterisk -rvvv -T + [2021-03-19 09:54:19.760-0400] Loading res_stasis_answer.so. + [Mar 19 09:55:43] -- Goto (dialExten,s,1) + + Given the following example configuration in logger.conf, Asterisk log + files and the console, will log verbose messages using the given + timestamp. Now ensuring that all remote console messages are logged + with the same dateformat as other log streams. + + --- + [general] + dateformat=%F %T.%3q + + [logfiles] + console => notice,warning,error,verbose + full => notice,warning,error,debug,verbose + --- + + Now we have a globally-defined dateformat that will be used + consistently across the Asterisk main console, remote consoles, and + log files. + + Now we have consistent logging: + + # asterisk -rvvv -T + [2021-03-19 09:54:19.760-0400] Loading res_stasis_answer.so. + [2021-03-19 09:55:43.920-0400] -- Goto (dialExten,s,1) + +res_pjsip +------------------ + * PJSIP transports can now be partially reloaded safely. This allows the + local_net and external_* options to be updated without restarting Asterisk. + + * PJSIP endpoints can now be configured to skip authentication when + handling OPTIONS requests by setting the allow_unauthenticated_options + configuration property to 'yes.' + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 18.2.2 to Asterisk 18.3.0 ------------ ------------------------------------------------------------------------------ diff --git a/UPGRADE.txt b/UPGRADE.txt index 7db926f1b5..5782164529 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -18,6 +18,16 @@ === =========================================================== +------------------------------------------------------------------------------ +--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------ +------------------------------------------------------------------------------ + +menuselect +------------------ + * menuselect --enable, --disable, --enable-category and --disable-category will + now fail with a non-zero exit code instead of silently failing if an invalid + option or category is specified. + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 18.2.2 to Asterisk 18.3.0 ------------ ------------------------------------------------------------------------------ diff --git a/doc/CHANGES-staging/logger_dateformat.txt b/doc/CHANGES-staging/logger_dateformat.txt deleted file mode 100644 index efeb11803d..0000000000 --- a/doc/CHANGES-staging/logger_dateformat.txt +++ /dev/null @@ -1,47 +0,0 @@ -Subject: logger - -The dateformat option in logger.conf will now control the remote -console (asterisk -r -T) timestamp format. Previously, dateformat only -controlled the formatting of the timestamp going to log files and the -main console (asterisk -c) but only for non-verbose messages. - -Internally, Asterisk does not send the logging timestamp with verbose -messages to console clients. It's up to the Asterisk remote consoles -to format verbose messages. Asterisk remote consoles previously did -not load dateformat from logger.conf. - -Previously there was a non-configurable and hard-coded "%b %e %T" -dateformat that would be used no matter what on all verbose console -messages printed on remote consoles. - -Example: -logger.conf - dateformat=%F %T.%3q - -# asterisk -rvvv -T -[2021-03-19 09:54:19.760-0400] Loading res_stasis_answer.so. -[Mar 19 09:55:43] -- Goto (dialExten,s,1) - -Given the following example configuration in logger.conf, Asterisk log -files and the console, will log verbose messages using the given -timestamp. Now ensuring that all remote console messages are logged -with the same dateformat as other log streams. - ---- -[general] -dateformat=%F %T.%3q - -[logfiles] -console => notice,warning,error,verbose -full => notice,warning,error,debug,verbose ---- - -Now we have a globally-defined dateformat that will be used -consistently across the Asterisk main console, remote consoles, and -log files. - -Now we have consistent logging: - -# asterisk -rvvv -T -[2021-03-19 09:54:19.760-0400] Loading res_stasis_answer.so. -[2021-03-19 09:55:43.920-0400] -- Goto (dialExten,s,1) diff --git a/doc/CHANGES-staging/pjsip_endpoint_unauthenticated_options.txt b/doc/CHANGES-staging/pjsip_endpoint_unauthenticated_options.txt deleted file mode 100644 index 9c8d32cb0e..0000000000 --- a/doc/CHANGES-staging/pjsip_endpoint_unauthenticated_options.txt +++ /dev/null @@ -1,5 +0,0 @@ -Subject: res_pjsip - -PJSIP endpoints can now be configured to skip authentication when -handling OPTIONS requests by setting the allow_unauthenticated_options -configuration property to 'yes.' diff --git a/doc/CHANGES-staging/pjsip_transport_partial_reload.txt b/doc/CHANGES-staging/pjsip_transport_partial_reload.txt deleted file mode 100644 index 1d1b0b6266..0000000000 --- a/doc/CHANGES-staging/pjsip_transport_partial_reload.txt +++ /dev/null @@ -1,4 +0,0 @@ -Subject: res_pjsip - -PJSIP transports can now be partially reloaded safely. This allows the -local_net and external_* options to be updated without restarting Asterisk. diff --git a/doc/UPGRADE-staging/menuselect-could-fail.txt b/doc/UPGRADE-staging/menuselect-could-fail.txt deleted file mode 100644 index e3e20ed833..0000000000 --- a/doc/UPGRADE-staging/menuselect-could-fail.txt +++ /dev/null @@ -1,5 +0,0 @@ -Subject: menuselect - -menuselect --enable, --disable, --enable-category and --disable-category will -now fail with a non-zero exit code instead of silently failing if an invalid -option or category is specified. -- GitLab