User's Manual 428 Document #: LTRT-68822
Mediant 2000
field.
5. Connect each device to the network and then power up the device.
6. The BootP reply contains the cmp and ini file names entered in the 'BootP File' field.
Each device retrieves these files using BootP and stores them in its flash memory. If
auxiliary files are required (e.g., call progress tones), they may also be specified in the
ini file and downloaded from the same TFTP server.
7. When the devices' LEDs turn green indicating that the files were successfully loaded,
disconnect the devices and ship to the customer.
Notes:
• Typically, IP addressing at the customer site is done by DHCP.
• For more information on the AcBootP utility, refer to the AcBootP Utility User's
Guide.
34.4.2 DHCP-based Configuration Server
This method is similar to the setup described in 'Local Configuration Server with
BootP/TFTP' on page 427, except that DHCP is used instead of BootP. The DHCP server
can be configured to automatically provide each device with a temporary IP address so that
individual MAC addresses are not required. Configuration occurs at a staging warehouse
for this method.
Below is an example configuration file for Linux DHCP server (dhcpd.conf). The devices
are allocated temporary IP addresses in the range 10.31.4.53 to 10.31.4.75. TFTP is
assumed to be on the same computer as the DHCP server (alternatively, the "next-server"
directive may be used).
ddns-update-style ad-hoc;
default-lease-time 60;
max-lease-time 60;
class "gateways" {
match if(substring(hardware, 1, 3) = 00:90:8f);
}
subnet 10.31.0.0 netmask 255.255.0.0 {
pool {
allow members of "audiocodes";
range 10.31.4.53 10.31.4.75;
filename "SIP_F6.60A.217.003.cmp –fb;device.ini";
option routers 10.31.0.1;
option subnet-mask 255.255.0.0;
}
}
34.4.3 Configuration using DHCP Option 67
This method is suitable for deployments where DHCP server configuration is possible at
the customer site. 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 does not require additional servers at
the customer premises and is NAT-safe.
Below is an example of a Linux DHCP configuration file (dhcpd.conf) showing the required
format of Option 67:
To Next Page
Loading...
Need help?
General
