From: Asterisk Development Team Date: Mon, 19 Oct 2020 18:06:13 +0000 (-0500) Subject: Update CHANGES and UPGRADE.txt for 16.14.0 X-Git-Tag: 16.15.0-rc1~20 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=69356a7895e96694f0993b637cff65261b9f8dea;p=thirdparty%2Fasterisk.git Update CHANGES and UPGRADE.txt for 16.14.0 --- diff --git a/CHANGES b/CHANGES index e6493d39cb..494cac4384 100644 --- a/CHANGES +++ b/CHANGES @@ -16,6 +16,57 @@ --- Functionality changes from Asterisk 16.13.0 to Asterisk 16.14.0 ---------- ------------------------------------------------------------------------------ +Core +------------------ + * Added debug logging categories that allow a user to output debug information + based on a specified category. This lets the user limit, and filter debug + output to data relevant to a particular context, or topic. For instance the + following categories are now available for debug logging purposes: + + dtls, dtls_packet, ice, rtcp, rtcp_packet, rtp, rtp_packet, stun, stun_packet + + These debug categories can be enable/disable via an Asterisk CLI command: + + core set debug category [:] [category[: [] ...] + + If no sub-level is associated all debug statements for a given category are + output. If a sub-level is given then only those statements assigned a value + at or below the associated sub-level are output. + +STIR/SHAKEN +------------------ + * STIR/SHAKEN support has been added to Asterisk. Configuration is done in + stir_shaken.conf. There is a sample configuration file to help you get + started (asterisk/configs/samples/stir_shaken.conf.sample). Once that's + set up, you can enable STIR/SHAKEN on any endpoint by setting stir_shaken + to yes on the endpoint configuration object. This will add an Identity + header on outgoing INVITEs, and check for an Identity header on incoming + INVITEs. This option has been added to Alembic as well. + + The information received on an incoming INVITE can be checked using the + STIR_SHAKEN dialplan function. There are two variations: + + STIR_SHAKEN(count) + STIR_SHAKEN(0, verify_result) + + The first variation will tell you how many STIR/SHAKEN results are on the + channel. The second fetches information for a specific result. The first + parameter is the index, followed by what information you want to retrieve. + The available options are 'verify_result', 'identity', and 'attestation'. + +app_confbridge +------------------ + * app_confbridge now has the ability to force the estimated bitrate on an SFU + bridge. To use it, set a bridge profile's remb_behavior to "force" and + set remb_estimated_bitrate to a rate in bits per second. The + remb_estimated_bitrate parameter is ignored if remb_behavior is something + other than "force". + +------------------------------------------------------------------------------ +--- Functionality changes from Asterisk 16.13.0 to Asterisk 16.14.0 ---------- +------------------------------------------------------------------------------ + chan_pjsip ------------------ * The PJSIP_SEND_SESSION_REFRESH dialplan function now issues a warning, and diff --git a/UPGRADE.txt b/UPGRADE.txt index 87c743c75f..4043e7308d 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -18,6 +18,16 @@ === =========================================================== +------------------------------------------------------------------------------ +--- Functionality changes from Asterisk 16.13.0 to Asterisk 16.14.0 ---------- +------------------------------------------------------------------------------ + +res_stir_shaken +------------------ + * A new directory has been added under the default (e.g., /var/lib/asterisk) - + inside the 'keys' directory - named 'stir_shaken'. This directory will + hold public keys that have been downloaded for STIR/SHAKEN verification. + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 16.9.0 to Asterisk 16.10.0 ----------- ------------------------------------------------------------------------------ diff --git a/doc/CHANGES-staging/app_confbridge.txt b/doc/CHANGES-staging/app_confbridge.txt deleted file mode 100644 index 092e392f5d..0000000000 --- a/doc/CHANGES-staging/app_confbridge.txt +++ /dev/null @@ -1,7 +0,0 @@ -Subject: app_confbridge - -app_confbridge now has the ability to force the estimated bitrate on an SFU -bridge. To use it, set a bridge profile's remb_behavior to "force" and -set remb_estimated_bitrate to a rate in bits per second. The -remb_estimated_bitrate parameter is ignored if remb_behavior is something -other than "force". diff --git a/doc/CHANGES-staging/logger_category.txt b/doc/CHANGES-staging/logger_category.txt deleted file mode 100644 index 67cc3ec7ad..0000000000 --- a/doc/CHANGES-staging/logger_category.txt +++ /dev/null @@ -1,18 +0,0 @@ -Subject: Core - -Added debug logging categories that allow a user to output debug information -based on a specified category. This lets the user limit, and filter debug -output to data relevant to a particular context, or topic. For instance the -following categories are now available for debug logging purposes: - - dtls, dtls_packet, ice, rtcp, rtcp_packet, rtp, rtp_packet, stun, stun_packet - -These debug categories can be enable/disable via an Asterisk CLI command: - - core set debug category [:] [category[: [] ...] - -If no sub-level is associated all debug statements for a given category are -output. If a sub-level is given then only those statements assigned a value -at or below the associated sub-level are output. - diff --git a/doc/CHANGES-staging/stir_shaken.txt b/doc/CHANGES-staging/stir_shaken.txt deleted file mode 100644 index 3ad1784bdf..0000000000 --- a/doc/CHANGES-staging/stir_shaken.txt +++ /dev/null @@ -1,20 +0,0 @@ -Subject: STIR/SHAKEN - -STIR/SHAKEN support has been added to Asterisk. Configuration is done in -stir_shaken.conf. There is a sample configuration file to help you get -started (asterisk/configs/samples/stir_shaken.conf.sample). Once that's -set up, you can enable STIR/SHAKEN on any endpoint by setting stir_shaken -to yes on the endpoint configuration object. This will add an Identity -header on outgoing INVITEs, and check for an Identity header on incoming -INVITEs. This option has been added to Alembic as well. - -The information received on an incoming INVITE can be checked using the -STIR_SHAKEN dialplan function. There are two variations: - -STIR_SHAKEN(count) -STIR_SHAKEN(0, verify_result) - -The first variation will tell you how many STIR/SHAKEN results are on the -channel. The second fetches information for a specific result. The first -parameter is the index, followed by what information you want to retrieve. -The available options are 'verify_result', 'identity', and 'attestation'. diff --git a/doc/UPGRADE-staging/res_stir_shaken_directory.txt b/doc/UPGRADE-staging/res_stir_shaken_directory.txt deleted file mode 100644 index 160241e742..0000000000 --- a/doc/UPGRADE-staging/res_stir_shaken_directory.txt +++ /dev/null @@ -1,5 +0,0 @@ -Subject: res_stir_shaken - -A new directory has been added under the default (e.g., /var/lib/asterisk) - -inside the 'keys' directory - named 'stir_shaken'. This directory will -hold public keys that have been downloaded for STIR/SHAKEN verification.