Diameter Event Time Stamp AVP Value Sent In CCR By OCSG Is Shown Incorrect In OCSG Default.log (Doc ID 1944123.1)

Last updated on JULY 06, 2015

Applies to:

Oracle Communications Services Gatekeeper - Version 5.1.0 and later
Information in this document applies to any platform.

Symptoms

Diameter Event Time Stamp AVP value sent in CCR by OCSG is incorrect as per RFC.

For example, presently even though OCSG sends the CCR with a proper Event Time
stamp value in the packet, the value printed in the log gives out a wrong
value which is unknowingly attributed as cause of any problems during
integration testing with 3rd party payment systems. Here is a example:

  user@company.com
  -1577201
  gvpSpAccount
  gvpAppAcount

The Event Timestamp value is time in seconds elapsed since Jan 01, 1900, here
the value printed in the log gives a wrong picture and does not translate to
valid date because of overflow of datatype in the plugin code.

From the diameter base protocol, Refer to RFC 3588
https://www.ietf.org/rfc/rfc3588.txt
section
8.21. Event-Timestamp AVP................................... 115
The Event-Timestamp (AVP Code 55) is of type Time, and MAY be included in an Accounting-Request and Accounting-Answer messages
to record the time that the reported event occurred, in seconds since January 1, 1900 00:00 UTC.

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