ACS Chassis Parameter OverwriteFci Not Working As Expected
(Doc ID 2718585.1)
Last updated on OCTOBER 12, 2020
Applies to:Oracle Communications Network Charging and Control - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (NCC) 18.104.22.168.0 version
As per NCC Advanced Control Services (ACS) Technical Guide, "overwriteFci" parameter inside acs.conf is used to control when a new Furnish Charging Information (FCI) is appended to an existing FCI or overwrites an existing FCI.
For Voice calls, Customer require an FCI before the connect/release operation. For example in case of Successful billing they want to send FCI 1 and if the Universal Attempt Termination with Billing (UATB) Feature Node fails, they want to send FCI 2. However instead of sending FCI B, NCC sends FCI 1 + 2 concatenated together.
Successful billing should send FCI 1 and If the UATB node fails, it should send FCI 2.
The issue can be reproduced at will with the following steps:
1. On NCC 12.0.2 Version, SMS Screen--> ACS -> Resources -> Tariff Codes -> New, Create two different FCI codes. FCI 1 and FCI 2.
2. Create a new control plan using the following Nodes.
Start Node--> Set Tariff Code 1 (FCI 1) -> AT node -> Set Tariff Code 2 (FCI 2)--> End Node
Set Tariff Code 1 (FCI 1)---Connect Tariff Set Exit Branch to ATnode, Tariff Not Set Branch to End Node
Connect AT node Success Node to End Node and Remaining failure exist to Set Tariff Node 2
Connect remaining Exists to End Node
3. Set a subscriber with insufficient funds and use the above Control Plan and trigger the same using a slpit script.
4. Check whether you are getting FCI1+ FCI2 concatenated together.
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