Cisco ASR 5000 series Product Overview page 793

GTPP Storage Server Overview
custom4 Format: This custom4 format was created to support writing CDRs in blocks. This file format is
similar to custom3 file format except CDRs will be written in 2Kbyte blocks in a file.
Header: No Header
Contents: CDR1|CDR2FFFFFF|CDR3FFFFF..|..CDRnFFFF|
EoF marker: No EoF marker
File name format:
Important:
by the billing system. Typically, the billing system would rename the file with .p extension after processing the files
with CDR information. This also informs the GSS system that the file can be deleted during periodic cleanup.
custom5 Format: This file format is similar to custom3 file format except that the sequence number for CDR
file name is of six digits in length ranging from 000001 to 999999.
Header: No Header
Contents:
EoF marker: No EoF marker
File name format:
Important:
custom7 Format: This customer-specific file format contains CDRs converted from ASN.1 format to ASCII
format according to the following conventions. Each line in the file consists of one CDR which contains 33
parameters occupying 491 bytes.
Header: No Header
Contents:
EoF marker: No EoF marker
File name format:
custom8 Format: This customer-specific file format encodes CDRs according to the following conventions:
Header: No Header
Contents:
EoF marker: No EoF marker
OL-22938-02
where | represents the end of a 2k block
With file format custom4, the files are generated with .u file extension indicating an unprocessed file
This release of GSS does not support custom6 file format.
...
...
...
Features of the GSS ▀
Cisco ASR 5000 Series Product Overview ▄