NGW Does Not Process "ON_Result_Code" from OSD
Last updated on NOVEMBER 06, 2017
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Convergent Charging Controller (OC3C), the Notification Gateway is a process which listens for Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) notifications and transforms them into Simple Object Access Protocol (SOAP) messages for Open Services Development (OSD). OSD in turn triggers service logic in an Advanced Control Services (ACS) Control Plan to send a notification to an end subscriber.
There are 2 ways to map different outcomes of the service logic executed in the Control Plan to OSD (which determines what OSD sends back to NGW):
- The SOAP status code which is based on whether a Release/Disconnect or Connect was returned by ACS
- The ON_Result_Code field in the SOAP eXtensible Markup Language (XML) which is based on what the Control Plan populates in the ON_Result_Code Profile Tag
Out of the box, the Control Plans delivered with NGW will always return a Connect and will set the ON_Result_Code to different values depending on which exit was taken from the Send Notification (NOTF) Feature Node (FN).
NGW unfortunately does not currently process the ON_Result_Code from OSD and only uses the SOAP status code to determine if the processing of the notification was successful or not.
So, out of the box, failures in ACS are never propagated back to NGW.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms