cdr_converter Module
The cdr_converter module reads CDR files, converts the raw data into Diameter packets and sends them to the Diameter Gateway so they can be processed. The processing includes checking for Diameter AVP mapping errors on the input CDR data.
Syntax
cdr_converter -C source_directory -D metadata_directory [-E earliest_timestamp] [-U 0|1] [-S leading_characters]
Options
- -C source_directory
- The pathname of the
top-level directory containing the CDR files. The cdr_converter module parses
all files in this directory and in any 2nd-level subdirectories. For example,
say you have a
/var/cdrs/MMS directory that contains the
following subdirectories:
- /09012013
- /09022013
To process CDR data files in both subdirectories, the top-level directory is /var/cdrs/MMS. To process CDR data files only in the /var/cdrs/MMS/09012013 directory, the top-level directory is /var/cdrs/MMS/09012013.
- -D metadata_directory
- The pathname of the directory in which to store rejected CDR files. The cdr_converter module saves the rejected files in the same directory location as the source data directory. The rejected files contain the rejected records along with a reason for each rejection.
- -E earliest_timestamp
- Specifies a timestamp to use as an upper boundary for valid CDRs. Any records having an earlier timestamp than the date and time provided will be rejected. The default is to use the timestamp value in the CDR.
- -U 0 | 1
- Rejection flag.
- -S leading_characters
- Removes the leading
characters, for example, zeros (00), from
BNumber
values that are longer than 15 digits. This is to handle valid B number that include Interactive Voice Response (IVR) digits that were entered as part of the called number. The first 15 digits after the leading characters are used as theBNumber
.