summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorLeif Madsen <leif@leifmadsen.com>2010-06-03 18:53:24 +0000
committerLeif Madsen <leif@leifmadsen.com>2010-06-03 18:53:24 +0000
commitdfa82e0852fc98982b252ea8078b9ea82ff1abb4 (patch)
tree31ceddbeb79c5fba93f758ddfdf425517f2d93d2 /CHANGES
parent6ab2173c978231ba154e8f414e51529d7bb0c3c6 (diff)
Update UPGRADE.txt and CHANGE for CDR functionality changes.
Updated the UPGRADE.txt and CHANGES file stating that CDR records will not be explicity written unless cdr.conf exists and is configured. (closes issue #17373) Reported by: wdoekes Tested by: pabelanger git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@267624 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES6
1 files changed, 6 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 49ad4d1e4..ac145d4bf 100644
--- a/CHANGES
+++ b/CHANGES
@@ -637,6 +637,12 @@ Miscellaneous
instead of the /var/run/asterisk.pid where it used to be. This will make
installs as non-root easier to manage.
+CDR
+---
+
+* The cdr.conf file must exist and be correctly programmed in order for CDR records to
+ be written; they will no longer be explicitly written.
+
Asterisk Manager Interface
--------------------------
* When using the AMI over HTTP, you can now include a 'SuppressEvents' header (with