beautypg.com

Records granularity – Cisco OL-15491-01 User Manual

Page 226

background image

A-226

Cisco Content Services Gateway - 2nd Generation Release 2.0 Installation and Configuration Guide

OL-15491-01

Appendix A CSG2 Command Reference

records granularity

records granularity

To specify the granularity at which CSG2 billing call detail records (CDRs) are to be generated, use the
records granularity command in CSG2 service configuration mode. To restore the default granularity,
use the no form of this command.

records granularity {transaction | service {bytes bytes | seconds seconds | bytes bytes

seconds seconds}}

no records granularity

Syntax Description

Defaults

If you do not specify the records granularity command, CDRs are generated for each transaction.

If you specify records granularity service, you must also specify the bytes keyword, the seconds
keyword, or both:

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.

If you specify only the bytes keyword and not the seconds keyword, there is no time limit between
billing records for a session.

If you specify only the seconds keyword and not the bytes keyword, there is no maximum number
of bytes of data that triggers the sending of a billing record.

Command Modes

CSG2 service configuration

transaction

Generate CDRs for each transaction. This is the default setting.

service

Generate summarized, service-level CDRs.

bytes bytes

Number of bytes of data, sent and received by a session, that triggers a CDR.

The difference between bytes sent and bytes received in two records might
not exactly equal the bytes argument, because updates must occur on packet
boundaries.

The range is from 5000 to 2147483647. If the bytes keyword is not
specified, there is no maximum.

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. If the time keyword is not specified, there is
no time limit.