Filter
Top Products
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000
Version 4.4 87 July 2005
6 ini File Configuration of the Mediant 2000
As an alternative to configuring the VoIP gateway using the Web Interface (refer to Section 5 on
page 39), it can be configured by loading the ini file containing Customer-configured parameters.
The ini file is loaded via the BootP/TFTP utility (refer to
Appendix B on page 189) or via any
standard TFTP server. It can also be loaded through the Web Interface (refer to Section
5.9.5 on
page 69).
The ini file configuration parameters are stored in the Mediant 2000 non-volatile memory after the
file is loaded. When a parameter is missing from the ini file, a default value is assigned to that
parameter (according to the cmp file loaded on the Mediant 2000) and stored in the non-volatile
memory (thereby overriding the value previously defined for that parameter). Therefore, to restore
the default configuration parameters, use the ini file without any valid parameters or with a
semicolon (;) preceding all lines in the file.
Some of the Mediant 2000 parameters are configurable through the ini file only (and not via the
Web). These parameters usually determine a low-level functionality and are seldom changed for
a specific application.
6.1 Secured ini File
The ini file contains sensitive information that is required for the functioning of the Mediant 2000.
It is loaded to, or retrieved from, the device via TFTP or HTTP. These protocols are unsecured
and vulnerable to potential hackers. Therefore an encoded ini file significantly reduces these
threats.
You can choose to load an encoded ini file to the Mediant 2000. When you load an encoded ini
file, the retrieved ini file is also encoded. Use the ‘TrunkPack Downloadable Conversion Utility’ to
encode or decode the ini file before you load it to, or retrieve it from, the device. Note that the
encoded ini file’s loading procedure is identical to the regular ini file’s loading procedure. For
information on encoding / decoding an ini file, refer to Section
G.1.3 on page 217.
6.2 Modifying an ini File
To modify the ini file, take these 3 steps:
1. Get the ini file from the gateway using the Embedded Web Server (refer to Section 5.9.5 on
page 69).
2. Open the file (the file opens in Notepad or a Customer-defined text file editor) and modify the
ini file parameters according to your requirements. Save and close the file.
3. Load the modified ini file to the gateway (using either the BootP/TFTP utility or the
Embedded Web Server).
This method preserves the programming that already exists in the device, including special
default values that were preconfigured when the unit was manufactured.
Tip: Before loading the ini file to the gateway, verify that the extension of the ini
file saved on your PC is correct: Verify that the check box ‘Hide file extension
for known file types’ (My computer>Tools>Folder Options>View) is
unchecked. Then, confirm that the ini file name extension is xxx.ini and NOT
erroneously xxx.ini.ini or xxx~.ini.