Cisco Cisco Tunnel Terminating Gateway (TTG) Manuel De L’Administrateur
GTPP Accounting Overview
Charging Records ▀
Cisco ASR 5x00 GTPP Interface Administration and Reference ▄
29
Important:
Remember that the unprocessed CDR (*.u) files should never be deleted from
HDD.
custom3 Format: This customer-specific file format encodes CDRs according to the following conventions:
Header: No header
Contents:
CDR1CDR2CDR3
…
CDRn
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
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|
where | represents the end of a 2K block
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
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:
CDR1CDR2CDR3
…
CDRn
EoF marker: No EoF marker
File name format:
<node-id-suffix+vpn-id>_<date>+<time>_<total-cdrs>_file<fixed-length-
seqnum>.u
seqnum>.u
Example:
default3_07_15_2009_08_09_25_4_file000003.u
custom6 Format: This file format is similar to custom4 file format except CDRs will be written in 8Kbyte
blocks in a file.
Header: No Header
Contents: CDR1|CDR2FFFFFF|CDR3FFFFF..|..CDRnFFFF|
where | represents the end of a 8K block