WLC Buckets Do Not Auto-Expire
(Doc ID 2045729.1)
Last updated on JULY 21, 2017
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.
The Wallet Life Cycle (WLC) feature of Oracle Communication Network Charging and Control (OCNCC) makes use of Voucher and Wallet Server (VWS) buckets to store the current state of a given subscriber's wallet.
WLC is handled through a bucket which has its own expiry set to the end of a grace period. A grace state provides limited functionality to a wallet which would otherwise be in the terminated state. A wallet can be in more than one grace period. Its value determines the state of the subscriber. While the subscriber is active or inactive subscription, this value is set to -1 to represent the fact that there is no grace. This is an internal value that cannot be changed.
A problem exists when the system is set up to not delete expired buckets that have a negative value automatically to make sure that any negative bucket is still present so when a recharge or anything happens, the negative value is not lost (as this is effectively a loss in revenue for operators).
Unfortunately, with the non-monetary WLC bucket value being set to -1, this means that only a 'manual' interaction will force the wlc bucket expiry.
In the debug you will see the following message:
2014/03/14 11:22:51 ccsWLCVWARS.cc 42  ccsWLCPlugin Wallet Type not defined in the cookies, exiting.
Have an account with a WLC bucket with a -1 value and an expiry in the past. Do not trigger it manually and leave it to the groveller find it and pass it to VWARS for processing.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document