Post-session BFT Taking Wrong Exit Of The UATB Node.
(Doc ID 2356265.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On version Oracle Communications Convergent Charging Controller 6.0.1, the Advanced Control Services (ACS) Control Plan, Universal Attempt Termination with Billing (UATB) node is used to bill subscribers for calls that they make or receive. Billing is done following the tariff plan assigned to the subscriber's product type.
Once the call has been connected, we have two parties attached to the call. The Billing Failure Treatment (BFT) (Released) and BFT (Disconnected) branches are used to differentiate between whether the A or B party ended the call. Essentially whether or not telephony is allowed.
The BFT exit does not cater for this. If the Vouchers and Wallets Server (VWS) is down while the ConfirmationRequest message is received for a call where the call got disconnected either by A or B party then UATB node was taking Billing Failure Treatment (BFT) exit ( Branch 2 ) as this value was hard coded. This scenario is ont always correct.
BFTGracePeriodLength can be configured as follows:
- -1: No grace period on BFT (communication or system error) for subsequent reservations. Node will branch donnected (NSF) on communication/system error.
- 0: No grace period on BFT (communication or system error) for subsequent reservations. Node will properly treat call as BFT, branching disconnected (BFT) on communications/system error. Call length of 0 is confirmed.
- Positive: The call is allowed to continue for the specified number of seconds on communication/system error for subsequent reservations. Node will properly treat call as BFT, branching disconnected (BFT) on communication or system error. Call length of 0 is confirmed.
- -2: behaves as per the 0 case, but no ACH is sent.
If missing/not configured, then this parameter defaults to -1.
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