Per Realm Accounting Control

You can enable or disable accounting for specific realms using the accounting-enable parameter, and enable the SBC to check the accounting setting on egress realms using the force-realm-accounting option.

Ingress Realm Accounting

The accounting-enable parameter on realm-config configuration element is enabled by default. The SBC’s SIP task checks whether this parameter is set to enabled or disabled, and sends records on that basis.

Note:

This configuration does not perform accounting for MESSAGE and REGISTER traffic.

This parameter is RTC supported.

Egress Realm Accounting Option

You can set the force-realm-accounting option in the sip-config to ensure the SBC performs accounting based on this configuration on the egress realm, regardless of the status on the ingress realm.

For session accounting, when you have enabled the force-realm-accounting option, the SBC checks the accounting-enable parameter on both the ingress and egress realms. If it is enabled on either realm, the SBC performs accounting for that session. If you have not enabled the force-realm-accounting option, the SBC only performs accounting for calls at the ingress realms that have accounting enabled.

When you set the force-realm-accounting option, the SBC also performs accounting for REGISTER and MESSAGE requests.

The SBC identifies the egress realm to check accounting for based on the next-hop parameter in the policy-attribute on the local-policy for the realm. The behavior differs depending on what next-hop is:
  • For a session agent (SA), the SBC checks the realm in the policy-attribute.

    If the policy-attribute does not include a realm, the SBC checks the realm-id or egress-realm-id associated with the SA. If both realm-id and egress-realm-id are specified, the SBC uses realm-id.

  • For a Local Route Table (LRT) that includes an SA or a combination of SAs and session agent groups (SAGs), the SBC checks the realm in the policy-attribute.

    If the policy-attribute does not include a realm, the CDR is not generated.

  • For a SAG or an LRT that includes only SAGs in the route, by default, CDRs are not generated when accounting-enable is disabled on the ingress realm, regardless of force-realm-accounting and the egress-realm accounting settings.

    However, when next-hop is a SAG or a SAG-only LRT, you can add the generate-cdr-for-sag option to the sip-config to enable the SBC to check the SAG-identified egress realm's accounting setting (this option does not apply when an LRT includes SAs only, or both SAGs and SAs.) When accounting-enable is disabled on the ingress realm and force-realm-accounting and generate-cdr-for-sag are added:

    • For a SAG:
      • The SBC checks the realm in the policy-attribute.
      • If there are multiple policy-attribute entries, the SBC uses the realm for the last one.

      • If the policy-attribute does not include a realm, the SBC checks the realm-id or egress-realm-id associated with the last SA in the SAG. If both realm-id and egress-realm-id are specified, the SBC uses realm-id.

        When using egress-realm-id, if there are multiple entries, the SBC uses the first one.

    • For a SAG-only LRT:
      • The SBC checks the egress-realm included in the LRT.
      • If there are multiple SAGs in the route, the SBC selects the realm from the last SAG in the route.
      • If the LRT does not include an egress-realm, the SBC checks the realm in the policy-attribute.
      • If there are multiple policy-attribute entries, the SBC uses the realm for the last one.
      • If the realm is specified in both egress-realm and policy-attribute, the SBC uses the egress-realm.

      • If the policy-attribute does not include a realm, the SBC checks the realm-id or egress-realm-id associated with the last SA in the SAG. If both realm-id and egress-realm-id are specified, the SBC uses realm-id.

        When using egress-realm-id, if there are multiple entries, the SBC uses the first one.

Use the following configuration syntax on the sip-config to set these options: 

ORACLE(sip-config)# options + force-realm-accounting + generate-cdr-for-sag

These options are RTC supported.