User`s manual

H.323 User's Manual 5. Web Management
Version 5.0 191 December 2006
5.8.2.2 Loading the Auxiliary Files via the ini File
Before you load the configuration files (Call Progress Tones, Prerecorded Tones, FXS/FXO
Coefficient, and CAS) to the gateway, in the ini file you need to define certain ini file
parameters associated with these files. These ini file parameters specify the files that you
want loaded and whether they must be stored in the non-volatile memory.
For a description of the ini file parameters associated with the configuration files, refer to
Section 6.5.13 on page 251.
¾ To load the auxiliary files via the ini file, take these 3 steps:
1. In the ini file, define the auxiliary files to be loaded to the Mediant 1000. You can also
define in the ini file whether the loaded files should be stored in the non-volatile
memory so that the TFTP process is not required every time the Mediant 1000 boots
up. (See note below.)
2. Locate the auxiliary files you want to load and the ini file in the same directory.
3. Invoke a BootP/TFTP session; the ini and auxiliary files are loaded onto the Mediant
1000.
5.8.3 Updating the Software Upgrade Key
Mediant 1000 gateways are supplied with a Software Upgrade Key already pre-configured
for the gateway.
You can later upgrade their Mediant 1000 features, capabilities and quantity of available
resources by specifying what upgrades are required, and purchasing a new key to match
their specification.
The Software Upgrade Key is sent as a string in a text file, to be loaded into the Mediant
1000. Stored in the device’s non-volatile flash memory, the string defines the features and
capabilities allowed by the specific key purchased by the user. The device allows you to
utilize only these features and capabilities. A new key overwrites a previously installed key.
For detailed information on the Software Upgrade Key, refer to Section 11.7 on page 312.