DiameterGateway Not Logging Error For Result Code 5010 For Unsupported Auth-Application ID (Doc ID 3072253.1)

Last updated on FEBRUARY 14, 2025

Applies to:

Symptoms

On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.8.7, DiameterGateway, Cloud Native (CN) Deployment

ACTUAL BEHAVIOUR:
-------------------------

Consider the scenario where DiameterGateway (DGW) is responding with Result Code 5010 ((DIAMETER_NO_COMMON_APPLICATION) for an un-supported Auth-Application ID from Gy/Sy Interface.

Here when the "diameter.framework" module loglevel is set as ERROR, the diameterGateway.log just shows the below line (incompatible capabilities, reason DIAMETER_NO_COMMON_APPLICATION (5010)) and it does not show the exact diameter message for which this result code 5010 is reported. In addition, here the diameterGateway.log also shows a "java.nio.channels.ClosedChannelException: null" during this scenario

diameterGateway.log

2. It should not throw "ClosedChannelException" while responding with Result Code 5010 towards Network.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Initiate a CER towards DGW and pass any value in Auth-Application-Id other than the values mentioned inside dictionary_main.xml
    Auth-Application-Id (258,M,l=12) = 1234
2. Check if DGW respond with the Result-Code 5010 as mentioned above.

Cause

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