Cisco Cisco Tunnel Terminating Gateway (TTG) Administrator's Guide
GTPP Accounting Overview
▀ Charging Records
▄ Cisco ASR 5x00 GTPP Interface Administration and Reference
28
introduced to enable this feature. This feature is disabled by default to ensure backward compatibility. For more
information on this command, see Cisco ASR 5x00 Command Line Interface Reference.
information on this command, see Cisco ASR 5x00 Command Line Interface Reference.
File Format for CDRs
The file format determines the information organization and structure -- format -- of the generated data files. All file
formats are different and are customizable.
formats are different and are customizable.
The following file formats are supported for CDRs:
custom1 Format: This file format encodes CDRs according to the following conventions:
Header: No header
Contents:
CDR1CDR2CDR3
…
CDRn
EoF marker: \n
File name format:
<node-id-suffix+vpn-id>_<date>+<time>_<total-cdrs>_file<fileseqnum>
The
<fileseqnum>
denotes the file sequence number ranging from 1 through 4294967295.
Example:
default3_07_15_2009+07_53_02_5_file1
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:
LEN1CDR1LEN2CDR2LEN3CDR3...LENnCDRn
EoF marker: No EoF marker
File name format:
<node-id-suffix+vpn-id>_<date>+<time>_<total-cdrs>_file<fileseqnum>.u
The
<fileseqnum>
denotes the file sequence number ranging from 1 through 4294967295.
Example:
default3_07_15_2009_07_59_32_5_file2.u
Important:
With file format custom2, the files are generated with .u file extension indicating
an unprocessed file by the billing system. Typically, the billing system would rename the file with .p
extension after processing the files with CDR information.
extension after processing the files with CDR information.