Http/S-Based Provisioning Using The Automatic Update Feature; Files Provisioned By Automatic Update - AudioCodes Mediant 4000 SBC User Manual

Session border controllers
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

CHAPTER 40    Automatic Provisioning
HTTP/S-Based Provisioning using the Automatic
Update Feature
The Automatic Update feature can be used for automatic provisioning of the device through
HTTP/S. Automatic provisioning is useful for large-scale deployment of devices. In some cases,
the devices are shipped to the end customer directly from the manufacturer. In other cases, they
may pass through a staging warehouse. Configuration may occur at the staging warehouse or at
the end-customer premises.
The device may be preconfigured during the manufacturing process (commonly known as private
labeling). Typically, a two-stage configuration process is implemented whereby initial configuration
includes only basic configuration, while the final configuration is done only when the device is
deployed in the live network.
If you use the IniFileURL parameter for the Automatic Update feature, do not use the
Web interface to configure the device. If you do configure the device through the Web
interface and save (burn) the new settings to the device's flash memory, the IniFileURL
parameter is automatically set to 0 and Automatic Updates is consequently disabled.
To enable Automatic Updates again, you need to re-load the ini file (using the Web
interface or BootP) with the correct IniFileURL settings. As a safeguard to an
unintended save-to-flash when resetting the device, if the device is configured for
Automatic Updates, the 'Burn To FLASH' field under the Reset Configuration group in
the Web interface's Maintenance Actions page is automatically set to No by default.

Files Provisioned by Automatic Update

You can use the Automatic Update feature to update the device with any of the following files:
Software file (cmp)
Auxiliary files (e.g., Call Progress Tones, SSL Certificates, SSL Private Key)
Configuration file:
ini File: Contains only ini file parameters and configures all the device's functionality.
CLI Script File: Contains only CLI commands and configures all the device's
functionalities (except commands such as show, debug or copy). The file updates the
device's configuration only according to the configuration settings in the file. The device's
existing configuration settings (not included in the file) are retained. The device does not
undergo a reset and therefore, this file typically contains configuration settings that do not
require a device reset. If a reset is required, for example, to apply certain settings, you
must include the following CLI command (root level) at the end of the file:
# reload if-needed
To configure the URL of the server where the file is located, use the CliScriptURL ini file
parameter or CLI command, configure system > automatic-update > cli-script <URL>.
For a description of all the Automatic Update parameters, see
Parameters
or refer to the CLI Reference Guide.
For additional security, use HTTPS or FTPS. The device supports HTTPS (RFC
2818) and FTPS using the AUTH TLS method <draft-murray-auth-ftp-ssl-16>.
- 697 -
Mediant 4000 SBC | User's Manual
Automatic Update

Advertisement

Table of Contents
loading

Table of Contents