Event Detail Records (Edrs) - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview
The Diameter Credit Control Application (DCCA) which resides as part of the ECS manages the credit and quota for a
subscriber.
Important:
administration guide for the product that you are deploying.

Event Detail Records (EDRs)

Event Detail Records (EDRs) are usage records with support to configure content information, format, and generation
triggers by the system administrative user.
EDRs are generated according to explicit action statements in rule commands. Several different EDR schema types,
each composed of a series of analyzer parameter names, are specified in EDR. EDRs are written at the time of each
event in CSV format. EDRs are stored in timestamped files that can be downloaded via SFTP from the configured
context.
EDRs are generated on per flow basis, and as such they catch whatever bytes get transmitted over that flow including
retransmitted.
EDR format
The EDRs can be generated in comma separated values (CSV) format as defined in the traffic analysis rules.
Important:
value is greater than 127 characters, in the EDR it is truncated to 127 characters. In 15.0 and later releases, an optional
filter "length" is supported for HTTP URL and User-Agent fields which when added will allow the user to configure
length from 1 to 255 for these fields in EDRs. For more information, see the
5x00 Command Line Interface Reference.
Flow-overflow EDR
Flow-overflow EDR or Summary FDR is a feature to count the data bytes from the subscriber that are missed due to
various reasons in ECS.
In case any condition that affects the callline (FLOW end-condition like hagr, handoff) occurs, flow-overflow EDR
generation is enabled, an extra EDR is generated. Based on how many bytes/packets were transferred from/to the
subscriber for which ECS did not allocate data session. This byte/packet count is reflected in that extra EDR. This extra
EDR is nothing but "flow-overflow" EDR or Summary FDR.
The extra EDR is generated if all of the following is true:
 Subscriber affecting condition occurs (session-end, hand-off, hagr)
 Flow-overflow EDR generation is enabled
 EDR generation on session-end, hand-off or hagr is enabled
 Number of bytes/packets for flow-overflow EDR is non-zero.
The bytes/packet count will be printed as a part of "sn-volume-amt" attribute in the EDR. Hence, this attribute must be
configured in the EDR format.
EDR Generation in Flow-end and Transaction Complete Scenarios with sn-volume Fields
For more information on Gy interface support, see the Gy Interface Support appendix in the
In EDRs, the maximum field length for normal and escaped strings is 127 characters. If a field's
rule-variable
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Accounting and Charging Interfaces ▀
command in the ASR
67