Provisioning From Tftp Server Using Dhcp Option 66; Http-Based Provisioning - AudioCodes Mediant 1000B User Manual

User's Manual
pool {
"INI=http://www.corp.com/master.ini";
}
}

37.1.1.2 Provisioning from TFTP Server using DHCP Option 66

This method is suitable when the network in which the device is deployed contains a
provisioning TFTP server for all network equipment, without being able to distinguish
between AudioCodes and non-AudioCodes devices.
Upon startup, the device searches for Option 66 in the DHCP response from the DHCP
server. If Option 66 contains a valid IP address, the device attempts to download, through
TFTP, a file that has a filename containing the device's MAC address (e.g.,
00908f0130aa.ini). This method requires a provisioning server at the customer premises.
This method loads the configuration file to the device as a one-time action. The download
is only repeated if the device is manually restored to factory defaults (by pressing the
hardware reset button while the Ethernet cable is not connected) and DHCP is enabled
(see note below).
Notes:
•
For TFTP configuration using DHCP Option 66, enable DHCP on your device:
DHCPEnable = 1 and DHCPRequestTFTPParams = 1.
•
Access to the core network using 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.

37.1.2 HTTP-based Provisioning

An HTTP or HTTPS server can be located in the network in which the device is deployed,
storing configuration and software files for the device to download. This does not require
additional servers and is NAT-safe.
For example, assume the core network HTTPS server is https://www.corp.com. A master
configuration
https://www.corp.com/gateways/master.ini. This file could point to additional ini files,
auxiliary files (e.g., call progress tones), and software files (cmp), all on the same HTTP
server or different HTTP servers in the network.
The main advantage of this method is that the device can be configured to periodically
check the HTTP server for file updates. HTTP(S) is not sensitive to NAT devices, enabling
configuration whenever needed without on-site intervention. For additional security, the
URL may contain a different port, and username and password.
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
staging warehouse. The URL is configured using the IniFileURL parameter.
Version 6.8
allow members of "audiocodes";
range 10.31.4.53 10.31.4.75;
option routers
option subnet-mask
option domain-name-servers
option bootfile-name
option dhcp-parameter-request-list 1,3,6,51,67;
ini file can
37. Automatic Update Mechanism
10.31.0.1;
255.255.0.0;
10.1.0.11;
be stored on
611 Mediant 1000B Gateway & SBC
the server,
609 or via TFTP at a
e.g.,