Voucher Recharge Node Treats Unavailable Batch Voucher As Abandoned
(Doc ID 2388445.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communications Convergent Charging Controller(OC3C) 6.0.1 version, it is observed that the Voucher Recharge(VR) Node treats unavailable batch voucher as abandoned.
ie when using the VR node, a voucher from an unavailable batch is treated as abandoned as shown in the belos sample logs:
It would be good to have an exit added for Unavailable, but failing that, a configuration option for the VR Node to tell it which exit to use. For example, in this particular case the user don't use voucher scenarios, so they could use that to indicate that the voucher is unavailable and set the ACS CDR details accordingly.
The issue can be reproduced at will with the following steps:
1. Use a Voucher Recharge Node to process a voucher from an unavailable batch
2. Check the slee_acs log and verify that the VR node processing fails and takes the Abandon.Branch exit.
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