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
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 5.0.0 and later
Information in this document applies to any platform.
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 :
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.
This problem is discovered on NCC 22.214.171.124, but is likely to be present on previous versions. An upgrade to an impacted version may introduct this problem.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms