My Oracle Support Banner

NCC Generated RARs Always Set End-toEnd Identifier to 0 (Doc ID 3036666.1)

Last updated on JULY 23, 2024

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 to 15.0.1.0.0 [Release 4.3 to 15.0.0]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 15.0.1.0, an issue exists where the Re-Authorization-Requests (RAR) generated by NCC always have the End-to-End identifier always set to 0.

As per the Request for Comment (RFC) 3588:

   End-to-End Identifier
      The End-to-End Identifier is an unsigned 32-bit integer field (in
      network byte order) and is used to detect duplicate messages.
      Upon reboot implementations MAY set the high order 12 bits to
      contain the low order 12 bits of current time, and the low order
      20 bits to a random value.  Senders of request messages MUST
      insert a unique identifier on each message.  The identifier MUST
      remain locally unique for a period of at least 4 minutes, even
      across reboots.  The originator of an Answer message MUST ensure
      that the End-to-End Identifier field contains the same value that
      was found in the corresponding request.  The End-to-End Identifier
      MUST NOT be modified by Diameter agents of any kind.  The
      combination of the Origin-Host (see Section 6.3) and this field is
      used to detect duplicates.  Duplicate requests SHOULD cause the
      same answer to be transmitted (modulo the hop-by-hop Identifier
      field and any routing AVPs that may be present), and MUST NOT
      affect any state that was set when the original request was
      processed.  Duplicate answer messages that are to be locally
      consumed (see Section 6.2) SHOULD be silently discarded.

This causes issues with the diameter network as the RAR will be treated as a duplicate message and be discarded due to the Origin-Host always being the same value from the same Service Logic Controller (SLC).

For information on how to configure RARs from NCC, please refer to: How to Configure RAR Support in NCC (Doc ID 2894460.1)

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.