Callassembling Flush Produced Duplicate Records

(Doc ID 854154.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 6.5.0.1.1
This problem can occur on any platform.

Symptoms

-- Problem Statement:
Unexpected duplicate records are found in the output from a Flush operation on the CallAssembling
plugin.

Before CallAssembling, for a given chain reference, the EDR dump includes these entries:

CHAIN_REFERENCE: <;217.200.177.11244709150>;

LONG_DURATION_INDICATOR: <;I>;
CHARGING_START_TIMESTAMP: <;20081209141656>;
CHARGING_END_TIMESTAMP: <;20081209141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081210141656>;
CHARGING_END_TIMESTAMP: <;20081210141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081207141656>;
CHARGING_END_TIMESTAMP: <;20081207141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081208141656>;
CHARGING_END_TIMESTAMP: <;20081208141735>;

LONG_DURATION_INDICATOR: <;I>;
CHARGING_START_TIMESTAMP: <;20081206141656>;
CHARGING_END_TIMESTAMP: <;20081206141735>;

Note the two duplicate L segments, which were rejected (as expected).

Following the CallAssembling module, these entries are found in the EDR dump

Error / Sev. = <;ERR_DUPLICATE_SEGMENT / MAJOR>;
LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081207141656>;
CHARGING_END_TIMESTAMP: <;20081207141735>;

Error / Sev. = <;ERR_DUPLICATE_SEGMENT / MAJOR>;
LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081208141656>;
CHARGING_END_TIMESTAMP: <;20081208141735>;

The following were produced after a flush operation:

LONG_DURATION_INDICATOR: <;I>;
CHARGING_START_TIMESTAMP: <;20081206141656>;
CHARGING_END_TIMESTAMP: <;20081206141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081207141656>;
CHARGING_END_TIMESTAMP: <;20081207141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081208141656>;
CHARGING_END_TIMESTAMP: <;20081208141735>;

LONG_DURATION_INDICATOR: <;I>;
CHARGING_START_TIMESTAMP: <;20081209141656>;
CHARGING_END_TIMESTAMP: <;20081209141735>;

LONG_DURATION_INDICATOR: <;L>;
CHARGING_START_TIMESTAMP: <;20081210141656>;
CHARGING_END_TIMESTAMP: <;20081210141735>;


Note how L segments with start 20081207141656 and 20081208141656 have been produced from the
flush, even if they were rejected for ERR_DUPLICATE_SEGMENT.

-- Steps To Reproduce:
1) Process duplicate "L" segment, with CallAssebling configured with "GapsOkOnFlush = FALSE"
2) Flush the CallAssembling


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms