The Real-Time Notification Details Need To Be Rounded Up
(Doc ID 1492300.1)
Last updated on AUGUST 01, 2022
Applies to:
Oracle Communications Network Charging and Control - Version 4.4.1 to 4.4.1 [Release 4.4]Information in this document applies to any platform.
Symptoms
If a Periodic Charge is configured to periodically credit the balance type 'X' and to set the expiry date of that balance to "now+ 30 days", this recharge generates a real-time notification, which is sent to the SLC via OSD.
The OSD message contains the new expiry date of the balance, in this example: 2012-08-30 12:09:49. However, the notification message is slightly delayed - the SLC receives it n seconds later, at 2012-07-31 12:11:01, rather than at 12:09:49
When the SLC receives the message, it works out that the balance will expiry in 29 days 23 hours 58 minutes and 48 seconds. Because the notification in ACS is configured to show "Elapsed time", and only the "days" part is configured to be shown, this is displayed in the notification as: "balance will expire in 29 days".
In 4.4.0 this is different from the behaviour of the pre-upgrade to NCC 4.4.0 software, which would say: "balance will expire in 30 days".
slee_acs debug:
Additionnal Note : When/If OSD is not available, e.g. due to replication issues, the information will be fetched directly from the Vouchers and Wallets Servers (VWS) through a Wallet Info (WI) message. This behavior is also exhibited when using a Wallet Info message to get the information - Issues like a late reply from the VWS will have the same effect.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |