mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-14 16:33:34 +00:00
Update CHANGES and UPGRADE.txt for 18.5.0
This commit is contained in:
Asterisk Development Team
87
CHANGES
87
CHANGES
@@ -12,6 +12,93 @@
|
|||||||
===
|
===
|
||||||
==============================================================================
|
==============================================================================
|
||||||
|
|
||||||
|
------------------------------------------------------------------------------
|
||||||
|
--- Functionality changes from Asterisk 18.4.0 to Asterisk 18.5.0 ------------
|
||||||
|
------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
AMI Flash event
|
||||||
|
------------------
|
||||||
|
* Hook flash events are now exposed as AMI events.
|
||||||
|
|
||||||
|
Add variable support to Originate
|
||||||
|
------------------
|
||||||
|
* The Originate application now allows
|
||||||
|
variables to be set on the new channel
|
||||||
|
through a new option.
|
||||||
|
|
||||||
|
MessageSend
|
||||||
|
------------------
|
||||||
|
* The MessageSend dialplan application now takes an
|
||||||
|
optional third argument that can set the message's
|
||||||
|
"To" field on outgoing messages. It's an alternative
|
||||||
|
to using the MESSAGE(to) dialplan function.
|
||||||
|
|
||||||
|
To prevent confusion with the first argument, currently
|
||||||
|
named "to", it's been renamed to "destination".
|
||||||
|
Its function, creating the request URI, hasn't changed.
|
||||||
|
|
||||||
|
The online documentation has also been enhanced to
|
||||||
|
explain the behavior.
|
||||||
|
|
||||||
|
Despite the changes in this commit, there should be
|
||||||
|
no impact to current users of MessageSend.
|
||||||
|
|
||||||
|
New ConfKick application
|
||||||
|
------------------
|
||||||
|
* Adds a ConfKick() application, which allows
|
||||||
|
a specific channel, all users, or all non-admin
|
||||||
|
users to be kicked from a conference bridge.
|
||||||
|
|
||||||
|
app_confbridge answer supervision control
|
||||||
|
------------------
|
||||||
|
* app_confbridge now provides a user option to prevent
|
||||||
|
answer supervision if the channel hasn't been
|
||||||
|
answered yet. To use it, set a user profile's
|
||||||
|
answer_channel option to no.
|
||||||
|
|
||||||
|
app_voicemail
|
||||||
|
------------------
|
||||||
|
* You can now customize the "beep" tone or omit it entirely.
|
||||||
|
|
||||||
|
func_math: Three new dialplan functions
|
||||||
|
------------------
|
||||||
|
* Introduce three new functions, MIN, MAX, and ABS, which can be used to
|
||||||
|
obtain the minimum or maximum of up to two integers or absolute value.
|
||||||
|
|
||||||
|
func_volume now can be read
|
||||||
|
------------------
|
||||||
|
* The VOLUME function can now also be used
|
||||||
|
to read existing values previously set.
|
||||||
|
|
||||||
|
res_pjsip
|
||||||
|
------------------
|
||||||
|
* PJSIP support of registrations of endpoints in multidomain
|
||||||
|
scenarios, where the endpoint contains the domain info
|
||||||
|
in pjsip_endpoint.conf
|
||||||
|
|
||||||
|
res_pjsip_dialog_info_body_generator
|
||||||
|
------------------
|
||||||
|
* PJSIP now supports RFC 4235 Section 4.1.6 dialog-info+xml local and
|
||||||
|
remote elements by iterating through ringing channels and inserting
|
||||||
|
that info into NOTIFY packet sent to the endpoint.
|
||||||
|
|
||||||
|
res_pjsip_messaging
|
||||||
|
------------------
|
||||||
|
* Implemented the new "to" parameter of the MessageSend()
|
||||||
|
dialplan application. This allows a user to specify
|
||||||
|
a complete SIP "To" header separate from the Request URI.
|
||||||
|
We now also accept a destination in the same format
|
||||||
|
as Dial()... PJSIP/number@endpoint
|
||||||
|
|
||||||
|
res_rtp_asterisk
|
||||||
|
------------------
|
||||||
|
* By default Asterisk reports the PJSIP version in all
|
||||||
|
STUN packets it sends.
|
||||||
|
|
||||||
|
This behaviour may not be desired in a production
|
||||||
|
environment and can now be disabled by setting the
|
||||||
|
stun_software_attribute option to 'no' in rtp.conf.
|
||||||
|
|
||||||
------------------------------------------------------------------------------
|
------------------------------------------------------------------------------
|
||||||
--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------
|
--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------
|
||||||
------------------------------------------------------------------------------
|
------------------------------------------------------------------------------
|
||||||
|
|||||||
18
UPGRADE.txt
18
UPGRADE.txt
@@ -18,6 +18,24 @@
|
|||||||
===
|
===
|
||||||
===========================================================
|
===========================================================
|
||||||
|
|
||||||
|
------------------------------------------------------------------------------
|
||||||
|
--- Functionality changes from Asterisk 18.4.0 to Asterisk 18.5.0 ------------
|
||||||
|
------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
STIR/SHAKEN
|
||||||
|
------------------
|
||||||
|
* The configuration option public_key_url in stir_shaken.conf
|
||||||
|
has been renamed to public_cert_url to better fit what it
|
||||||
|
contains. Only the name has changed - functionality is the
|
||||||
|
same.
|
||||||
|
|
||||||
|
* STIR/SHAKEN originally needed an origid to be specified in
|
||||||
|
stir_shaken.conf under the certificate config object in
|
||||||
|
order to work. Now, one is automatically created by
|
||||||
|
generating a UUID, as recommended by RFC8588. Any origid
|
||||||
|
you have in your stir_shaken.conf will need to be removed
|
||||||
|
for the module to read in certificates.
|
||||||
|
|
||||||
------------------------------------------------------------------------------
|
------------------------------------------------------------------------------
|
||||||
--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------
|
--- Functionality changes from Asterisk 18.3.0 to Asterisk 18.4.0 ------------
|
||||||
------------------------------------------------------------------------------
|
------------------------------------------------------------------------------
|
||||||
|
|||||||
@@ -1,6 +0,0 @@
|
|||||||
Subject: app_confbridge answer supervision control
|
|
||||||
|
|
||||||
app_confbridge now provides a user option to prevent
|
|
||||||
answer supervision if the channel hasn't been
|
|
||||||
answered yet. To use it, set a user profile's
|
|
||||||
answer_channel option to no.
|
|
||||||
@@ -1,6 +0,0 @@
|
|||||||
Subject: New ConfKick application
|
|
||||||
|
|
||||||
Adds a ConfKick() application, which allows
|
|
||||||
a specific channel, all users, or all non-admin
|
|
||||||
users to be kicked from a conference bridge.
|
|
||||||
|
|
||||||
@@ -1,6 +0,0 @@
|
|||||||
Subject: Add variable support to Originate
|
|
||||||
|
|
||||||
The Originate application now allows
|
|
||||||
variables to be set on the new channel
|
|
||||||
through a new option.
|
|
||||||
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
Subject: AMI Flash event
|
|
||||||
|
|
||||||
Hook flash events are now exposed as AMI events.
|
|
||||||
@@ -1,4 +0,0 @@
|
|||||||
Subject: func_math: Three new dialplan functions
|
|
||||||
|
|
||||||
Introduce three new functions, MIN, MAX, and ABS, which can be used to
|
|
||||||
obtain the minimum or maximum of up to two integers or absolute value.
|
|
||||||
@@ -1,4 +0,0 @@
|
|||||||
Subject: func_volume now can be read
|
|
||||||
|
|
||||||
The VOLUME function can now also be used
|
|
||||||
to read existing values previously set.
|
|
||||||
@@ -1,16 +0,0 @@
|
|||||||
Subject: MessageSend
|
|
||||||
|
|
||||||
The MessageSend dialplan application now takes an
|
|
||||||
optional third argument that can set the message's
|
|
||||||
"To" field on outgoing messages. It's an alternative
|
|
||||||
to using the MESSAGE(to) dialplan function.
|
|
||||||
|
|
||||||
To prevent confusion with the first argument, currently
|
|
||||||
named "to", it's been renamed to "destination".
|
|
||||||
Its function, creating the request URI, hasn't changed.
|
|
||||||
|
|
||||||
The online documentation has also been enhanced to
|
|
||||||
explain the behavior.
|
|
||||||
|
|
||||||
Despite the changes in this commit, there should be
|
|
||||||
no impact to current users of MessageSend.
|
|
||||||
@@ -1,5 +0,0 @@
|
|||||||
Subject: res_pjsip
|
|
||||||
|
|
||||||
PJSIP support of registrations of endpoints in multidomain
|
|
||||||
scenarios, where the endpoint contains the domain info
|
|
||||||
in pjsip_endpoint.conf
|
|
||||||
@@ -1,5 +0,0 @@
|
|||||||
Subject: res_pjsip_dialog_info_body_generator
|
|
||||||
|
|
||||||
PJSIP now supports RFC 4235 Section 4.1.6 dialog-info+xml local and
|
|
||||||
remote elements by iterating through ringing channels and inserting
|
|
||||||
that info into NOTIFY packet sent to the endpoint.
|
|
||||||
@@ -1,5 +0,0 @@
|
|||||||
res_pjsip_dtmf_info: Hook flash
|
|
||||||
|
|
||||||
Adds recognition for application/
|
|
||||||
hook-flash as a hook flash event.
|
|
||||||
|
|
||||||
@@ -1,7 +0,0 @@
|
|||||||
Subject: res_pjsip_messaging
|
|
||||||
|
|
||||||
Implemented the new "to" parameter of the MessageSend()
|
|
||||||
dialplan application. This allows a user to specify
|
|
||||||
a complete SIP "To" header separate from the Request URI.
|
|
||||||
We now also accept a destination in the same format
|
|
||||||
as Dial()... PJSIP/number@endpoint
|
|
||||||
@@ -1,8 +0,0 @@
|
|||||||
Subject: res_rtp_asterisk
|
|
||||||
|
|
||||||
By default Asterisk reports the PJSIP version in all
|
|
||||||
STUN packets it sends.
|
|
||||||
|
|
||||||
This behaviour may not be desired in a production
|
|
||||||
environment and can now be disabled by setting the
|
|
||||||
stun_software_attribute option to 'no' in rtp.conf.
|
|
||||||
@@ -1,3 +0,0 @@
|
|||||||
Subject: app_voicemail
|
|
||||||
|
|
||||||
You can now customize the "beep" tone or omit it entirely.
|
|
||||||
@@ -1,6 +0,0 @@
|
|||||||
Subject: STIR/SHAKEN
|
|
||||||
|
|
||||||
The configuration option public_key_url in stir_shaken.conf
|
|
||||||
has been renamed to public_cert_url to better fit what it
|
|
||||||
contains. Only the name has changed - functionality is the
|
|
||||||
same.
|
|
||||||
@@ -1,8 +0,0 @@
|
|||||||
Subject: STIR/SHAKEN
|
|
||||||
|
|
||||||
STIR/SHAKEN originally needed an origid to be specified in
|
|
||||||
stir_shaken.conf under the certificate config object in
|
|
||||||
order to work. Now, one is automatically created by
|
|
||||||
generating a UUID, as recommended by RFC8588. Any origid
|
|
||||||
you have in your stir_shaken.conf will need to be removed
|
|
||||||
for the module to read in certificates.
|
|
||||||
Reference in New Issue
Block a user