dect
/
asterisk
Archived
13
0
Fork 0
Code Releases Activity

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: http://svn.digium.com/svn/asterisk/trunk@267624 f38db490-d61c-443f-a65b-d21fe96a405b
This commit is contained in:
lmadsen 2010-06-03 18:53:24 +00:00
parent 3dab894d2a
commit 6a72266cbe
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CHANGES
View File

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

5
UPGRADE.txt
View File

@ -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()