Merged revisions 281294 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r281294 | russell | 2010-08-09 07:14:34 -0500 (Mon, 09 Aug 2010) | 5 lines
  
  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.
........


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@281295 65c4cc65-6c06-0410-ace0-fbb531ad65f3

1 files changed, 15 insertions, 15 deletions

diff --git a/configs/cdr.conf.sample b/configs/cdr.conf.sample
index 3866ab1fa..d78a065a1 100644
--- a/configs/cdr.conf.sample
+++ b/configs/cdr.conf.sample
@@ -29,6 +29,21 @@
 ; 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
 ; asterisk server.  Default is "no".
@@ -65,21 +80,6 @@
 ; 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
-
 ;
 ;
 ; CHOOSING A CDR "BACKEND"  (what kind of output to generate)