UATB Node Takes INSF Exit Instead of BFT after Mid-Call BFT
Last updated on SEPTEMBER 25, 2017
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), when using the Universal Attempt Termination with Billing (UATB) node, mid-call/session billing failures result in the UATB node exiting out the Insufficient Funds (INSF) exit instead of the Billing Failure Treatment (BFT) exit.
As a result, any contingency service logic expected after a BFT scenario will not be triggered in a BFT situation.
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