The Call Cost Node That Reads In The Call Cost from ECE Considers A Zero-cost As "unsupported"
(Doc ID 2855237.1)
Last updated on JUNE 16, 2023
Applies to:Oracle Communications Convergent Charging Controller - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On Oracle Communications Convergent Charging Controller (OC3C), 188.8.131.52.0 version,
The Call Cost node that reads in the call cost over Diameter Charging Driver (DCD) from Oracle Communications Elastic Charging Engine (ECE) considers a zero-cost as "unsupported"
Here OC3C receives the call cost over Diameter in the CCR-Terminate message. This call cost is correctly read in by DCD, and transferred to Adavnce Control Services (ACS). If this call cost is 0, then the Call Cost Duration Branching (CCDB) Feature Node exits out of the unsupported branch, not one of the other branches.
A value of 0 for call cost is a valid call cost that might need to be presented to the subscriber, so the unsupported branch is not a valid branch to take in this scenario.
The issue can be reproduced at will with the following steps:
1. On OC3C 12.0.4 Version, receive a Call cost of zero on a CCR-Terminate message on the DCD Interface from ECE.
2. Check if the call cost is correctly read in by DCD, and transferred to ACS via the Control Plan having the CCDB Node.
2, Check if the Call Cost Duration Branching (CCDB) node exits out of the unsupported branch.
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