For this, Polycom Phone Support Module 5.1.0 (or higher) and Fusion 3.x.x is required.
All versions (except the latest one) are available on Polycom's site under the "sip download matrix" at: phones are end of support and need older software package.
For this method, you will not need to modify any default configuration files because this file will contain the entire phone's configuration.
For this example, we will use 000411223344 as our phone's MAC address.
Generate your CA certificate, remove all the headers and trailers, concatanate to one line and place it here. Each phone has three specific configuration files which are named accoring to its MAC address.
Note: The certificate is broken here into multiple lines. For example, if we say mac.cfg, and the mac address is 000411223344 then the file name is: 000411223344I've found this to be the simplest method for provisioning a Polycom.
As for the firmware and config files, they are stored in the user's temp folder.By default the phone will look for a file called 000411223344In this file, we can override ALL of the previously loaded variables. We set the NTP server, time to EST, enable presence, set voicemail call back to *1, and fill in the authentication credentials needed.This was tested on firmware 4.0.3 but I've also tested it on 3. 000411223344-phone.cfg: Here we have some basic configurations.What provisioning means is that in addition to the option of configuring the device through its web interface, you can instead point the phone at some kind of file transport server on the network (TFTP, HTTP(S), FTP(S)), where the phone will first try and download a device specific configuration file (based on its MAC address), then failing that, download a generic 000000000000 configuration file to setup defaults.These configuration files need to do a couple basic things.
We set the NTP server, time to EST, enable presence, set voicemail call back to *1, and fill in the authentication credentials needed.