AudioCodes Mediant 500L - Provisioning the Device Using DHCP Option 160

User's Manual 832 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
using the following ini file parameter:
DHCPRequestTFTPParams = 1
3. Reset the device with a save-to-flash for your settings to take effect.
Note:
• Access to the core network through TFTP is not NAT-safe.
• The TFTP data block size (packets) when downloading a file from a TFTP server
for the Automatic Update mechanism can be configured using the
AUPDTftpBlockSize parameter.
48.1.1.3 Provisioning the Device using DHCP Option 160
You can provision the device using DHCP Option 160. DHCP Option 160 provides the
device with the URL address of the provisioning server from where it can download its
software (.cmp) and configuration (.ini) files. The URL can also include the names of the
required files to download and their folder location on the server.
If you enable DHCP client functionality with DHCP Option 160, upon a device reset or
power up, the device (as a DHCP client) sends a DHCP request to the DHCP server to
obtain networking information (e.g., the device's IP address) and the URL address of the
provisioning server.
 The following syntax is supported for defining the URL and configuration/firmware
filenames in DHCP Option 160 (on the DHCP server):
 <protocol>://<server IP address or hostname>
 <protocol>://<server IP address or hostname>/<software filename>
 <protocol>://<server IP address or hostname>/;<configuration filename>
 <protocol>://<server IP address or hostname>/<software filename>;<configuration
filename>
The protocol can be HTTP, HTTPS, FTP, or TFTP. As shown above, the URL can include
both the software and configuration filenames. In this case, they must be separated by a
semicolon (;) and without spaces.
If the URL does not specify a configuration filename or the file does not exist on the
provisioning server, the device requests from the server a "default" configuration file whose
name includes the device's product name and MAC address (<Product><MAC>.ini, for
example, "M800B00908f5b1035.ini"). If this "default" file also does not exist on the server,
the device attempts to retrieve another "default" configuration file whose name includes
only the device's product name (<Product>.ini, for example, "M800B.ini"). The device
makes up to three attempts to download the configuration file if a failure occurs (i.e., file not
exist or any other failure reason). This applies to each of the configuration files, as
mentioned previously.
If the URL specifies a software file, the device makes only one attempt to download the file
(even if a failure occurs). If the URL does not specify a software file, the device does not
make any attempt to download a software file.
Once the device downloads the file(s), it undergoes a reset to apply the configuration
and/or software. In addition, once the file(s) has been downloaded, the device ignores all
future DHCP Option 160 messages. Only if the device is restored to factory defaults will it
process Option 160 again (and download any required files).
 To enable provisioning using DHCP Option 160:
1. Make sure that the DHCP server is configured with the appropriate information
(including the URL address of the provisioning server for Option 160).
2. Make sure that the required configuration and/or software files are located on the