My Oracle Support Banner

DGW_UNABLE_TO_COMPLY When Sy Triggered On Closed Account (Doc ID 2937853.1)

Last updated on APRIL 17, 2024

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Goal

Qn1:When Sy session is triggered on closed account/service, DGW reported DIAMETER_UNABLE_TO_COMPLY(5012) in SLA.
But our expectation is to get DIAMETER_USER_UNKNOWN as this error code is more relevant for this scenario.

Steps to replicate the issue:
1. Create an account with Base,Roaming and RCC bundle.
2. After 10 min, close the account. using SET_STATUS.
3. Trigger usage on this closed account (Sy, Gy)
4. Sy SLA returned result code 5012 DIAMETER_UNABLE_TO_COMPLY.

Actual: DIAMETER_UNABLE_TO_COMPLY
Expected: DIAMETER_USER_UNKNOWN
 
Qn2:why are we getting DIAMETER_UNABLE_TO_COMPLY when MSISDN does not existing at that time. Account is not only closed but MSISDN is also renamed from XYZ to XYZ_epoch_time?
 

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


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