My Oracle Support Banner

CDRs Closed With "NORMAL_RELASE" While The Trigger Was "ABNORMAL_RELEASE" (Doc ID 3028857.1)

Last updated on JULY 29, 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

Charging Function (CHF) Generated a complete Call Detail Record (CDR) with Cause for Rec Closure as "NORMAL_RELEASE" incorrectly for the Abnormal release in the PDU trigger session of CDRs .

In customer's environment,observed that CDRs closed with "NORMAL_RELASE" while the trigger was "ABNORMAL_RELEASE" , but for these triggers CFRC should be same as trigger type except the Final trigger where CFRC should be "NORMAL_RELEASE"

EXPECTED BEHAVIOR
-----------------------
In this scenario, causeForRecordClosing should be shown as ABNORMAL_RELEASE.

Steps to reproduce:
1. Send an INITIATE
2. Send a TERMINATE for same sessionID ( TERMINATE should have "ABNORMAL_RELEASE" in external triggers field)

Query:How to fix this?

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
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.