diff --git a/doc/CHANGES-staging/README.md b/doc/CHANGES-staging/README.md index 8a2407f95a21d998efe6543ef2d1ec44ece3a5c6..8fc51bce282232e27b87c43392423be8a2046b65 100644 --- a/doc/CHANGES-staging/README.md +++ b/doc/CHANGES-staging/README.md @@ -9,10 +9,10 @@ it probably should. If there are multiple items that need documenting, you can add multiple files, each with their own description. If the message is going to be the same for each subject, then you can add multiple subject headers to one file. The "Subject: xxx" line is case sensitive! For example, if you are making -a change to PJSIP, then you might add the file "res_pjsip_my_cool_feature" to -this directory, with a short description of what it does. If you are adding -multiple entries, they should be done in the same commit to avoid merge -conflicts. Here's an example: +a change to PJSIP, then you might add the file "res_pjsip_my_cool_feature.txt" to +this directory, with a short description of what it does. The files must have +the ".txt" suffix. If you are adding multiple entries, they should be done in +the same commit to avoid merge conflicts. Here's an example: > Subject: res_pjsip > Subject: Core diff --git a/doc/CHANGES-staging/hide_messaging_ami_events.txt b/doc/CHANGES-staging/hide_messaging_ami_events.txt new file mode 100644 index 0000000000000000000000000000000000000000..0afbeecdf74790725771ad568be2fcfcf893e38d --- /dev/null +++ b/doc/CHANGES-staging/hide_messaging_ami_events.txt @@ -0,0 +1,11 @@ +Subject: Messaging + +In order to reduce the amount of AMI and ARI events generated, +the global "Message/ast_msg_queue" channel can be set to suppress +it's normal channel housekeeping events such as "Newexten", +"VarSet", etc. This can greatly reduce load on the manager +and ARI applications when the Digium Phone Module for Asterisk +is in use. To enable, set "hide_messaging_ami_events" in +asterisk.conf to "yes" In Asterisk versions <18, the default +is "no" preserving existing behavior. Beginning with +Asterisk 18, the option will default to "yes". diff --git a/doc/CHANGES-staging/res_fax_negotiate_both b/doc/CHANGES-staging/res_fax_negotiate_both deleted file mode 100644 index 73be756028fd34eec3e9603333ff2edf09c550f0..0000000000000000000000000000000000000000 --- a/doc/CHANGES-staging/res_fax_negotiate_both +++ /dev/null @@ -1,7 +0,0 @@ -Subject: res_fax - -Added configuration option "negotiate_both". This option is only used -when a gateway is enabled, and a v21 preamble is detected. If this option -is enabled, once a preamble is detected Asterisk will initiate negotiation -requests to both T.38 enabled endpoint versus waiting, and forwarding a -request from an initiating endpoint. Defaults to disabled. diff --git a/doc/UPGRADE-staging/README.md b/doc/UPGRADE-staging/README.md index 81471617a4cf7bfb442a2611d959d6803748dce2..21cbe78c590945f6ca034f47dd1766ee76feaf2b 100644 --- a/doc/UPGRADE-staging/README.md +++ b/doc/UPGRADE-staging/README.md @@ -9,9 +9,10 @@ are multiple items that need documenting, you can add multiple files, each with their own description. If the message is going to be the same for each subject, then you can add multiple subject headers to one file. The "Subject: xxx" line is case sensitive! For example, if you are making a change to PJSIP, then you -might add the file "res_pjsip_my_cool_feature" to this directory, with a short -description of what it does. If you are adding multiple entries, they should be -done in the same commit to avoid merge conflicts. Here's an example: +might add the file "res_pjsip_my_cool_feature.txt" to this directory, with a +short description of what it does. The files must have the ".txt" suffix. +If you are adding multiple entries, they should be done in the same commit +to avoid merge conflicts. Here's an example: > Subject: res_pjsip > Subject: Core