Provisioning Using Audiocodes Ovoc; Http/S-Based Provisioning Using The Automatic Update Feature; Files Provisioned By Automatic Update - AudioCodes Mediant 500L User Manual

Enterprise session border controller (e-sbc) & media gateway
Hide thumbs Also See for Mediant 500L:
Table of Contents

Advertisement

48.1.4 Provisioning using AudioCodes OVOC

AudioCodes OVOC server functions as a core-network provisioning server. The device's
SNMP Manager should be configured with the IP address of the OVOC server, using one
of the methods detailed in the previous sections. As soon as a registered device contacts
the OVOC server through SNMP, the OVOC server handles all required configuration
automatically, upgrading software as needed. This alternative method doesn't require
additional servers at the customer premises, and is NAT-safe.
48.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.
Warning:
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.
Note:
For a description of all the Automatic Update parameters, see ''Automatic Update
Parameters'' on page
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>.

48.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:
ini File: Contains only ini file parameters and configures all the device's
functionalities, except Data-Routing.
User's Manual
If you use the IniFileURL parameter for the Automatic Update feature, do
1016
or refer to the CLI Reference Guide.
834
Mediant 500L Gateway & E-SBC
Document #: LTRT-10532

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents