ECE Not Accept Diameter Connection From Secondary CNCP Diam-gw Pod
(Doc ID 2929063.1)
Last updated on FEBRUARY 20, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.0.0.4.0 version, Diameter Gateway
For reasons of performance, one user needs to increase the number of Cloud Native Core Policy (CNCP) Diameter GateWay (DGW) pods that will talk to the Elastic Charging Engine (ECE) DGW pods with a one on one situation.
After correctly accepting Diameter Connection from CNCP DG (Capabilities Exchange Request (CER) / Capabilities Exchange Answer (CEA) messages are correctly exchanged), two CNCP DGW pods talking to ECE DGW, one has observed that the ECE DGW does not allow a connection from secondary pod.
However, according to the spec, the ECE DGW should accept a Diameter connection from same "Diameter Identity" even with a different IP address.
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 |