My Oracle Support Banner

CAET set as CCET when ElapsedTimesFromApplyChargingReport is Enabled (Doc ID 2346777.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 6.0.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Network Charging and Control (OCNCC) version 6.0.1, in the Advanced Control Services (ACS) module, different ways to compute the call duration can be used. 

The 'elapsedTimesFromApplyChargingReport' option determines whether or not to calculate Call Attempt Elapsed Time (CAET) and Call Connect Elapsed Time (CCET) using the ApplyChargingReport message.

It has been observed that when 'elapsedTimesFromApplyChargingReport' option is enabled, CAET held incorrect values. 

Here is an example from the debug logfile showing the call which has no ring time:

2017/06/08 03:12:48    acsChassisTelephony.cc  3826 [16211] acsChassisSLEE    Setting elapsed times from ACR: callAttemptElapsedTime: 0; duration in deciseconds: 807; callStopTime: 1496891568

The EDR values:

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.