How to Implement Diameter Result-Code DIAMETER_CREDIT_LIMIT_REACHED
Last updated on DECEMBER 14, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11.2.0]
Information in this document applies to any platform.
On : 18.104.22.168.2 version, Diameter Gateway
When there is a failure while processing diameter result code, there is no unique result code returned specific to that scenario.
If there is no prepaid balance then Usage response is reporting the error as "credit ceiling reached". But diameter gateway CCA reply will have result code as DIAMETER_RATING_FAILED(5031)
Same result code is returned if the service is inactive or no active products to rate the event.
For example, there is no balance and initiate request is triggered, the usage response is like below which is having 3 reasons. (NO_RATED_QUANTITY, CREDIT_CEILING_BREACH, FINAL_UNIT_INDICATOR). In this case the diameter result code is 5031 (DIAMETER_RATING_FAILED), but the expected result code is DIAMETER_CREDIT_LIMIT_REACHED.
There is some logic required to be implemented at NCC based on the specific failure here. How can we achieve this?
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