My Oracle Support Banner

How To Keep The Original Session_id On Rated Event From OCOMC (Doc ID 3027602.1)

Last updated on JUNE 10, 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.

Goal

How to keep the original session_id on rated event from Oracle Communications Offline Mediation Controller (OCOMC)?

OCOMC sets a session_id on every Call Details Record (CDR), when it is rated on Elastic Charging Engine (ECE), this session_id is stored on the field EVENT_T.NETWORK_SESSION_ID but extra values are being concatenated on ECE.

For example:
OCOMC sets the session_id:
DGR_CTL_CEL_3G_xxxx_20240214_05.txt83234144608976872029090222491020290902225017102400

ECE changes it to:
DGR_CTL_CEL_3G_xxxx_20240214_05.txt83234144608976872029090222491020290902225017102400_ECE_MSCC_SESSION_ID_TelcoGsmTelephony_83234144
As it shows, the extra information is "_ECE_MSCC_SESSION_ID_TelcoGsmTelephony_83234144"

The new session_id value is being stored in the EVENT_T.NETWORK_SESSION_ID field.

This behavior began to occur from the upgrade to BRM12, before that the original session_id was kept.

Solution

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