[JP] Midsession CDR Is Created On The First Gyn Update Usage Not Meeting Midsession Cdr Condition
(Doc ID 3060995.1)
Last updated on DECEMBER 19, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Goal
On : 12.0.0.8.0 version, Charging server launcher
Midsession CDR is created on the first gyn update usage not meeting midsession cdr condition
Charging-Settings.xml midsession CDR configuration is as below:
Steps :
1. Create Account activate
2. Initiate a Session (RGID 8000)
3. Purchase a Addon which grants 1GB data for BOCO counter
4. Consume around 400mb of data on RGID 8000
Expected Results: CDR should not get created with just 400MB of usage
Actual Results: : CDR gets generated randomly which creates an unnecessary load on the system.
How to resolve this issue?
Solution
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
Goal |
Solution |