[asterisk-commits] russell: branch 1.8 r281294 - /branches/1.8/configs/cdr.conf.sample

[SVN commits to the Asterisk project]

Author: russell
Date: Mon Aug  9 07:14:34 2010
New Revision: 281294

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=281294
Log:
Reorder some options in cdr.conf.sample.

Put all of the options that affect the contents of CDRs together, instead
of having the batch mode options in the middle of them.

Modified:
    branches/1.8/configs/cdr.conf.sample

Modified: branches/1.8/configs/cdr.conf.sample
URL: http://svnview.digium.com/svn/asterisk/branches/1.8/configs/cdr.conf.sample?view=diff&rev=281294&r1=281293&r2=281294
==============================================================================
--- branches/1.8/configs/cdr.conf.sample (original)
+++ branches/1.8/configs/cdr.conf.sample Mon Aug  9 07:14:34 2010
@@ -28,6 +28,21 @@
 ; output, as they have the B side channel as their source channel, and no destination 
 ; channel.)
 ;unanswered = no
+
+; Normally, CDR's are not closed out until after all extensions are finished
+; executing.  By enabling this option, the CDR will be ended before executing
+; the "h" extension so that CDR values such as "end" and "billsec" may be
+; retrieved inside of of this extension.
+;endbeforehexten=no
+
+; Normally, the 'billsec' field logged to the backends (text files or databases)
+; is simply the end time (hangup time) minus the answer time in seconds. Internally,
+; asterisk stores the time in terms of microseconds and seconds. By setting
+; initiatedseconds to 'yes', you can force asterisk to report any seconds
+; that were initiated (a sort of round up method). Technically, this is
+; when the microsecond part of the end time is greater than the microsecond
+; part of the answer time, then the billsec time is incremented one second.
+;initiatedseconds=no
 
 ; Define the CDR batch mode, where instead of posting the CDR at the end of
 ; every call, the data will be stored in a buffer to help alleviate load on the
@@ -64,21 +79,6 @@
 ; submission of CDR data during asterisk shutdown, set this to "yes".  Default
 ; is "yes".
 ;safeshutdown=yes
-
-; Normally, CDR's are not closed out until after all extensions are finished
-; executing.  By enabling this option, the CDR will be ended before executing
-; the "h" extension so that CDR values such as "end" and "billsec" may be
-; retrieved inside of of this extension.
-;endbeforehexten=no
-
-; Normally, the 'billsec' field logged to the backends (text files or databases)
-; is simply the end time (hangup time) minus the answer time in seconds. Internally,
-; asterisk stores the time in terms of microseconds and seconds. By setting
-; initiatedseconds to 'yes', you can force asterisk to report any seconds
-; that were initiated (a sort of round up method). Technically, this is
-; when the microsecond part of the end time is greater than the microsecond
-; part of the answer time, then the billsec time is incremented one second.
-;initiatedseconds=no
 
 ;
 ;