I added the following rewrite rules to the Apache configs: RewriteEngine on RewriteRule ^/000000000000\.cfg /index.php RewriteRule /prov/ /( )-phone\.cfg /provision.php?mac=$1 RewriteRule /prov/polycom_ / -directory\.xml /prov/polycom_directory.php` RewriteCond % In this case, what we’ve done is look for a MAC address in Polycom’s space (00:04:f2) and pass it option 66 with our boot server. With the base configs in place, this is where mod_rewrite comes into play. This directory, on my server, is /While right now the IP-330 and IP-331 can use the same firmware and configs, since the IP-330 has been discontinued they will probably diverge sometime in the not too near future. Creating the initial configs I used the standard download of firmware and configs from Polycom to seed a base directory. If something here doesn’t make sense or you’re curious, post a comment. **Note: **there are some areas where this is intentionally vague, as I’ve tried to avoid revealing too much about our private corporate administrative structure. At this rate, provisioning a phone for a new employee is simply me entering the new extension and MAC address into an admin screen, and giving them the phone. Phone boots with new provisioning information, begins downloading update SIP application and BootROM. Reboots with new provisioning information. Script on the server hands out the correct provisioning path for that model of phone. Phone boots initially, receives server from DHCP option 66. ![]() So the flow of what happens is this: I create a profile for the phone in the database, then plug the phone in. The configuration files should be generated on the fly when the phone requests them. And… To eliminate per-phone physical configuration files stored on the server. I want to be able to create a profile for it in the database, then simply plug the phone in and let it do the rest. The goal of this project were twofold: To completely eliminate the need for me to touch the phone to provision it.
0 Comments
Leave a Reply. |