Wrong Behaviour Of Validity-Time For ExtensionContext.setValidity() Method
(Doc ID 2496659.1)
Last updated on FEBRUARY 04, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
In ECE PreRating Extensions, a custom code is written in such a way that for every Updates deliver logic:
It looks like Validity-Time has been set once for whole Diameter session not for each transaction (Credit-Control-Request /CCA) and decrease with value of time spend between requests.
Global ece Validity-Time set via jconsole in ECE configurations is 3600.
Note that Update reports that usage of 100% on Granted Quotas always. This behaviour does not fit in Diameter Request for Comments(RFC) 4006
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