Value Of Validity Time In CCA Is Varying
(Doc ID 2621566.1)
Last updated on FEBRUARY 11, 2020
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.9.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Elastic Charging Engine (ECE), 11.3.0.9.0 version, Rating business logic
ACTUAL BEHAVIOR
----------------------
It is observed that the value of Validity time in Diameter Credit Control Answer (CCA) is varying.
Consider a scenario, where the user set default validity time as 600 seconds. But when the quota is getting granted then validity time is also getting prorated based on Granted Service Unit (GSU).
In another scenario they had only 1.5MB as GSU and they have got only 3 seconds as validity time. This value is very less.
EXPECTED BEHAVIOR
-----------------------
The validity time should be static.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On ECE 11.3.0.9.7 Version, set the granted service unit less than that of Requested Service Unit (RSU).
2. Check when the quota is getting granted, the validity time is also getting prorated based on GSU or not.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |