View source for Provisioning via DHCP
From berofix - professional SIP gateway
= Prerequisites = * beroNet VoIP-Gateway (with enabled DHCP) * DHCP-Server (with support for setting option 66 / 67) * TFTP-Server = Setup = == DHCP == Configure your DHCP-Server to supply the Gateway with an TFTP-Servername (Option 66) and path (Option 67). Examples for common DHCP-Servers can be found here: * [http://www.3cx.com/sip-phones/dhcp-option-66/ Microsoft Windows Server] * [http://www.lubby.org/result.jsf?DB=lkb_linux_english&ID=97 ISC DHCPd under debian-based Distributions] Keep in mind to set '''only''' the path in Option 67! Do '''NOT''' append the file name ''conf-update.conf''! == TFTP == The configuration of your TFTP-Server depends on the server you are using. Please see the according manual. As we are working with ATFTPd, we have encountered the following options set in ''/etc/default/atftpd'' to work best: USE_INETD=false OPTIONS="--daemon --bind-address <ip-address> --verbose=0 /path/to/tftp/root" == Provisioning Files == The process of provisioning a beroNet Gateway is controlled by the file conf-update.conf. It's options are described here: [[Howto configure berofix with TFTP]] == beroNet VoIP Gateway == There is actually nothing to configure if you want to provision a Gateway delivered with a firmware newer then 3.0,<br /> as they are delivered with enabled DHCP. If you have a Gateway which uses static ip-address-assignment, you'll have to set it to DHCP and reboot your gateway.
Provisioning via DHCP
Retrieved from "
What links here
About berofix - professional SIP gateway