DCA Rejects the CCR Message with "is less than last received" Error when CC-Request-Number is Out of Sequence In The Same MSCC Session (Doc ID 1600938.1)

Last updated on MARCH 27, 2023

Applies to:

Symptoms

Introduction

It is important to understand that the Oracle Communication Network Charging and Control (OCNCC or NCC) application will allow disordered CC-Request-Number only within the same Multiple Services Credit Control (MSCC) session, and only if the CC-Request-Number are ordered from each rated service point of view.

The NCC Diameter Charging Agent (DCA) interface will reject a message with a disordered CC-Request-Number

• for a single charging session
• within the same service in a MSCC session

Please refer to the following note for more information :

DCA Rejects the CCR Message with "is less than last received" Error when CC-Request-Number is Out of Sequence (Doc ID 1549806.1)

This document reports a problem where DCA ignores Credit-Control Request (CCR) messages with disordered CC-Request-Number, where CCRs are for different services within the same MSCC session. It is important to note that the order is kept for each service (based on Rating-Group), the disorder only appears across services within the same session.

It is expected that NCC allows disordered CCRs for different services within the same MSCC session.

Changes

This problem is discovered on NCC 5.0.0.2, but is likely to be present on previous versions. An upgrade to an impacted version may introduce this problem.

Cause

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