Records intermediate – Cisco OL-15491-01 User Manual
Page 228

A-228
Cisco Content Services Gateway - 2nd Generation Release 2.0 Installation and Configuration Guide
OL-15491-01
Appendix A CSG2 Command Reference
records intermediate
records intermediate
To enable the generation of CSG2 intermediate call detail records (CDRs), use the records intermediate
command in CSG2 content configuration mode. To disable the generation of intermediate CDRs, use the
no form of this command.
records intermediate {bytes bytes | seconds seconds | bytes bytes seconds seconds}
no records intermediate {bytes bytes | seconds seconds | bytes bytes seconds seconds}
Syntax Description
Defaults
If you do not specify the records intermediate command, or if you specify the records intermediate
command for a content for a protocol handler that does not support intermediate statistics, intermediate
CDRs are not generated.
If you specify the bytes keyword but not the seconds keyword, the maximum time between billing
records for a session is set to 0 seconds, indicating no time limit.
If you specify the seconds keyword but not the bytes keyword, the number of bytes of data that triggers
the sending of an intermediate CDR is set to 0 bytes, indicating that the number of bytes sent and
received will not trigger an intermediate record.
If you specify both the bytes keyword and the seconds keyword, a billing record is sent when either limit
is reached. Then both limits are reset.
Command Modes
CSG2 content configuration
bytes bytes
Number of bytes of data, sent and received by a session, that triggers the sending of
an intermediate CDR.
The difference between bytes sent and received in two records might not exactly
equal the bytes argument. A trigger can occur only on a packet boundary. Once
triggered, a separate process captures a snapshot of the current byte counts for a
session. Between the trigger and the snapshot, additional packets might be counted.
The range is from 5000 to 4294967295. The default value, if the bytes keyword is
not specified, is 0, indicating that the number of bytes sent and received will not
trigger an intermediate record.
seconds seconds
Maximum time, in seconds, between billing records for a session. Records can be
sent more frequently if the number of bytes is reached.
When a record is sent because the maximum time has been reached, the byte counts
reported in the record are approximate.
The range is from 5 to 86400. The default value, if the seconds keyword is not
specified, is 0, indicating no time limit.