Features/Mass Deployment/DHCP/DHCP Server

From Snom User Wiki

Jump to: navigation, search

Contents

Introduction

snom phones use DHCP to receive network related parameters, see this general description. Professional DHCP servers can be configured to offer additional options to the network device sending the DHCP request. snom phones retrieve their setting (provisioning) URL from the values configured in option 43/66/67.

DHCP server installation

DHCP Options and Values

DHCP Server MUST be capable to provide one of the following option types:

Option 43 (vendor-encapsulated-options)

Firmware
Encapsulated Option 66 and Option 67 are supported since 7.3.17/8.2.1
Encapsulated Option 132 and Option 133 are supported since 7.3.24/8.2.7.
Description
Encapsulated DHCP options, for encoding see RFC 2132 Section 2. DHCP Option Field Format; One can tunnel vendor specific DHCP options depending on the vendor-id (option 60) send before from the phone to the DHCP server. Vendor specific DHCP options may be provided encapsulated in option 43, see RFC 2132 Section 8.4. Vendor Specific Information.
VALIDVALUE (Examples)
linux dhcpd3 syntax: 
option vendor-encapsulated-options
42:0c:68:74:74:70:3a:2f:2f:74:65:73:74:00:43:12:73:6e:6f:6d:2f:73:65:74:74:69:6e:67:73:2e:70:68:70:00;
Which means tunnel opt 66 http://test and opt 67 snom/settings.php via opt 43. 
option vendor-encapsulated-options
84:02:33:00;
Which means tunnel opt 132 value 3 via opt 43. 
option vendor-encapsulated-options
84:04:31:31:34:00:85:02:35:00;
Which means tunnel opt 132 value 114 and opt 133 value 5 via opt 43.

Option 60 (Vendor class identifier)

Description
This option is used by DHCP clients to optionally identify the vendor type and configuration of a DHCP client. The information is a string of n octets, interpreted by servers. Vendors may choose to define specific vendor class identifiers to convey particular configuration or other identification information about a client. For example, the identifier may encode the client's hardware configuration. Servers not equipped to interpret the class-specific information sent by a client MUST ignore it (although it may be reported). Servers that respond SHOULD only use option 43 to return the vendor-specific information to the client. The code for this option is 60, and its minimum length is 1.

Option 66 (TFTP server name)

Description
This option is used to identify a TFTP server when the 'sname' field in the DHCP header has been used for DHCP options. The code for this option is 66, and its minimum length is 1.
VALIDVALUE
<protocol> : // <IP address> or <domain> e.g. http://10.0.0.2, https://provisioning.company.com
<IP address> or <domain> e.g. 10.0.0.2, provisioning.company.com
where <protocol> = server type/protocol
where <IP address> = server IP address
where <domain> = server domain name
NOTE
Without specifying the <protocol> the firmware will attempt all supported server protocol types consecutively:
  1. tftp://...
  2. http://...
  3. https://...
SETTING
update_server

Option 67 (Bootfile name)

Description
This option is used to identify a bootfile when the 'file' field in the DHCP header has been used for DHCP options. The code for this option is 67, and its minimum length is 1.
VALIDVALUE
<path> e.g. settingfiles/snom/snom300.cfg, settingfiles/snom/snom320.htm, settingfiles/snom/snom360.xml
<empty> or <not used>
where <path> = path to the location of the setting file/script file
NOTE
If this option is empty or not specified at all the firmware automatically requests the following setting files, except the whole URL is encoded in option 66:
all snom300 phones request --> http://<domain>/snom300.htm
all snom320 phones request --> http://<domain>/snom320.htm
all snom360 phones request --> http://<domain>/snom360.htm
all snom370 phones request --> http://<domain>/snom370.htm
all snom820 phones request --> http://<domain>/snom820.htm
all snom870 phones request --> http://<domain>/snom870.htm
all snom MeetingPoint phones request --> http://<domain>/snommp.htm
SETTING
update_filename
Retrieved from "http://wiki.snom.com/Features/Mass_Deployment/DHCP/DHCP_Server"
Personal tools
VoIP Products
Interoperability