AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 809 / 1248

Version 7.2 809 Mediant 500 MSBR
User's Manual 51. Automatic Provisioning
The only configuration required is to preconfigure the device(s) with the URL of the initial
(master) ini file. This can be done using one of the following methods:

DHCP, as described in DHCP-based Provisioning on page 807 or via TFTP at a
staging warehouse. The URL is configured using the IniFileURL parameter.

Private labeling (preconfigured during the manufacturing process).


Manually on-site, using the RS-232 port or Web interface.
When the device is deployed at the customer site, local DHCP server provides the devices
with IP addressing and DNS server information. From the URL provided in the DHCP
response, the device can then contact the HTTP server at the core network and
automatically download its configuration. The URL can be a simple file name or contain the
device's MAC or IP address, e.g.:

http://corp.com/config-<MAC>.ini - which becomes, for example,
http://corp.com/config-00908f030012.ini

http://corp.com/<IP>/config.ini - which becomes, for example,
http://corp.com/192.168.0.7/config.ini
For more information on HTTP-based provisioning, see HTTP/S-Based Provisioning using
the Automatic Update Feature on page 809.
51.1.3 FTP-based Provisioning
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 they are changed on the server).
The only difference between FTP-based provisioning and those described in HTTP-based
Provisioning on page 808 is that the protocol in the URL is "ftp" (instead of "http").
51.1.4 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.
51.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 822.