Cisco ASR 5000 Series - Page 792

GTPP Storage Server Overview
▀ Features of the GSS
▄ Cisco ASR 5000 Series Product Overview
OL-22938-02
EoF marker: \n
File name format:
GSN_
GSN_
custom1 Format: This file format encodes CDRs according to the starent file format explained above.
Important: The use of either starent or custom1 file formats, imposes a few specific reactions: - files are
generated without an extension; acknowledged and unacknowledged files are differentiated by their file names; the
system deletes all the files after reaching the maximum storage period (1-7 days) configured during GSS configuration.
custom2 Format: This customer-specific file format encodes CDRs according to the following conventions:
Header: 24 byte header incorporating the following information:
Field
Description
Value
0x00 - 0x03
Offset
Offset from EoH to first Unread CDR (4 Bytes)
0x04 - 0x07
Encoding
Basic Encoding Rule (BER) i.e. 1 (4 Bytes)
0x08 - 0x0b
Number of CDRs
Total number of CDRs in the file (4 Bytes)
0x0c - 0x0f
Number of read CDRs
Total number of read CDRs in the file (4 Bytes)
0x10 - 0x13
File size
Size of CDR file in bytes (4 Bytes)
0x14 - 0x17
Abstract Syntax Notation One (ASN.1) format definition version
ASN.1 definition version information (4 Bytes)
Contents:
EoF marker: No EoF marker
File name format:
GSN_
custom3 Format: This customer-specific file format encodes CDRs according to the following conventions:
Header: No header
Contents: …
EoF marker: No EoF marker
File name format:
GSN_
Important: The use of either custom2 or custom3 file formats imposes the following actions: - files are
generated with the .u file extension (indicating an unprocessed file to the billing system); - the GSS system deletes files
with .p extension as part of periodic clean-up.