My Oracle Support Banner

HTTP Gateway - NRF Registration Issue (Doc ID 2862503.1)

Last updated on AUGUST 08, 2023

Applies to:

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

Symptoms

On Elastic Charging Engine (ECE) 12.0 Patch Set 4 Interim Patch 3, registration of Charging Function (CHF) via HTTP Gateway is failing in Network Repository Function (NRF) with responseCode=400 since HTTP gateway is sending those fields whose values are not defined in the charging-settings.

Example:
The values are not defined like below, but still it is going in the NRF put request.
ipv4Addresses":[],"ipv6Addresses":[],"allowedPlmns":[],"allowedSnpns":[],"allowedNfTypes":[],



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure with null values
 plmnRangeListStart: ""
  plmnRangeListEnd: ""
  plmnRangeListPattern: ""

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


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