| -csv |
|
Selects CSV file output. |
| -xml |
|
Selects XML file output. |
| <filename> |
|
<filename> is the name of
the input message to decode. This element is required. The use of
wildcards like * and ? is supported. |
| -schema |
<filename> |
This option is required when using CSV or decoding PER
data. When converting BER data to XML, a schema is not
required; ASN2TXT will convert the data using tag names.
|
| -bitsfmt |
<hex | bin> |
-bitsfmt may be used to specify how
BIT STRING items are formatted. By
default they are expressed as hexadecimal strings; use
bin to express them as binary strings
instead. |
| -inputFileType |
<binary | hextext | base64> |
-inputFileType may be used to tell
ASN2TXT how the input data are formatted. By default
ASN2TXT will assume that the input data are binary, but
it can also decode hexadecimal or base64 encoded data.
Whitespace in the input is ignored when
hextext is specified. |
| -lickey |
<key> |
In Linux, Macintosh, and Windows systems, license
checking is performed by the Reprise License Manager.
This option permits command-line license activation.
This option is compiled out for operating systems that
do not support the RLM license. |
| -noopentype |
|
This option disables the conversion of open types in
the output. This is the default behavior when converting
BER to CSV. |
| -paddingbyte |
<hexbyte> |
<hexbyte> is the
hexadecimal value of a padding byte that may appear in
the input message. Call data records (CDRs) are commonly
continuously dumped to files by telephony equipment. If
no information is available, the records are padding,
normally by 0x00 or 0xFF bytes. The default padding byte
is 0x00.
<hexbyte> may be formatted
with or without a 0x prefix. |
| -pdu |
<typename> |
<typename> is the name of
the PDU data type to be decoded. This option is
necessary when the top-level data type is ambiguous. It
is also required when converting PER data. |