--- 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>[:<sublevel>] [category[:<sublevel] ...]
+ core set debug category off [<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
===
===========================================================
+------------------------------------------------------------------------------
+--- 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 -----------
------------------------------------------------------------------------------
+++ /dev/null
-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".
+++ /dev/null
-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>[:<sublevel>] [category[:<sublevel] ...]
- core set debug category off [<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.
-
+++ /dev/null
-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'.
+++ /dev/null
-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.
projects / thirdparty / asterisk.git / commitdiff
