CHAPTER37 Loading Auxiliary Files
Mediant 4000 SBC | User's Manual
37 Loading Auxiliary Files
You can load Auxiliary files to the device using any of the following methods:
■ Web interface - see Loading Auxiliary Files through Web Interface
■ CLI - see Loading Auxiliary Files through CLI
■ One Voice Operations Center (OVOC) – refer to the OVOC User’s Manual
The types of Auxiliary files are listed below.
Table 37-1: Auxiliary Files
File Description
INI Configures the device. The Web interface enables practically full device
provisioning. However, some features may only be configured by ini file or you
may wish to configure your device through ini file. For more information, see INI
File-Based Management.
Call
Progress
Tones
Region-specific, telephone exchange-dependent file that contains the Call
Progress Tones (CPT) levels and frequencies for the device. The default CPT
file is U.S.A. For more information, see Call Progress Tones File.
Prerecorded
Tones
The Prerecorded Tones (PRT) file enhances the device's capabilities of playing
a wide range of telephone exchange tones that cannot be defined in the CPT
file. For more information, see Prerecorded Tones File.
Dial Plan Provides dialing plans.
Note: Load a Dial Plan file using the Auxiliary Files page only for backward
compatibility; otherwise, import Dial Plan files using the Dial Plan table (see
Configuring Dial Plans on page462).
User Info Loads a User Information file.
Note: Load a User Information file using the Auxiliary Files page only for
backward compatibility; otherwise, load the file or configure users in the User
Information table for SBC users (see Configuring SBC User Information Table
through Web Interface on page448).
AMD
Sensitivity
Answer Machine Detector (AMD) Sensitivity file containing the AMD
Sensitivity suites. For more information, see AMD Sensitivity File.
SBC Wizard
Template
Package
Contains the vendor-interoperability configuration templates for the SBC
Configuration Wizard. For more information, see SBC Configuration Wizard.
● You can automatically load Auxiliary files from a remote server, using the device's
Automatic Update mechanism (see Automatic Update Mechanism).
● Saving Auxiliary files to flash memory may disrupt current traffic on the device. To
avoid this, disable all traffic on the device by performing a graceful lock (see
Locking and Unlocking the Device).
Loading Auxiliary Files through Web Interface
The following procedure describes how to load Auxiliary files through the Web interface.
- 664 -