Gy Terminate Request on a RGID Terminating Rest of the RGID Sessions
(Doc ID 3063048.1)
Last updated on DECEMBER 11, 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
If one terminates 1 session with 1 Rating Group ID (RGID), the rest of the sessions with different RGID also gets terminated.
STEPS
-----------------------
1. Create Account and Activate
2. Initiate a session with RGID 8000
3. Purchase Addon with BOCO and CUCO Bucket
4. Send update with 400mb Used Service Unit (USU) with RGID 8000
5. Purchase Addons with B_COUNT and AACO Buckets
6. Send Gy Update with 8100 RGID and 0mb USU
7. Send 1 more update with 8100 RGID and 400mb USU
8. Send Gy Terminate with 8000 RGID with 400mb USU
BOCO = A boost bucket which is having high priority ChargeOffer.
CUCO = A deal bucket with the name CU.
AACO = A deal bucket with the name AA.
EXPECTED BEHAVIOR
-----------------------------------
Session with 8100 RGID should be there active and holding the balance.
ACTUAL BEHAVIOR
-----------------------------------
1. Session with RGID 8100 also got cleared from Balance cache and ActiveSession cache.
2. Call Detail Record (CDR)s created for 8100 RGID do not report the usage happened before the terminate to Database (i.e step 7 usage not reported DB causing balance mismatch in DB and ECE Balance Cache).
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 |
References |