Unrated CDR Incorrect Value '-1' For LRSN Incase Of Stale Session CDRs
(Doc ID 2964814.1)
Last updated on SEPTEMBER 13, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
As per 3GPP TS 32.298, Local Record Sequence Number - Consecutive record number created by the Charging Data Function (CDF). The number is allocated sequentially including all Call Data Record (CDR) types.
Presently we are seeing this Local Record Sequence Number statically coming as -1 for all staleSessionCleanup = true CDRs, which is deviation of 3GPP.
This needs to be corrected.
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 |