Recording/CDR Settings


Here you can configure CDR and recording settings.


  • Expand the menu General under "Settings".
  • From the expanded General menu, click on Recording/CDR.

Explanation of the Settings

  • Default CDR listing size: A Call Detail Record (CDR) is a record that is produced by the system and contains the details of calls that have terminated on the system. CDRs include the date and time the call started, the number that made the call, the number that received the call, and the call duration. Use this field to limit the number of CDRs that will be displayed in the web interface (CDRs can be memory consuming). The default is 30 CDRs.
  • Keep CDR Duration: This setting defines the length of time CDRs are kept on the file system. CDRs can consume large amounts of disk space, so be careful when setting this field. If too many CDRs are on a busy system, the system will not start. The default is 7 days. The duration can be expressed in various time units:
    Seconds: Enter an s after the number (e.g., 60s for 60 seconds)
    Minutes: Enter an m after the number (e.g., 60m for 60 minutes)
    Hours: Enter an h after the number (e.g., 24h for 24 hours)
    Days: Enter a d after the number (e.g., 7d for 7 days)
  • Maximum number of CDRs (per type): This setting allows the admin to control the number of CDRs, according to type, that will be retained on the system. The CDRs are classified according to extension, trunk, and ivr and are stored in the cdre, cdrt, and cdri folders, respectively.
  • CDR URL: The CDR URL field controls where CDRs are written. The system can write CDRs to a CSV file, an email address, a server address, or to a SOAP destination. To populate the CDR URL field, use the syntax shown below. CDRs can be viewed only after they have been collected and organized through an external call accounting application. The detail information about CDR can be found on the CDR page.
  • Record Location: This field determines where system-initiated recordings will be stored on the system. By default, $r/$o/$a/$d-$t-$i-$n.wav is the string used in this field. If you wanted to set an absolute path for the recordings, you would use something like /tmp/test/$d-$t-$i.wav. For more information about recording calls and how to create a string for the Record Location field, see Record Location.
  • Compress Recordings: The system will compress recordings when this setting is enabled. Otherwise, recordings will be saved as 16 bits/sample.
  • Maximum Duration of Call Recording: This setting allows you to establish an upper limit on call recordings, which is important since large recordings can cause problems with system performance. To further conserve disk space, you can limit the number of messages that can be stored in a user’s voicemail box (see the Voicemail Size setting in Domains).
  • Delete the call recording files along with the CDR: Whenever the CDR related to that call is deleted, the call recording will also be deleted. So, if the CDR gets deleted based on the time limit (7d, 1d, etc.) that has been set in the Keep CDR Duration setting, then the recording will be deleted along with it. (This setting has been removed in version 62.0 and above)

SPAM Detection:

What is a nuisance in email for many years recently has become a problem also for telephone system: Unwanted calls. Such calls do not  In order to address the problem, the PBX offers several mechanisms depending on the type of call. Before taking any action, the PBX needs to determine if a call is a suspected SPAM call. For that the PBX has the following rules:

  • Anonymous calls are always considered SPAM calls;
  • Internal calls from another extension are never considered SPAM calls (even though sometimes it could make sense);
  • For tagging calls that have a caller-ID there are several methods: You can use TrueCNAM or Tellows as external SPAM provider or you can use the address book to mark a specific caller-ID for blocking.

For calls directly to an extension, the PBX offers the following options:

  • No special treatment means that the call is processed normally.
  • Reject call means that the call gets outright rejected.
  • Send to mailbox sends the call to the mailbox.
  • Pretend to be busy applies the rules for a busy extension, which could for example trigger redirection on busy.
  • Ask for name triggers the call screening process where the caller first needs to leave the name. This name will be read out to the extension before that user can make a decision on how to proceed.
  • You can also select that the screening process should be performed for all calls, even if they are not considered SPAM.

For calls to the ACD and to the hunt group you can specify a destination where calls should be redirected. This destination can be another ACD or hunt group, a mailbox, an auto attendant or anything else.