Buckets from Different Balance Types in a Balance Type Cascade are not Charged if they Expire Mid-Call (Doc ID 2118336.1)

Last updated on MARCH 25, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.2 to 5.0.3 [Release 5.0]
Information in this document applies to any platform.

Symptoms

On Oracle Communications Network Charging and Control 5.0.2 and 5.0.3, a problem exists when a Cross Balance Type cascade consists of different balance types, a problem exists if a bucket from a different balance type expires mid-call.

Instead of the potions of the call being commited relative to the buckets/balances types which the reservations were placed, the entire cost of the call ends up being charged from the unexpired bucket.

As an example, assume the following wallet:

The call starts and $3 is reserved against the Promotional Cash bucket and granted to the caller.  After 3 minutes, a request comes in to extend the reservation but the Promotional Cash balance is expired so the next reservation is placed against the General Cash bucket.

The call ends after 5 minutes but instead of $3 being commited against the Promotional Cash bucket and $2 commited against the General Cash bucket, the entire $5 is commited against the General Cash bucket.

Changes

Addition of new Balance Type Cascades.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms