My Oracle Support Banner

5G || Incorrect CDR Consolidation For QHT Internal Trigger Followed By Release Having Extclosingtrig (Doc ID 3033663.1)

Last updated on JULY 18, 2024

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Symptoms

Incorrect CDR (Call Detail Record) consolidation for quota internal trigger followed by release request having external closing trigger

ACTUAL BEHAVIOR
---------------
In the CDR line num a and line b shows there are 2 instances of Used Service Unit (USU).

 



EXPECTED BEHAVIOR
-----------------------
 In the CDR line num a and line b shows there are 2 instances of USU. Ideally USU1 shouldn't be closed for quota trigger. There should be only 1 USU which is a consolidated one.


STEPS
-----------------------

This the 5G scenario.

1). Accout provision

2). Usage initiate

3). For the above session id, usage request-1 - usage request-1 should have USU with internal trigger (like QUOTA_EXHAUSTED)

4). For the above session id, release request, which has internal trigger MANAGEMENT_INTERVENTION, also has used units.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.