How to Overcome the ATPD Call Duration Limitation when Used with ECA
(Doc ID 2309160.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 184.108.40.206.0 [Release 4.3 to 12.0.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 220.127.116.11.0 [Release 6.0 to 12.0.0]
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), the Event Data Record Control Agent (ECA) is a flexible interface used to process incoming flat files containing Event Data Records (EDRs) or Call Data Records(CDRs) to trigger services on OC3C/NCC configured in an Advanced Control Services (ACS) Control Plan (CP). ECA will parse the contents of the EDR and generate a "fake" voice call to ACS.
One scenario ECA can be utilized is the offline charging of services used by a subscriber.
This can be easily achieved by using an Attempt Terminate to Pending Termination Number with Duration (ATPD) node and a Direct Unit Charge Request (DUCR) node for call durations under 86400s but will result in revenue loss for any duration which exceeds this duration.
This article will explain the reason behind this limitation and offer an alternate approach to circumvent this limitation.
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