accounting

Syntax

accounting {profile profile-name {operational-state (normal | survivable | any); report-unanswered-call;use-compact-cdr;formats {comma-separated-values csv-profile-name {batch-size size; purge-time-interval interval; }}transport ftp {server server-name {address (fqdn fqdn | ipv4-address ipv4-address); auth-id authentication-id; auth-password authentication-password; format csv-profile-name; path-name file-path-name; }}}}

Hierarchy Level

[edit services convergence-services features]

Release Information

Statement introduced in Release 10.2 of Junos OS.

Description

Configure the accounting feature to direct the voice daemon to generate and collect call records, write them to a file, and store them in an archive. The voice daemon collects the records in batches whose size you specify, and then it writes them to a file in system memory. You can also specify a purge time interval to direct the voice daemon to write the records to the system memory file at that time, regardless of whether the batch size number of records is met. The batch size and the purge time interval work together to ensure that the records the voice daemon collects are written to the system memory file at a specified point to avoid data loss if the voice daemon crashes.

Note: Despite these precautions, the voice daemon can crash before either the batch size or the purge time interval is reached. In this case, the generated and collected call records are lost, and they are not written to the system memory file.

The voice daemon also takes precautions against loss of record data that can occur if the system is rebooted. To this end, at 15 minute intervals, the voice daemon writes record files stored in system memory to an archive in permanent storage, either to a server, if you configure information for one, or to flash memory. If the server is unavailable, it writes the file to flash memory.

Note: If the system crashes before the file containing the call records is written either to an FTP server or to flash memory to be archived, the records that the voice daemon generated and collected are lost.

Because the flash memory might be full, the voice daemon rotates files that it writes to the flash memory. The daemon overwrites existing files on a first-in, first-out (FIFO) basis.

By default, the voice daemon collects records for successful calls that have been answered. If a call is not answered, it is considered unsuccessful. If you have configured the report-unanswered-call parameter for the accounting profile, the voice daemon also writes records for unsuccessful calls.

It is possible that a call engaged in a constellation can both succeed and fail. For example, a call from one party to another might succeed, but if the call is transferred to a third party whose line is busy or the call cannot be connected for some other reason, it fails. In this case, two records are generated, one for the part of the call that succeeded and one for the part of the call that failed.

The calling party incurs session level and transport level accounting at both the calling party and called-party sides.

The accounting feature applies to both the SRX Series media gateway (SRX Series MGW) and the SRX Series survivable call server (SRX Series SCS).

Options

The remaining statements are explained separately.

Usage Guidelines

For configuration instructions and examples, see the Junos OS Integrated Convergence Services Configuration and Administration Guide.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.