Per Realm Accounting Control

You can enable or disable accounting control for specific ingress realms using the accounting-enable parameter. This parameter is enabled by default.

The SBC’s SIP and H.323 tasks check whether this parameter is set to enabled or disabled, and sends records on that basis.

Note:

This realm configuration does not trigger accounting of MESSAGE and REGISTER traffic.

Egress Realm Accounting Option

You can also set the force-realm-accounting option in the sip-config to ensure the SBC performs accounting based on this configuration on the egress realm.

For session accounting, the SBC checks the realm accounting configuration on both the ingress and egress realms. If the accounting configuration is enabled on either realm, and you have enabled the sip-config option, the SBC performs accounting for that session. If you have not enabled the sip-config option, the SBC only performs accounting for calls at the ingress realms that have accounting enabled.

This option also causes the SBC to perform accounting for REGISTER and MESSAGE requests. For this purpose, the SBC first checks whether you have configured the sip-config option. If set, the SBC checks the realm accounting configuration on the ingress and egress realms. If you have configured realm accounting configuration on either realm, the SBC performs accounting on these messages.

The syntax for this option follows.

ORACLE(sip-config)# options + force-realm-accounting

Both the force-realm-accounting option and the accounting-enable parameter are RTC supported.