RADIUS CDR Content Control

The OCSBC’s RADIUS support has been enhanced so that you can limit the size of RADIUS CDRs. The OCSBC’s RADIUS accounting provides a detailed set of records that can contain, for example, multiple media flow descriptions for forked calls that can contain multiple sets of media and QoS attributes. While the level of detail might be required for some networks, in others the large CDRs generated to reflect that level of granularity can cause issues for the application receiving the records.

You can use the following enhancements to control the size of the RADIUS CDRs your OCSBC produces:

Duplicate RADIUS attribute prevention—Using this feature, you can configure the OCSBC to send only one set of RADIUS attributes in CDR for a forked call. (When a forked SIP INVITE contains media information, media and QoS attributes can potentially be duplicated.)
RADIUS attribute selection—You can set a list of the Oracle VSAs you want included in a RADIUS CDR, and the OCSBC will exclude the others from the record; standard attributes are always included. You specify attributes using their unique identifier in a comma-delimited list, and you can list them in any order. However, entering an invalid range disables this feature.
The OCSBC excludes attributes from the records in which they are already defined. If an attributes only appears in a Stop record, then it will be deleted from Stop records.

The configuration provides a mechanism to make entries flexible and easy.

ACLI Instructions and Examples

You enable these enhancements using two parameters in the accounting configuration.

Accessing the Accounting Configuration

To access the accounting configuration:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
```
Type session-router and press Enter.
```
ORACLE(configure)# session-router
```
Type account-config and press Enter.
```
ORACLE(session-router)# account-config
```
From this point, you can reach the individual parameters for duplicate RADIUS attribute prevention and for RADIUS attribute selection.

Preventing Duplicate RADIUS Attributes

To enable duplicate RADIUS attribute prevention:

prevent-duplicate-attrs—Enable this parameter to prevent the OCSBC from duplicating attributes in the accounting records it generates. This duplication can be caused, for example, by multiple media sessions within the context of a call. Retaining the default (disabled) allows the OCSBC to include duplicate attributes in RADIUS, Diameter and Local accounting records. This can result in attribute placement and counts that are less consistent.
```
ORACLE(account-config)# prevent-duplicate-attrs enabled
```
Save and activate your configuration.

RADIUS Attribute Selection

You enter the list of VSAs that you want included as a comma-delimited list. There are special entry types you can use in the comma-delimited list to set ranges and make entries easier:

X- — Where X is a VSA identifier, the OCSBC will include all attributes with an identifier equal to or greater than X.
-X — Where X is a VSA identifier, the OCSBC will include all attributes with an identifier equal to or less than X.
- — Use the minus sign (-) alone when you want to turn off attribute selection, including all VSAs in the CDR.
To enter a list of RADIUS attributes to include in a CDR:

vsa-id-range—Enter a comma-delimited list that represents the VSA you want to appear in the RADIUS CDR. There is no default for this parameter.
Do not use <Spaces> when typing in your comma-delimited list.
```
ORACLE(account-config)# vsa-id-range -5,7,10-
```
This entry specifies that CDRs contain VSA with identifiers equal to and less than 5, VSA 7, and VSAs with identifiers equal to and greater than 10.

Limit this list to accounting VSAs. For example, VSA 254 is an authentication VSA, so it should not be included in the range. The system generates validate-config errors if your range includes VSAs that are not accounting VSAs.
Save and activate your configuration.