My Oracle Support Banner

Diameter Gateway Overload Protection (Doc ID 2536189.1)

Last updated on SEPTEMBER 17, 2019

Applies to:

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

Symptoms

On : 11.3.0.7.0 version, Diameter Gateway

When Diameter Gateway(DGW) overload protection is enabled and DGW is overloaded, the expected result code should be 'diameter too busy' (3004) but receiving 'diameter unable to comply'.

To be specific, currently the Sy interface receives the response code as "DIAMETER_UNABLE_TO_COMPLY" in case of Batch Request Service(BRS) Overload. The expected response code in case of BRS Overload should be "DIAMETER_TOO_BUSY".

A solution to this is expected in the product.

Changes

 

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
Changes
Cause
Solution
References


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