NRF Registration Process Triggering GET Request Instead Of PUT
(Doc ID 2828335.1)
Last updated on DECEMBER 15, 2021
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
While doing Network Repository Function (NRF) - Charging Function (CHF) integration, it is observed request triggered from httpgateway towards NRF is a GET request. As per 3gpp first request should be PUT request for registration.
GET request is responded by NRF with Response 501.
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 |