My Oracle Support Banner

Declined Billing Cause Node Does Not Work With Named Events (Doc ID 2617082.1)

Last updated on DECEMBER 10, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC) until 12.0.3 the Control Plan (CP) defines where to route calls, based on factors such as the type of service, geographic location, time of day, and so on. 

The Declined Billing Cause Branching (DBCB) node is used in the CP to determine the cause of a billing failure.

DBCB feature node provides additional functionality for the Universal Attempt Termination with Billing (UATB) feature node when placed after the "declined (no funds)" branch of the UATB feature node. 

DBCB works well when placed after the UATB node, however if the billing is done via a Named Event Node, the DBCB node does not return accurate billing failure causes.

Changes

 

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
Changes
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.