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

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

UPGRADE.txt

@@ -1,6 +1,6 @@
 ===========================================================
 ===
-=== Information for upgrading between Asterisk 1.6 versions
+=== Information for upgrading between Asterisk versions
 ===
 === These files document all the changes that MUST be taken
 === into account when upgrading between the Asterisk
@@ -180,6 +180,9 @@ From 1.6.1 to 1.6.2:
   that would end up being interpreted as a bug once Asterisk started removing 
   the contacts from a user list.
 
+* The cdr.conf file must exist and be configured correctly in order for CDR
+  records to be written.
+
 From 1.6.0.1 to 1.6.1:
 
 * The ast_agi_register_multiple() and ast_agi_unregister_multiple()