AudioCodes Mediant 500 E-SBC, User Manual

Page: 586 / 920

User's Manual 586 Document #: LTRT-10437
Mediant 500 E-SBC
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 583 or via TFTP at a
staging warehouse. The URL is configured using the IniFileURL parameter.

Private labeling (preconfigured during the manufacturing process).

Using DHCP Option 67 (see Provisioning from HTTP Server using DHCP Option 67
on page
584 ).

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
587 .
40.1.5 FTP- 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
585 and Provisioning from HTTP Server using DHCP Option 67 on
page 584 is that the protocol in the URL is "ftp" (instead of "http").
40.1.6 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.