SPA112 Provisioning - not working...

Question

Hi,
We just purchased an SPA112 unit for testing before a large deployment.
There's a working provisioning setup in place for SPA303 devices using DHCP option 66 with an https URL. The provisioning of SPA303 phones wokrs just fine, SPA112 on the other hand simply won't parse DHCP 66 option properly.
The relevant sniffer output of the SPA112 unit provisioning attemtp with the DHCP 66 URL is attached here, it was tested with firmware 1.0.x (out of box) and after upgrade to 1.2.1 (004).
The clear conclusion is - ATA tries to use the full provisioning URL as a hostname (?!?!) of the provisioning server and resolve it via DNS... e.g. a DNS query for A record of "https://prov.server.com/devconf.cfg" is sent to the DNS server. Protocol name and path to file are not stripped, the whole string is treated as a hostname.
Is this a bug or behavior by design (which is hard to believe)?

Answer 1

Yes, I know it. It's great resource. Despite of it, it's hard to found information even in the case the administrator knows what he are looking for.
The main problem is - the documentation is spreaded over so many separate documents, application notes, technical notes, semi-official information in this forum and other resources. In most case, there is lack of information related to particular feature implementations. I wqant to use example to explain what I'm mean.
Have you configured sd+blf+cp function ? Are you interested to know when the button press will invoke 'sd' and when 'cp' ? Do you want to know if sd+blf (but no cp) combination of functions is possible ? Need to use vid=  ? (where you can found such parameter like vid= exists at all  ?) No answers avaiable in Admin Guide and no way to deduce answers by self as there are no implementation details. No reference to other document (not counting the reference to document specific for Broadsoft server). Yes, there may or may not be other document with such detailed description. The unfortunate customer need to read many and many documents and - there may but may not be the one with required description in such list.
The paragraph above show the example of problem only. And note the English is not my native language, so if it sounds so strong, then it's not intentional. I'm not trying to yell "it's crap" in any way. I'm trying to explain, using my poor language skills, the problem with 'task oriented' style of Cisco's documentation. I hope this comment will not be misunderstood.
I'm wishing to see a information-oriented style of documentation. Such kind of documentation is matter of course in the case of Cisco's switches. Especially I'm calling for index of all configuration keywords, with list of all possible values and their meaning, index of SIP NOTIFY Event, list of DHCP options recognized by device (can be time offset set by DHCP instead of provisioning or manual configuration ?) and so on ...