Snomphones are very good option if you are looking for feature-rich VoIP phones for Lync infrastructure.
But it is not that easy to provision them, when you have more than several units. Snow is keen to provide a solution here but their wiki is for Linux environment, which is not always the case when you have MS Lync based infrastructure :)
So I'd like to share my experience setting up auto provisioning services for Snom phones in UC edition. (btw, there should be an option to provision Snom phones using normal Lync device update procedure with ucupdates.cab soon).
But for now let us look at what do we have in generic Lync-deployed environment: some servers with IIS installed and DHCP server where by means of netsh script you have created MS-UC-Client vendor extensions with options to provide provisioning for Lync Phone Edition based phones (more on this can be found here or on technet along with aforementioned netsh script)
According to Snom wiki we need to create some 66 and 67 DHCP options. In our case standard options 66 and 67 are occupied but it is worth mentioning Snom UC edition firmware is presents itself as MS-UC-Client, which is perfectly fine, because we can add options 66 and 67 as vendor specific.
Snom recommends to use http for provisioning, and if the server is http://snom-provisioning.domain.com, then netsh commands to create additional records will be the following:
But it is not that easy to provision them, when you have more than several units. Snow is keen to provide a solution here but their wiki is for Linux environment, which is not always the case when you have MS Lync based infrastructure :)
So I'd like to share my experience setting up auto provisioning services for Snom phones in UC edition. (btw, there should be an option to provision Snom phones using normal Lync device update procedure with ucupdates.cab soon).
But for now let us look at what do we have in generic Lync-deployed environment: some servers with IIS installed and DHCP server where by means of netsh script you have created MS-UC-Client vendor extensions with options to provide provisioning for Lync Phone Edition based phones (more on this can be found here or on technet along with aforementioned netsh script)
According to Snom wiki we need to create some 66 and 67 DHCP options. In our case standard options 66 and 67 are occupied but it is worth mentioning Snom UC edition firmware is presents itself as MS-UC-Client, which is perfectly fine, because we can add options 66 and 67 as vendor specific.
Snom recommends to use http for provisioning, and if the server is http://snom-provisioning.domain.com, then netsh commands to create additional records will be the following:
netsh dhcp server add optiondef 66 ProvSrv Binary 0 Vendor=MSUCClient comment="Snom Provisioning Server"
netsh dhcp server set optionvalue 66 binary vendor=MSUCClient 687474703a2f2f736e6f6d2d70726f766973696f6e696e672e646f6d61696e2e636f6d
I used http://www.asciitohex.com/ to convert server name to hex format (just check you don't convert Enter (NewLine - Carriage Return) along with your string, otherwise don't forget to remove 0d0a from the end of hex line)
In my case I like that phones look for their respective model configuration file in the root folder of the server and I don't need option 67, but if you have subfolders with configs then you need to create option 67 also.
netsh dhcp server add optiondef 67 ProvPath Binary 0 Vendor=MSUCClient comment="Snom Provisioning path"
netsh dhcp server set optionvalue 67 binary vendor=MSUCClient 736e6f6d2f736e6f6d2e68746d
I used default IIS server to host Snom provisioning files along with firmwares for every model.