My Oracle Support Banner

5G CHF || Duration Is Coming Incorrectly As Zero For The CDRs With RetransmissionIndicator=true (Doc ID 2984804.1)

Last updated on NOVEMBER 06, 2023

Applies to:

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


For 5G Charging Function (CHF), duration is coming incorrectly as zero for the Call Detail Record (CDRs) with retransmissionIndicator=true. 

Partial CDRs are generated after setting isPossibleDuplicate = true. 
While performing internal validation, it has been observed that duration is coming as zero and entry is not in seqStore while generating previous CDR (possibleduplicate= true).

Scenario followed to reproduce the issue:

Duration is coming incorrectly as zero for the subsequent CDR after retransmissionIndicator=true.

1. Account provision.

2. Site-1 outage; Update went to site-2; external trigger RAT_CHANGE; retransmissionIndicator=true in the payload; ISN-4; could see CDR with duration 0. This is okay.

3. Session next update to site-2; external trigger RAT_CHANGE; ISN-5;
In this CDR, expecting the correct duration instead of 0.


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

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