mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-03 03:20:57 +00:00
Update CHANGES and UPGRADE.txt for 18.1.0
This commit is contained in:
30
CHANGES
30
CHANGES
@@ -12,6 +12,36 @@
|
||||
===
|
||||
==============================================================================
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
--- Functionality changes from Asterisk 18.0.0 to Asterisk 18.1.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.
|
||||
|
||||
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 17.0.0 to Asterisk 18.0.0 ------------
|
||||
------------------------------------------------------------------------------
|
||||
|
@@ -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".
|
@@ -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>[:<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.
|
||||
|
Reference in New Issue
Block a user