A Long Call Audit CDR (Call Detail Record) is generated for a call whose duration is longer than two consecutive midnights. The record itself is generated at the 2nd midnight and each midnight thereafter. A Standard CDR is generated when the call is released, with field no. 4 containing the total overall call duration.
The Long Call Audit Records contain essentially the same information as Standard CDR Records, the following fields, including comma delimiters, are not part of the Long Duration Audit Record:
Attempt Indicator (field #18 in Standard CDR)
Release Cause / Completion Indicator (field #19 in Standard CDR)
Call Release Time (field #49 in Standard CDR)
Incoming Carrier Release Time (field #51 in Standard CDR)
Outgoing Carrier Release Time (field #53 in Standard CDR)
IC / INC Call Event Status (field #61 in Standard CDR)
Therefore, the field numbers in the Long Call Audit Record do not match the field numbers in the Standard Call Record (for example, ‘Additional CDRs’ is field no. 94 in the Long Call Audit Record, while it is field no. 100 in the Standard CDR).
If you have not received statistics for a particular field, or if a field does not apply to your application, it displays a default of either zero (0) or NULL (, ,).
Configuration of RTP parameter Srx/Main/LongCallTimer
The maximum length of a long duration call can be specified via the RTP parameter Srx/Main/LongCallTimer
Valid values ranges from 4 to 240 hours. Default value is 12 hours.
After the expiration of this UCE timer the call will be torn down and a release will besent to both sides of the call to return them to the idle condition.
A long call timer value of zero (0) will disable this feature and leave a call up indefinitely.
Parent topic: Call Detail Record (CDR)
Standard CDR (Call Detail Record)
Intermediate Long Duration Records
Call Forwarding CDR (Call Detail Record)
Change of Software Audit Record
Feature Activation / Deactivation Record