Ftp- Or Nfs-Based Provisioning; Provisioning Using Audiocodes Ems; Http/S-Based Provisioning Using The Automatic Update Feature - AudioCodes MP-11x User Manual

33.1.6 FTP- or NFS-based Provisioning

Some networks block access to HTTP(S). The Automatic Update feature provides limited
support for FTP/FTPS connectivity. Periodic polling for updates is not possible since these
protocols do not support conditional fetching, i.e., updating files only if it is changed on the
server.
The only difference between this method and those described in ''HTTP-based
Provisioning'' on page 394 and Provisioning from HTTP Server using DHCP Option 67 on
page 393 is that the protocol in the URL is "ftp" (instead of "http").
Notes:
•
Unlike FTP, NFS is not NAT-safe.
•
NFS v2/v3 is also supported.

33.1.7 Provisioning using AudioCodes EMS

AudioCodes EMS server functions as a core-network provisioning server. The device's
SNMP Manager should be configured with the IP address of the EMS server, using one of
the methods detailed in the previous sections. As soon as a registered device contacts the
EMS server through SNMP, the EMS 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.
33.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 burn-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.
User's Manual
If you use the IniFileURL parameter for the Automatic Update feature, do
396
MP-11x & MP-124
Document #: LTRT-65432