Diameter Gateway Result Code Expectation for MSISDN Not in Cache

(Doc ID 2405163.1)

Last updated on JUNE 12, 2018

Applies to:

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

Symptoms

On : 11.3.0.3.0 version, Diameter Gateway

When a CCR is sent for MSISDN which is not in cache, Diameter Gateway (DGW) should send CCA with RC = 5030 DIAMETER_USER_UNKNOWN, but DGW is sending as simple RC = 5012.

Send CCR:
 Session-Id (263,M,l=26) = session-1509457563
 ...
 Subscription-Id (443,M,l=40) =
   Subscription-Id-Type (450,M,l=12) = END_USER_E164 (0)
   Subscription-Id-Data (444,M,l=17) = 678678678
 ...

Error in diameterGateway.log:



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms