BCD Fails to Respect CREDIT_LIMIT_EXCEEDED(26) RATING_STATUS from BRM
(Doc ID 2412990.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On Oracle Communications Convergent Charging Controller (OC3C of 3C) 18.104.22.168 to 22.214.171.124, there is an issue with the Billing and Revenue Management (BRM) Charging Driver (BCD) where BCD does not respect a CREDIT_LIMIT_EXCEEDED(26) RATING_STATUS response from BRM and will attempt to reserve further funds from BRM in a subsequent reservation.
This causes an alarm to be logged on the BRM servers as the expectation by BRM is that the units granted with CREDIT_LIMIT_EXCEEDED(26) set are the last units that can be granted and the next message from BCD should be a STOP_ACCOUNTING message to commit/end the session.
The current behavior in BCD is as long as any units are returned, that more can be requested regardless of what the RATING_STATUS is set to. This affects both initial and non-initial PCM_OP_BILL_DEBUT opcode responses.
When BCD attempts to reserve more funds after the previous CREDIT_LIMIT_EXCEEDED(26) response from BRM, BRM will respond with 0 units and RATING_STATUS set to CREDIT_LIMIT_EXCEEDED(26) which BCD will correctly handle and terminate the call. This also prevents any low balance based processing from working.
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