Round Robin Routing Creating Duplicates CDR's some times
(Doc ID 2815704.1)
Last updated on OCTOBER 25, 2021
Applies to:Oracle Communications Offline Mediation Controller - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Customer Node Chain is having an Aggregation Processor (AP) connected with Distribution Cartridge (DC) on remote servers . Single AP is connected with 2 or more DC on remote server which are connected as Round Robin. Some time same Call Detail Record (CDR) is sent to both the DC. This is not happening always and only few times it is seen.
Duplicate CDR's are happening when customer configure "Both(Time Based and Volume Based Session Segmentation)" in AP GUI.
AP is flushing out the CDR even when HashTableFlush0 "delete"; is set in config block when data volume is reaching the limit configured
In Graphical User Interface (GUI) causing the duplicate CDR's. customer could not use just timer based flush because few methods like Java.storeNARWithTimer(in, tableIndex, currTime, "true"); and Java.storeNARWithAbsoluteTimer(in, tableIndex, flushTimeLong); do not work when they select just time based flush.
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