Limiting REGISTER CDR Generation

The Oracle Communications Unified Session Manager allows the user to generate RADIUS CDRs for REGISTER events via configuration. Large networks, however, can generate an inordinate volume of CDRs. So the Oracle Communications Unified Session Manager also allows the user to reduce REGISTER CDR generation by filtering out some of the messages it sends.

When the user enables accounting with the generate-events parameter, the Oracle Communications Unified Session Manager can generate CDRs for the following register and/or local register events:

Initial REGISTER
REGISTER refresh
REGISTER update
de-REGISTER

Depending on the event, the system generates per-contact start, interim and/or stop CDRs. With no other configuration, the system generates the appropriate CDRs for all of these events.

The user can prevent the system from issuing some CDR via an account-config option that filters, as described below, and sets a timer that restarts the CDR suppression window. Use the syntax below to set this register-cdr-interval option with an expiry timer value of 43200 in minutes (30 days), and limit the number of generated CDRs as described below.

(account-config)#options +register-cdr-interval=43200

When configured with this option, the Oracle Communications Unified Session Manager limits the generation of CDRs for each user as follows:

Send a START CDR for first Register message (for first contact).
Don't send CDRs until the user specified time period expires. After it expires, when a Registration message causes a 'START' or 'INTERIM' CDR event to occur, send it. Then, re-set the time value. Applicable 'START' CDR events include:
- Add new contact
- Replace contact
- Overwrite contact

The applicable 'INTERIM' CDR event is a Refresh Contact.

The generate-event parameter must also be set to register.