mirror of
https://github.com/asterisk/asterisk.git
synced 2025-10-12 15:45:18 +00:00
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/branches/1.8@281294 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
@@ -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)
|
||||
|
Reference in New Issue
Block a user