===
==============================================================================
+------------------------------------------------------------------------------
+--- Functionality changes from Asterisk 16.29.0 to Asterisk 16.30.0 ----------
+------------------------------------------------------------------------------
+
+cdr
+------------------
+ * Two new options have been added which allow
+ bridging and dial state changes to be ignored
+ in CDRs, which can be useful if a single CDR
+ is desired for a channel.
+
+res_pjsip
+------------------
+ * Added options "security_negotiation" and "security_mechanisms" to pjsip
+ endpoints and registrations. "security_negotiation" can be set to "no" (default)
+ or "mediasec", and "security_mechanisms" can be a list of comma-separated
+ security_mechanisms in the form defined by RFC 3329 section 2.2.
+
+ * A new option named "all_codecs_on_empty_reinvite" has been added to the
+ global section. When this option is enabled, on reception of a re-INVITE
+ without SDP, Asterisk will send an SDP offer in the 200 OK response containing
+ all configured codecs on the endpoint, instead of simply those that have
+ already been negotiated. RFC 3261 specifies this as a SHOULD requirement.
+ The default value is "off".
+
+res_tonedetect
+------------------
+ * The TONE_DETECT function now supports
+ detection of audible ringback tone
+ using the p option.
+
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 16.28.0 to Asterisk 16.29.0 ----------
------------------------------------------------------------------------------
===
===========================================================
+------------------------------------------------------------------------------
+--- Functionality changes from Asterisk 16.29.0 to Asterisk 16.30.0 ----------
+------------------------------------------------------------------------------
+
+AMI (Asterisk Manager Interface)
+------------------
+ * Previously, GetConfig and UpdateConfig were able to access files outside of
+ the Asterisk configuration directory. Now this access is put behind the
+ live_dangerously configuration option in asterisk.conf, which is disabled by
+ default. If access to configuration files outside of the Asterisk configuation
+ directory is required via AMI, then the live_dangerously configuration option
+ must be set to yes.
+
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 16.28.0 to Asterisk 16.29.0 ----------
------------------------------------------------------------------------------
+++ /dev/null
-Subject: cdr
-
-Two new options have been added which allow
-bridging and dial state changes to be ignored
-in CDRs, which can be useful if a single CDR
-is desired for a channel.
+++ /dev/null
-Subject: res_pjsip
-
-A new option named "all_codecs_on_empty_reinvite" has been added to the
-global section. When this option is enabled, on reception of a re-INVITE
-without SDP, Asterisk will send an SDP offer in the 200 OK response containing
-all configured codecs on the endpoint, instead of simply those that have
-already been negotiated. RFC 3261 specifies this as a SHOULD requirement.
-The default value is "off".
\ No newline at end of file
+++ /dev/null
-Subject: res_pjsip
-
-Added options "security_negotiation" and "security_mechanisms" to pjsip
-endpoints and registrations. "security_negotiation" can be set to "no" (default)
-or "mediasec", and "security_mechanisms" can be a list of comma-separated
-security_mechanisms in the form defined by RFC 3329 section 2.2.
+++ /dev/null
-Subject: res_tonedetect
-
-The TONE_DETECT function now supports
-detection of audible ringback tone
-using the p option.
+++ /dev/null
-Subject: AMI (Asterisk Manager Interface)
-
-Previously, GetConfig and UpdateConfig were able to access files outside of
-the Asterisk configuration directory. Now this access is put behind the
-live_dangerously configuration option in asterisk.conf, which is disabled by
-default. If access to configuration files outside of the Asterisk configuation
-directory is required via AMI, then the live_dangerously configuration option
-must be set to yes.