BCD Rating Status Profile Tag Stored Incorrectly
Last updated on FEBRUARY 20, 2018
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) Applications, 6.0.1 version, BRM Charging Driver(BCD) appears to store the Rating Status returned from Oracle Communications Billing and Revenue Management(BRM) incorrectly, making result comparisons difficult.
This is observed while testing the branching on a non-zero Rating Status returned from BRM.
Consider the below sample response field:
It is expected that BCD should store the Rating Status returned from BRM correctly.
The issue can be reproduced at will with the following steps:
1) Set up BCD integration as per usual setup for voice or data charging.
2) Configure simple UATB control plan for performing a call/session.
3) Trigger subscriber that will receive a non-zero rating status - e.g. insufficient funds (26).
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