kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-09-06 04:30:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge "doc: Fix CHANGES entries to have .txt suffix and update READMEs" into 13

Browse Source
This commit is contained in:
George Joseph
2020-02-13 08:30:13 -06:00
committed by Gerrit Code Review
parent ea1f318534 74d0244dc3
commit 796680cc57
4 changed files with 19 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/CHANGES-staging/README.md
View File

@@ -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 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 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 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 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. If you are adding this directory, with a short description of what it does. The files must have
multiple entries, they should be done in the same commit to avoid merge the ".txt" suffix. If you are adding multiple entries, they should be done in
conflicts. Here's an example: the same commit to avoid merge conflicts. Here's an example:
> Subject: res_pjsip > Subject: res_pjsip
> Subject: Core > Subject: Core

11
doc/CHANGES-staging/hide_messaging_ami_events.txt Normal file
View File

@@ -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".

7
doc/CHANGES-staging/res_fax_negotiate_both
View File

@@ -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.

7
doc/UPGRADE-staging/README.md
View File

@@ -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, 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 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 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 might add the file "res_pjsip_my_cool_feature.txt" to this directory, with a
description of what it does. If you are adding multiple entries, they should be short description of what it does. The files must have the ".txt" suffix.
done in the same commit to avoid merge conflicts. Here's an example: 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: res_pjsip
> Subject: Core > Subject: Core