Phone Provisioning

Provisioning is how a phone learns its SIP credentials, line assignments, and other settings without anyone typing them in by hand. As a platform admin you decide which method your accounts' phones will use — the choice is usually the same across your whole fleet, and your account-admins do not need to think about it once it is in place.

If you are moving customer-owned phones over from another provider, see Migrating Existing Phones for the full procedure (factory reset, previous-provider locks, rollback).

Supported devices

Provisioning supports phones from these vendors:

Vendor	Model lines	Zero-touch
Snom	D-series deskphones; M-series DECT (base stations and handsets)	Yes
Yealink	T-series deskphones; W70B DECT base station and its handsets	No
Poly	VVX-series deskphones; Rove-series DECT (base stations and handsets)	No

Phones from other vendors — including Cisco and Grandstream — are not supported. Within these model lines the set of supported models changes over time, so before standardising on a phone family or placing a large order, contact support to confirm the specific models are currently supported.

There are three ways a phone can find its configuration. The resulting configuration is the same; the difference is how the phone discovers DialStack on first boot.

Manual URL

The provisioning URL is pasted into the phone's local admin interface. You enter it once per phone; the phone then pulls its full configuration from DialStack, reboots, and registers on its own.

• Works on every supported phone, with no network changes.
• One-time per phone, but each phone has to be touched at least once.
• Best when you have phones on a bench before they ship, or for one-off deployments.

Before you start

1. Copy the provisioning URL. It is on the account's Account Settings page, under the collapsible Provisioning section — use the copy button. The same URL is used for every phone on the account.
2. Add the phone as a device by MAC address on the Devices page, so DialStack recognises it when it checks in.
3. Put the phone on the same network as your computer, or note the phone's IP address, so you can reach its web interface.
4. Know the phone's admin password. A brand-new or factory-reset phone still uses the vendor default noted below; newer models prompt you to set a password during first-boot setup. Once a phone has been provisioned, it has its own admin password, which you can reveal from the Phone web admin password row on the device's page. To clear an old configuration first, see Migrating Existing Phones.

The steps below use each vendor's own field names, and menu labels vary a little between models and firmware. Once the URL is saved and the phone reboots, it fetches its configuration with no further input.

Snom (D-series deskphones)

Snom deskphones take the provisioning URL from their web interface.

1. Find the phone's IP address: press the settings key (wrench icon) on the phone → Information (or Status) → Network, and note the IPv4 address.
2. In a browser on the same network, open http://[phone-IP] and sign in (username admin; the default password is 0000 on older firmware, or the password you set during first-boot setup).
3. Go to Advanced → Update tab.
4. Paste the provisioning URL into the Setting URL field.
5. Click Apply, then Save, then Reboot.

On the current D8xx models (for example the D812 and D865) the web interface is arranged differently; if you can't find the Setting URL field, use DHCP Option 66 or zero-touch instead, or contact support for the model-specific path.

Snom (M-series DECT)

For a DECT system, configure the base station — the paired handsets pick up their configuration from the base, so you don't touch them individually. Sign in to the base's web interface at http://[base-IP] (default username admin, password admin); find the base's IP address from its status display or your router's DHCP leases. The field's location depends on the model:

• M500 (and M5x single-cell bases): Servicing → Provisioning → paste the URL into the Server URL field → Save, then reboot from Servicing → Reboot.
• M700 / M900: Management → enter the URL as the Configuration server address → Save, then reboot the base station.

Yealink (T-series deskphones)

Yealink deskphones can take the URL from the web interface or from the phone's own menu. The web interface is easier for entering a long URL.

Web interface (recommended):

1. Find the phone's IP address: press Menu → Status, and note the IPv4 address.
2. In a browser on the same network, open http://[phone-IP] and sign in (default username admin, password admin).
3. Go to Settings → Auto Provision.
4. Paste the provisioning URL into the Server URL field and click Confirm.
5. Click Auto Provision Now to fetch the configuration immediately.

On the phone:

1. Press Menu → Advanced Settings (labelled Advanced on some color-screen models such as the T54W; default password admin) → Auto Provision.
2. Enter the provisioning URL in the Server URL field.
3. Save to confirm. The phone provisions and reboots.

Poly (VVX / Rove)

Poly deskphones take the URL from their web interface. These steps are verified on the Edge E series; other Poly models use the same web interface, though menu labels can differ slightly by model and firmware.

1. Find the phone's IP address from its Settings → Status → Network screen.
2. In a browser on the same network, open https://[phone-IP] and sign in as Admin (username Polycom; on a brand-new or factory-reset phone the default password is 456). Accept the browser's certificate warning: the phone uses a self-signed certificate.
3. Go to Settings → Provisioning Server.
4. Set Server Type to HTTPS and paste the provisioning URL into Server Address.
5. Click Save. The phone fetches its configuration within a few seconds and restarts on its own.

For Rove DECT base stations, contact support for the current procedure.

Confirming it worked

After the phone reboots it should come online and pull its configuration. Note that coming online is not the same as being ready to call — a deskphone or handset also has to be assigned to a user before it can place and receive calls. The device setup checklist on the device's detail page shows exactly how far the phone has gotten. If it stays on "Initializing" or shows a registration error:

1. Verify the MAC address was entered correctly on the Devices page.
2. Check that the account's provisioning token hasn't been rotated since the phone was given the URL. Rotating it invalidates the old URL.
3. Confirm the phone can reach the provisioning URL from its network over HTTPS.

DHCP Option 66

The provisioning URL is set on the customer's network DHCP server as Option 66 (or Option 159 / 160, depending on the equipment). Phones plugged into that network read the URL automatically on boot.

• Works for any number of phones on the same network with zero per-phone setup.
• Requires that you (or someone on-site) controls the customer's DHCP server.
• Best when you manage the customer's network or they manage it themselves competently.

Zero-touch

For select phones from supported vendors, the phone discovers DialStack automatically the first time it boots. No URL, no DHCP, no on-site configuration.

• Add the phone to the account by MAC address on the Devices page, then ship it directly to the end site.
• The phone contacts its vendor's redirection service on first boot, gets pointed at DialStack, and pulls its configuration.
• Best for ship-to-site deployments where no one will be on hand to touch the phone or the network.

Zero-touch is enabled automatically — nothing to configure. See Supported devices for which vendors offer it.

Picking a method

Most platforms standardise on one method for the bulk of their fleet and keep one of the others as a fallback.

Deployment shape	Recommended
Ship-to-site (you never touch the phone or network)	Zero-touch where supported, otherwise manual URL
You install on-site or manage the network	DHCP Option 66
Pre-staging phones in your warehouse	Manual URL while staging, then ship
Mixed fleet	Pick one default and document the exceptions

Phones claimed by a previous provider

Some phones arrive still registered to a previous provider, which is common with refurbished units and migrated phones. Their zero-touch registration is escalated to support automatically; track it on Provisioning Escalations, and use the manual URL method if you can't wait.