asterisk

History

Mark Murawski b4347c4861 logger: Console sessions will now respect logger.conf dateformat= option The 'core' console (ie: asterisk -c) does read logger.conf and does use the dateformat= option. Whereas 'remote' consoles (ie: asterisk -r -T) does not read logger.conf and uses a hard coded dateformat option for printing received verbose messages: main/logger.c: static char dateformat[256] = "%b %e %T" This change will load logger.conf for each remote console session and use the dateformat= option to set the per-line timestamp for verbose messages Change-Id: I3ea10990dbd920e9f7ce8ff771bc65aa7f4ea8c1 ASTERISK-25358: #close Reported-by: Igor Liferenko		5 years ago
..
README.md	doc: Fix CHANGES entries to have .txt suffix and update READMEs	6 years ago
app_confbridge.txt	app_confbridge/bridge_softmix: Add ability to force estimated bitrate	6 years ago
app_transferprotocol.txt	chan_pjsip, app_transfer: Add TRANSFERSTATUSPROTOCOL variable	5 years ago
chan_iax2.txt	chan_iax2.c: Require secret and auth method if encryption is enabled	5 years ago
func_odbc_ARGC_minargs.txt	func_odbc: Introduce minargs config and expose ARGC in addition to ARGn.	5 years ago
logger_category.txt	Logging: Add debug logging categories	6 years ago
logger_dateformat.txt	logger: Console sessions will now respect logger.conf dateformat= option	5 years ago
logger_format.txt	logger.c: Added a new log formatter called "plain"	6 years ago
media_cache_cachedir.txt	Introduce astcachedir, to be used for temporary bucket files	6 years ago
mixmonitor_manager_events.txt	app_mixmonitor: Add AMI events MixMonitorStart, -Stop and -Mute.	5 years ago
pjsip_send_session_refresh.txt	chan_pjsip: disallow PJSIP_SEND_SESSION_REFRESH pre-answer execution	6 years ago
pjsip_transport_partial_reload.txt	res_pjsip: Add support for partial transport reload.	5 years ago
srtp_replay_protection.txt	rtp: Enable srtp replay protection	5 years ago
voicemail_early_media.txt	voicemail: add option 'e' to play greetings as early media	6 years ago

README.md

DO NOT REMOVE THIS FILE!

The only files that should be added to this directory are ones that will be used by the release script to update the CHANGES file automatically. The only time that it is necessary to add something to the CHANGES-staging directory is if you are either adding a new feature to Asterisk or adding new functionality to an existing feature. The file does not need to have a meaningful name, but 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.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

Here's a pretty good description of my new feature that explains exactly what it does and how to use it.

Here's a master-only example:

Subject: res_ari Master-Only: True

This change will only go into the master branch. The "Master-Only" header will never be in a change not in master.

Note that the second subject has another header: "Master-Only". Changes that go into the master branch and ONLY the master branch are the only ones that should have this header. Also, the value can only be "true" or "True". The "Master-Only" part of the header IS case-sensitive, however!

For more information, check out the wiki page: https://wiki.asterisk.org/wiki/display/AST/CHANGES+and+UPGRADE.txt