Http/S-Based Provisioning Using The Automatic Update Feature; Files Provisioned By Automatic Update - AudioCodes Mediant 800B MSBR User Manual

47.2 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. However, the device may also be
deployed without any initial configuration and then automatically provisioned by triggering
the Automatic Update feature using the Zero Configuration feature, discussed in detail in
Zero Configuration on page 646.
Notes:
•
For a description of all the Automatic Update parameters, see Automatic Update
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>.

47.2.1 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- the configuration file can be one of the following types, depending
on required configuration:
•
ini File: Contains ini file parameters only, which configures only System and VoIP
functionalities (not Data-Routing functionality).
•
CLI script files: Contains CLI commands related only to device configuration (not
commands such as show, debug or copy). The file can be used for configuring all
the device's functionalities (i.e., System, VoIP, and Data Routing). You can use
one of the following types of CLI script files, the only difference being the way that
they configure the device:
♦
User's Manual
CLI Script: The file updates the device's configuration only according to the
file's configuration settings. 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
The URL of the server where this file is located is configured by the
AUPDCliScriptURL ini file parameter or CLI command, configure system >
automatic-update > cli-script <URL>.
634
Mediant 800B MSBR
Document #: LTRT-12813