Installing the VoIP Emergency Intercom
Parts List
Operations Guide
930279M
CyberData Corporation
59
To set up a Linux DHCPD server to serve autoprovisioning information (in this case using both
option 66 and 150), here's an example dhcpd.conf:
# dhcpd.conf
#
# Configuration file for ISC dhcpd (see 'man dhcpd.conf')
#
ddns-update-style ad-hoc;
option option-150 code 150 = ip-address;
subnet 10.0.0.0 netmask 255.0.0.0 {
max-lease-time 120;
default-lease-time 120;
option routers 10.0.0.1;
option subnet-mask 255.0.0.0;
option domain-name "voiplab";
option domain-name-servers 10.0.0.1;
option time-offset -8; # Pacific Standard Time
option tftp-server-name "10.0.0.254";
option option-150 10.0.0.254;
range 10.10.0.1 10.10.2.1;}
Autoprovisioning
Server (IP Address)
Instead of using DHCP to provide the autoprovisioning tftp server address, you can specify an
address manually.
Autoprovisioning
Autoupdate
If
Autoprovisioning
is enabled and the
Autoprovisioning Autoupdate
value is something other
than
0
minutes, a service is started on startup that will wait the configured number of minutes and
then try to re-download its autoprovisioning file. It will compare its previously autoprovisioned file
with this new file and if there are differences, it will reboot the board.
Autoprovisioned
Firmware Upgrades
An Autoprovisioned firmware upgrade only happens after a reboot, will take roughly three
minutes, and the web page will be unresponsive during this time.
The '
FirmwareVersion'
value in the xml file
must
match the version stored in the '
FirmwareFile
'.
<FirmwareVersion>v5.0.5b01</FirmwareVersion>
<FirmwareFile>505b01-uImage-intercom</FirmwareFile>
If these values are mismatched, the board can get stuck in a loop where it goes through the
following sequence of actions:
1. The board downloads and writes a new firmware file.
2. After the next reboot, the board recognizes that the firmware version does not match.
3. The board downloads and writes the firmware file again.
CyberData has timed a firmware upgrade at 140 seconds. Therefore, if you suspect the board is
stuck in a loop, either remove or comment out the
FirmwareVersion
line in the XML file and let the
board boot as it normally does.
