My Oracle Support Banner

Wrong Dates Are Sent by DGW in CCA Message for Expiry of the Various Buckets (Doc ID 2913835.1)

Last updated on DECEMBER 12, 2022

Applies to:

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

Symptoms

On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.4.6, for the scenario of data session, Diameter Gateway (DGW) is sending wrong values for ORA-Earliest-Expiry-Time in Credit Control Answer (CCA) sent for first Credit Control Request - Update (CCR-U) message in the session.

The following response is received from Event Charging Server (ecs):

The problem is that DGW wrongly translates INIX time to a date from 1952.

It is expected DGW will send the same dates in CCA as it received from ecs.

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


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