Unable To Change Service-Context-Id AVP In OCSG 4.1
(Doc ID 1055102.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Communications Services Gatekeeper - Version 4.1.1 to 4.1.1 [Release 4.1]
Information in this document applies to any platform.
While integrating OCSG 4.1 with 3rd party Diameter charging simulator, there is no way to change "oracle.com" suffix for Service-Context-Id when sending ChargeAmount request.
OCSG is able to connect to the simulator successfully. While sending ChargeAmount request it received a service exception. After debugging this error it was found that one of the mandatory AVP (Service-Context-Id) is failing in CCR request for chargeAmount. Service-Context-Id is configurable and it is part of the parlay X request in charge:code() field, but there is no way to change "oracle.com" suffix for Service-Context-Id.
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