"InsufficientFundsDropCallResultCodes" Does Not Perform Configured Response Mapping
(Doc ID 2485389.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Communications Network Charging and Control - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control(NCC), 6.0.1 version,
When values are set in the "insufficientFundsDropCallResultCodes" Diameter Charging Driver(DCD) configuration array, responses from a diameter server containing these result codes causes the diameter session to abort, but this fails to:
1) Set profile tags to AVPs returned by the diameter server
2) Writes a Billing Failure Treatment(BFT) tag to the EDR even if the cause is not necessarily BFT
The issue can be reproduced at will with the following steps:
1. Set up DCA/DCD, and add the insufficientFundsDropCallResultCodes configuration item
2. Run a data session
3. Have the diameter server return various Reason Codes (RCs).
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