Connecting Poly devices to SimpleThree Provisioning

Applies to: SimpleTwo 1.0.46, SimpleThree Provisioning 0.10.0 · Checked: 02.11.2026

SimpleThree Provisioning (the prov role) is the provisioning server Poly phones and video systems fetch their configuration files from. A device learns the server's address once, shows up in the enrolment list, the administrator binds it to its site — and from then on it is configured from here. Everything is done in the console: SimpleThree → Provisioning → Poly devices.

1. Before you start

• A host with the prov role and a public name (for example prov.example.com). Everything runs on that name over HTTPS: the devices' files, administration from the console and the integration with SimpleTwo. The host needs no private address.
• A certificate for the name. The coordinator orders one (Let's Encrypt) or you import your own. The device must trust it: a public certificate needs nothing; one from the corporate CA needs the CA's root installed on the device first (device web interface → Security → Certificates).
• A console sign-in through the directory. The Poly devices card talks to prov through the console's gateway with your own account: the browser needs to reach the console only (see Console); a break-glass sign-in cannot.

2. How a device finds the server

The console's Poly devices card shows the exact addresses for your installation. Below, prov.example.com is an example.

Poly Trio and other UC Software phones

The provisioning server address is https://prov.example.com/poly.

By DHCP (convenient for many devices): option 160 (or 66) with the string https://prov.example.com/poly.

# ISC DHCP
option poly-prov code 160 = text;
option poly-prov "https://prov.example.com/poly";

In Windows DHCP, create predefined option 160 of type string with the same address.

By hand (once on the device): the phone's web interface → Settings → Provisioning Server: server type HTTPS, address https://prov.example.com/poly, user and password empty. Save — the phone restarts.

Poly Studio X and G7500 (VideoOS)

1. The system's web interface → General Settings → Provider → Poly Video.
2. Servers → Provisioning Server: enable, authentication Basic, address https://prov.example.com/ucservice, any non-empty user name and password.

The system appears in the enrolment list and can be bound; the server does not serve VideoOS configuration yet.

3. The enrolment window and binding

1. In the Poly devices card press Open for an hour. While the window is open the server records new devices; a closed window records none.
2. Restart the device. Within a few minutes it is listed under Waiting to be bound, with its MAC and the fingerprint of its factory certificate.
3. The sites are the directory's, one set for every platform: the same ones SimpleTwo's numbering plan and MCU use. Sites lists the directory's offices and data centres. If the one you need is missing, an administrator who may write the directory adds it: a name, a type (office or data centre), the country (RU), the city and the time zone (Europe/Moscow). A site no device is bound to can be removed; removing it removes it for every platform.
4. Pick the site in the device's row and press Bind. The device moves to Devices; on its next request it gets its configuration.
5. Close the window when everything you meant to connect is in (Close now) — or it closes by itself after an hour.

A device is recognised by its factory certificate: a phone with another certificate under the same MAC does not get this device's configuration.

4. Linking to a SimpleTwo meeting room

For a meeting-room phone to get its line to the MCU and the schedule panel's pages and key:

1. Switch the integration on: SimpleThree → Provisioning → Integration with SimpleTwo → Switch on. The coordinator calls prov on its public name and signs its requests with its own key — there are no tokens to set up.
2. In the room's card in SimpleTwo, pick the bound device. The parameters SimpleTwo writes are marked in the device's configuration as managed by SimpleTwo.

More on meeting rooms: Meeting rooms and SIP terminals.

5. Profiles: device parameters and Zoom

The Poly profiles card manages the devices' parameters. A configuration is put together from profiles, widest to narrowest — everywhere, a country, a site, a model, a purpose, a room, the device itself; a narrower profile overrides a wider one. Trio (UC Software) and Studio X / G7500 (VideoOS) have profiles of their own — the family switch at the top of the card.

1. New profile → a name, a layer (for example "A site") and what it applies to.
2. Quick settings fill the usual parameters:
   • Studio X, G7500: Zoom Rooms — one tick (management.provider.select="Zoom Rooms"); the conferencing provider (Poly Video, Microsoft Teams, Zoom Rooms and others), the room name on screen, the language, the time zone, automatic updates and their window.
   • Trio: the Zoom Rooms controller (Generic base profile and the app switcher), the base profile, the menu language, the time server.
   • Trio: Zoom calls over SIP. A second line beside SimpleTwo's: the phone shows a "Zoom" key (the name can be changed). Pick it and dial the meeting's ID — the phone calls <ID>@zoomcrc.com; a meeting with a passcode is <ID>.<passcode>, or the passcode as tones once answered. The line does not register (reg.2.server.1.register="0"), TLS on 5061 by default, TCP on 5060 if needed. It needs Zoom's H.323/SIP Room Connector licence on the Zoom account. Line 1 stays SimpleTwo's. Studio X and G7500 in Poly Video mode call Zoom the same way — dial <ID>@zoomcrc.com, nothing to set.
3. All parameters of this profile — a table: any parameter is set by its name from Poly's reference; the "remove a wider value" tick takes away what a wider profile set.
4. Preview on this device — what the device gets with the draft and where each value comes from; then Save.

Parameters SimpleTwo writes for a linked meeting room are marked "managed by SimpleTwo" and a device profile does not override them. The server does not serve VideoOS configuration yet (section 2): Studio X profiles can be prepared ahead.

6. Updating the firmware

1. Download Poly's software package for the model. For a Trio it is the UC Software package, with a <part number>.sip.ld file per model (for example 3111-66420-001.sip.ld — Trio C60).
2. The Poly firmware card: the model, the version (as Poly names it, for example 7.2.6.0123), the file and, optionally, the SHA-256 from the package's notes → Upload. The server checks the checksum and keeps nothing if it does not match.
3. In Poly profiles pick the Firmware version: on the profile for everywhere for every device of the family; on a site, a model or one device to update those first (a staged rollout).
4. A Trio updates on its next configuration check (or after a restart). What a device runs now is in the Firmware column of the devices list and in the preview ("runs … · wanted …").

Only a bound device of the model an image was uploaded for gets it. If the model has no image of that version, the device stays on its firmware and the preview says "no image". For Studio X and G7500 images and the version are set the same way; delivery starts with their provisioning.

7. Troubleshooting

Symptom	Cause	What to do
The device never shows under Waiting to be bound	the window is closed, the device does not reach the server, or it does not trust the certificate	open the window; check the address on the device; for a corporate CA certificate install the root on the device
The card says "does not answer through the console"	the console cannot reach prov's public name (DNS, firewall, prov's certificate), or the console's network is not among those the control API admits	check that https://<prov's name>/control/about opens from the console's host (the coordinator's): a 401 or 403 means the network is fine; check Settings → Console and control API
"sign in through the directory…"	the console was opened with a break-glass sign-in	sign in through the directory
Integration: "prov has no public name yet"	the prov host has no public name	set one: Servers → Configure
Integration: 401 from prov	prov is older than 0.10.0, or the host has not received the coordinator's key registry yet	wait for the role to update (a few minutes after the release)