Provisioning From Http Server Using Dhcp Option 67; Provisioning From Tftp Server Using Dhcp Option 66 - AudioCodes Mediant 3000 User Manual

User's Manual
Notes:
•
If the DHCP server denies the use of the device's current IP address and specifies
a different IP address (according to RFC 1541), the device must change its
networking parameters. If this occurs while calls are in progress, they are not
automatically rerouted to the new network address. Therefore, administrators are
advised to configure DHCP servers to allow renewal of IP addresses.
•
If the device's network cable is disconnected and then reconnected, a DHCP
renewal is performed (to verify that the device is still connected to the same
network). The device also includes its product name in the DHCP Option 60
Vendor Class Identifier. The DHCP server can use this product name to assign an
IP address accordingly.
•
After power-up, the device performs two distinct DHCP sequences. Only in the
second sequence is DHCP Option 60 included. If the device is software reset
(e.g., from the Web interface or SNMP), only a single DHCP sequence containing
Option 60 is sent.

39.2.3 Provisioning from HTTP Server using DHCP Option 67

Most DHCP servers support the configuration of individual DHCP option values for different
devices on the network. The DHCP configuration should be modified so that the device
receives a URL to the configuration file in Option 67, along with IP addressing and DNS
server information. The DHCP response is processed by the device upon startup and the
device automatically downloads the configuration file from the HTTP server specified in the
DHCP response. This method is NAT-safe.
Below is an example of a Linux DHCP configuration file (dhcpd.conf) showing the required
format of Option 67:
ddns-update-style ad-hoc;
default-lease-time 3600;
max-lease-time 3600;
class "audiocodes" {
match if(substring(hardware, 1, 3) = 00:90:8f);
}
subnet 10.31.0.0 netmask 255.255.0.0 {
pool {
"INI=http://www.corp.com/master.ini";
}
}

39.2.4 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.
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;
39. Automatic Update Mechanism
10.31.0.1;
255.255.0.0;
10.1.0.11;
623 Mediant 3000