The Call Detail Recording (CDR) and media statistics reporting framework is embedded in the CDR report and made available at the end of the call. The reporting framework provides a RADIUS interface to send CDR messages to the third-party RADIUS Server. If the interface does not exist or the RADIUS interface is nonfunctional because of network outage or a maintenance window, Avaya SBC saves the CDR records locally. Avaya SBC periodically sends data to the CDR adjunct using SFTP. You can configure the frequency when Avaya SBC sends data to the CDR adjunct.
The following types of configurations are available:
The CDR adjunct is configured through the management interface.
Data is pushed from Avaya SBC to SFTP. In this case, CDR adjunct and Avaya SBC validate each other based on a shared username and password.
Avaya SBC raises a CDR alarm if /archive/cdr usage crosses the 70% threshold. The /archive/cdr directory can use 50% of the /archive/ partition.
For example, if the /archive/ size is 20 GB, /archive/cdr/ can use up to 10 GB. Avaya SBC raises a CDR alarm if /archive/cdr/ uses more than 7 GB space.
Avaya SBC begins purging CDR when /archive/cdr/ usage crosses the 80% threshold. For example, if /archive/cdr/ usage crosses the 8 GB threshold, Avaya SBC deletes files older than 3 days.
RADIUS interface is used to send the CDR and media statistics event messages to the RADIUS Server. Vendor Specific Attributes are used to include CDR information that is not available with the standard RADIUS session information. Third party RADIUS servers need to upload the RADIUS dictionary from /usr/local/ipcs/etc/rdictionary/dictionary.avayasbce to analyze the CDR messages from Avaya SBC.
CDR data can be stored on locally. To store locally, in the CDR Support field, select CDR Adjunct, but do not configure the CDR adjunct in the section.
