ECE/DGW - ER To Handle CCR-T Without MSCC Block
(Doc ID 3014332.1)
Last updated on APRIL 05, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Goal
Currently, when a Credit-Control-Request of type Terminate (CCR-T) without MSCC block is received by Diameter Gateway|Elastic Charging Engine (DGW|ECE), then the following exception is thrown:
DGW log:
2022-09-02 06:13:55.865 CEST ERROR - - - - DiameterFrameworkMessagesBundle-30112: Following AVP is missing as part of the request: Multiple-Services-Credit-Control
oracle.communication.brm.charging.ecegateway.diameter.framework.controller.DiameterFrameworkException: DiameterFrameworkMessagesBundle-30112: Following AVP is missing as part of the request: Multiple-Services-Credit-Control
at oracle.communication.brm.charging.ecegateway.diameter.framework.controller.DiameterFrameworkUtils.handleMissingAVP(DiameterFrameworkUtils.java:506) ~[ece-diametergateway.jar:?]
...
Q1: There is a need for an Enhancement Request (ER) to handle CCR-T without MSCC block (or when this block is present but does not contain all Rating-Groups). Both cases are valid from 3GPP point of view but ECE is failing to handle this.
Solution
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
Goal |
Solution |
References |