Binary Configuration File Download; Encoding Mechanism - AudioCodes Mediant 2000 User Manual

User's Manual
6.4.1.2.2 Tables in the Uploaded ini File
Tables are grouped according to the applications they configure. For example, several
tables are required to configure SS7, and other tables are required to configure ATM
(if available).
When uploading the ini file, the policy is to include only tables that belong to
applications, which have been configured. (Dynamic tables of other applications are
empty, but static tables are not.)
documented in the applications' specific sections.
6.4.1.2.3 Secret Tables
A table is defined as a secret table if it contains at least one secret data field or if it
depends on such a table. A secret data field is a field that must not be revealed to the
user. An example of a secret field can be found in an IPSec application. The IPsec
tables are defined as secret tables because the IKE table contains a pre-shared key
field, which must not be revealed. The SPD table depends on the IKE table.
Therefore, the SPD table is defined as a secret table.
There are two major differences between tables and secret tables:
The secret field itself can not be viewed via SNMP, Web Server or any other tool.
ini File behavior: These tables are never uploaded in the ini File (e.g., 'Get INI-
File from WEB'). Instead, there is a commented title that states that the secret
table is present at the board, and is not to be revealed.
Secret tables are always kept in the board's non-volatile memory, and may be
over-written by new tables that should be provided in a new ini File. If a secret
table appears in an ini File, it replaces the current table regardless of its content.
The way to delete a secret table from a board is, for example, to provide an
empty table of that type (with no data lines) as part of a new ini File. The empty
table replaces the previous table in the board.
The lists of table parameters are provided in the Appendix, 'Table Parameters' on
page 369.
6.4.1.3

Binary Configuration File Download

The ini file contains sensitive information required for appropriate functioning of the
Mediant 2000. The ini file is uploaded to the Mediant 2000 or downloaded from the
gateway using TFTP or HTTP protocols. These protocols are unsecured (and thus
vulnerable to a potential hacker). Conversely, if the ini file is encoded, the ini file
would be significantly less vulnerable to outside harm.
6.4.1.3.1

Encoding Mechanism

The ini file to be loaded and retrieved is available with or without encoding. When an
encoded ini file is downloaded to the Mediant 2000, it is retrieved as encoded from the
Mediant 2000 as well. When a decoded file is downloaded to the Mediant 2000, it is
retrieved as decoded from the Mediant 2000 as well.
In order to create an encoded ini file, the user must first create an ini file and then
apply the DConvert utility to it in order to encode it. (Refer to ''Utilities'' on page
detailed instruction on ini file encoding.)
Version 5.0
6. Mediant 2000 Initialization & Configuration Files
The trigger for uploading tables is further
69
471 for
June 2006