Realm And Host Configuration In DiameterGateway Active-Active Setup Is Incorrect
(Doc ID 2878060.1)
Last updated on JUNE 27, 2022
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Issue is that since Elastic Charging Engine (ECE) charging-settings is being federated from site 1 to site 2, the diameter gateway (DGW) configuration is being overridden from site 1. Since realm and host name are different for site 1 and site 2, User is facing issues when they are connecting to DGW as they returning site 1 hostname in Capabilities Exchange Request (CER).
But in charging-settings.yaml, it is taking the cluster name from charging section of override-values.yaml and creating entries in charging-settings.xml in the configmap.
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