ECE Diameter Gateway Responding With Result Code 5012 For CCR-Update Requests
(Doc ID 2852636.1)
Last updated on APRIL 17, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.7.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Elastic Charging Engine (ECE) 11.3.0.7.0 version, Rating business logic
ACTUAL BEHAVIOR
---------------
ECE is not processing customer's Credit-Control-Update Requests (CCR-U) from Network and respond with RESULT CODE 5012(DIAMETER_UNABLE_TO_COMPLY). The usages are not getting reported in these case and ECE throws the below Exception during this.
ecs.log:
EXPECTED BEHAVIOR
-----------------------
ECE Should process the CCR-Update requests from Network
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send Diameter CCR-Update requests from Network to ECE Diameter Gateway.
2. Verify if ECE/DGW is responding with DIAMETER_UNABLE_TO_COMPLY Result Code with the mentioned exception.
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 |