Diameter Error 5030 Is Not Showing up in the Log When Log Level Is Error
(Doc ID 3028029.1)
Last updated on JULY 18, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Symptoms
Diameter error 5030 (UNKNOWN_SUBSCRIBER) is not showing up in the DiameterGateway (DGW) log file when it is set to ERROR log level (see below log snippet). However if one increases the log level to DEBUG, the error 5030 is captured in the log.
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 |