My Oracle Support Banner

ACS Populates EDR RELC From CIR When No Release Cause Was Requested Or Provided (Doc ID 2333959.1)

Last updated on DECEMBER 06, 2017

Applies to:

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


On Oracle Communications Convergent Charging Controller(OC3C), 6.0.1 version, it is observed that Advanced Control Services(ACS) populates Event Detail Record(EDR) RELC from the Call Information Report(CIR) when no release cause is requested or provided.

Actual Behavior:

Consider a scenario when ACS is configured to use the CIR but not use the Release Cause, i.e, when SendCIR = 1 and AskCirReleaseCause = 0, the RELC value in the EDR is overwritten with 0.


In other words, it appears that the Telephony Release Cause is overwritten by the Release Cause from the CIR, even when a CIR Release Cause is not requested or supplied. This means that our EDRs will always have RELC=0.

Expected Behavior:

It is expected that RELC contain the INAP/CAMEL call release cause value. ie, it will be like below:

  1. If SendCIR = 0, RELC = regular INAP/CAMEL Release Cause.

  2. If SendCIR = 1,

    a. AskCirReleaseCause = 0, then RELC = regular INAP/CAMEL Release Cause.
    b. AskCirReleaseCause = 1 and CIR provides the release cause, then RELC = as provided in CIR.
    c. AskCirReleaseCause = 1 and CIR does not provide the release cause, then RELC = regular INAP/CAMEL Release Cause.


The issue can be reproduced at will with the following steps:
1. Enable SendCIR in acs.conf.
2. Enable any or all of the AskCIR* parameters except 'AskCirReleaseCause'.
3. Run a charged call where either party disconnects after talk time is used.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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