cdr.conf.sample 2.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. ;
  2. ; Asterisk Call Detail Record engine configuration
  3. ;
  4. ; CDR is Call Detail Record, which provides logging services via a variety of
  5. ; pluggable backend modules. Detailed call information can be recorded to
  6. ; databases, files, etc. Useful for billing, fraud prevention, compliance with
  7. ; Sarbanes-Oxley aka The Enron Act, QOS evaluations, and more.
  8. ;
  9. [general]
  10. ; Define whether or not to use CDR logging. Setting this to "no" will override
  11. ; any loading of backend CDR modules. Default is "yes".
  12. ;enable=yes
  13. ; Define the CDR batch mode, where instead of posting the CDR at the end of
  14. ; every call, the data will be stored in a buffer to help alleviate load on the
  15. ; asterisk server. Default is "no".
  16. ;
  17. ; WARNING WARNING WARNING
  18. ; Use of batch mode may result in data loss after unsafe asterisk termination
  19. ; ie. software crash, power failure, kill -9, etc.
  20. ; WARNING WARNING WARNING
  21. ;
  22. ;batch=no
  23. ; Define the maximum number of CDRs to accumulate in the buffer before posting
  24. ; them to the backend engines. 'batch' must be set to 'yes'. Default is 100.
  25. ;size=100
  26. ; Define the maximum time to accumulate CDRs in the buffer before posting them
  27. ; to the backend engines. If this time limit is reached, then it will post the
  28. ; records, regardless of the value defined for 'size'. 'batch' must be set to
  29. ; 'yes'. Note that time is in seconds. Default is 300 (5 minutes).
  30. ;time=300
  31. ; The CDR engine uses the internal asterisk scheduler to determine when to post
  32. ; records. Posting can either occure inside the scheduler thread, or a new
  33. ; thread can be spawned for the submission of every batch. For small batches,
  34. ; it might be acceptable to just use the scheduler thread, so set this to "yes".
  35. ; For large batches, say anything over size=10, a new thread is recommended, so
  36. ; set this to "no". Default is "no".
  37. ;scheduleronly=no
  38. ; When shutting down asterisk, you can block until the CDRs are submitted. If
  39. ; you don't, then data will likely be lost. You can always check the size of
  40. ; the CDR batch buffer with the CLI "cdr status" command. To enable blocking on
  41. ; submission of CDR data during asterisk shutdown, set this to "yes". Default
  42. ; is "yes".
  43. ;safeshutdown=yes