Tftp Configuration Using Dhcp Option 66; Http-Based Automatic Updates - AudioCodes Mediant 800B User Manual

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

40.3.3 TFTP Configuration using DHCP Option 66

This method is suitable when the customer's network 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 with a name that contains 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.

40.3.4 HTTP-based Automatic Updates

An HTTP or HTTPS server can be placed in the customer's network where configuration
and software updates are available for download. This does not require additional servers
at the customer premises and is NAT-safe. For example, assume the core network HTTPS
server is https://www.corp.com. A master configuration ini file should be placed on the
server, e.g., 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 HTTP configuration can be checked
periodically when the device is deployed at the customer site. 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 devices should only be preconfigured with the URL of the initial ini file, using one of the
following methods:

Methods described in ''DHCP-based Configuration Server'' on page
TFTP at a staging warehouse. The configuration URL is configured using the
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;
40. Automatic Update Mechanism
10.31.0.1;
255.255.0.0;
10.1.0.11;
615 Mediant 800B Gateway and E-SBC
613 or above, via