Polycom Configuration File Serial Will Enable

Available End User Poly services offerings are detailed here If this is some sort of an Internet discounter providing your MAC address or your Poly devices serial will enable us to look up who would be able to support you.

If the unit is no longer within the warranty please be prepared to Pay Per Incident PPI.

I am just a simple volunteer in the community like everybody else.

My official day Job is 3rd Level support at Poly but I am unable to provide official support via the community.

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.

If you need immediate andor official assistance please open a service ticket through your proper support channels.

Please also ensure you always check the VoIP, Video Endpoint, Skype for Business, PSTN or RPM FAQs.

Polycom Configuration File Archive But Within

Not sure I fully understand what you are trying to archive but within a configuration file you cannot call another configuration file.

Please consider this when utilizing any information referenced here.

The goal of this project were twofold: To completely eliminate the need for me to touch the phone to provision it.

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.

And To eliminate per-phone physical configuration files stored on the server.

The configuration files should be generated on the fly when the phone requests them.

So the flow of what happens is this: I create a profile for the phone in the database, then plug the phone in.

Script on the server hands out the correct provisioning path for that model of phone.

Polycom Configuration File Update SIP Application

Phone boots with new provisioning information, begins downloading update SIP application and BootROM.

Reboots. Phone boots again, connects to Asterisk.

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.

Its pretty neat. Note: there are some areas where this is intentionally vague, as Ive tried to avoid revealing too much about our private corporate administrative structure.

If something here doesnt make sense or youre curious, post a comment.

Creating the initial configs I used the standard download of firmware and configs from Polycom to seed a base directory.

This directory, on my server, is wwwasteriskprovpolycomipXXX, where XXX in the phone model.

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.

With the base configs in place, this is where modrewrite comes into play.

I added the following rewrite rules to the Apache configs: RewriteEngine on.

It requests the following files in this order: whichever bootrom.ld image its using, mac-address.cfg if it exists or 000000000000.cfg otherwise, the sip.ld image, mac-address-phone.cfg, mac-address-web.cfg, and mac-address-directory.xml.

So, were going to rewrite some of these requests to our scripts instead.

Generating configs on the fly Were going to skip the first rewrite rule (well talk about that one in a little bit since it has to do with plug-in auto provisioning).

The one were concerned with is the next one, which rewrites mac-address-phone.cfg requests to our provisioning script.

So each request to that file is actually rewritten to provision.phpmacmac-address.

Now, in the database, were keeping track of what kind of phone it is (an IP-330, IP-331 or IP-4000), so when a request hits the script, we look up in the database what kind of phone were dealing with based on the MAC address, and use the variables from the database to fill in a template file containing exactly what that phone needs to configure itself.

For example, the base template file for the IP-330 looks something like this.

A lot of the settings custom to the company and shared among the various phones are in a master dealnews.cfg file, and included with each phone (it was added to the 000000000000.cfg file).

Now, on to the next rule.

Generating the company directory Polycom phones support directories.

Theres a way to get this to work with LDAP, but I havent tackled that yet.

So, for now, we generate those dynamically as well when the phone requests any of its -directory.xml files.

This ones pretty easy since 1) we dont allow the endpoints to customize their directories (yet), and 2) because every phone has the same directory.

Polycom Configuration File Generator