3Com VCX V7122 Installation Manual page 48

48 C 7: U
HAPTER PGRADING THE
V7122 M G
EDIA ATEWAYS
provisioning. Table 13
auxiliary files.
ini and Auxiliary Files Descriptions
Table 13
File Type
ini
CAS
Dial Plan
Voice Prompts
Call Progress Tones This is a region-specific, telephone exchange-dependent file
Prerecorded Tones
User Information
To load an auxiliary file via the Embedded Web Server, perform these
steps:
1 Open the Auxiliary Files screen (Software Update menu > Load
Auxiliary Files); the Auxiliary Files screen is displayed (see
2 Click the Browse button corresponding to the type of file you want to
load.
presents a brief description of the ini file and the
Description
Load this file to provision the V7122 parameters. The
Embedded Web Server enables practically full device
provisioning but customers may occasionally require new
feature configuration parameters in which case this file is
loaded.
Note that loading the ini file only provisions parameters that
are contained in the ini file. If a parameter is not specified in
the ini file, values associated with that parameter are reset to
a default value. These values may not be the same as the
values that were configured for the VoIP gateway at the time
of manufacture.
Note: After the file has completed loading, the VoIP
gateway automatically restarts (software is loaded from the
flash).
(Only applicable for digital interfaces.) Up to eight different
CAS files containing specific CAS protocol definitions.
These files are provided to support various types of CAS
signaling.
The Dial Plan file.
The voice announcement file contains a set of Voice Prompts
to be played by the V7122 during operation on Call Agent
request.
that contains the Call Progress Tones levels and frequencies
that the VoIP gateway uses. Default CPT file: U.S.A.
The dat PRT file enhances the gateway's capabilities of
playing a wide range of telephone exchange tones that
cannot be defined in the Call Progress Tones file.
The User Information file maps PBX extensions to IP
numbers. This file can be used to represent PBX extensions as
IP phones in the global 'IP world'.
Figure 22).