Zero-touch
Plug a phone in and it configures itself.
An admin types a MAC address and picks a model. That is the task. Everything after the handset finds a network cable, from the config it downloads to the line it registers on, happens without a person touching that phone again.
One handset, first boot
- inMAC + model entered
- step 1Provisioning URL
- answeredRegistered, keys lit
What the admin does
Two fields, then the phone sets itself up
A MAC address identifies the physical handset. A model tells the platform which settings file to build for it. Nothing else is typed before the phone is on a line.
The device is added to the platform before it is ever plugged in, so the config is waiting the moment it asks. Assign it to a line at the same time, or leave that for later; either way the handset does not sit unconfigured on a desk.
Nobody reads a password off the phone's screen and nobody types one into it. The settings a handset needs, its line, its extension, its keys, arrive as a file it downloads for itself.
The provisioning URL
Every phone gets its own address
A generic config file that any phone could fetch would mean any phone could ask for anyone's settings. So it isn't generic.
One URL per device
Each handset is issued its own provisioning address, built from that device alone, and no other phone's address will hand back this one's settings.
A token, bound to one phone
The address carries a random token in place of a password, and that token works for one handset and no other. It expires, and reissuing it from the portal kills the old one immediately, so a URL that ends up in an email or a spreadsheet can be made worthless in a click.
Nobody hands out a SIP password
Because the credential is a token bound to one device address, there is no shared secret to type, copy or send, and no file another phone on the network could usefully ask for. The handset keeps using its own address on every reboot, which is how it picks up a change you make months later without anybody visiting the desk.
A whole office, no typing
Set one option on your own DHCP server, and every phone finds us
A DHCP option is a setting your router or DHCP server hands to every device on the network the moment it asks for an address. Point it at the platform once, and a new handset finds its provisioning address on its own, before anyone opens the admin screen.
| Vendor | DHCP option | What it means for you |
|---|---|---|
| Yealink | Option 66 | the phone reads it straight out of the DHCP lease on first boot |
| Poly | Option 160 | checked first, ahead of option 66, which the phone still falls back to |
| Grandstream | Option 66 | newer models also accept option 43 if that is what your DHCP server already carries |
| Snom | Option 66 | option 43 is read too, and takes over if both are present |
Set the matching option once on the DHCP server that hands out addresses in your office, and a phone in a box from the manufacturer comes up already pointed at the platform the first time it is plugged in. Nobody has typed anything into it at all.
Drawn, not filmed
From cold boot to a lit line key
The handset asks the network what it is, downloads its configuration and brings its keys up, in the seconds between plugging it in and the screen settling.
Two things nobody thinks to ask about until the boxes arrive
Your logo on the screen, and firmware that is checked before it registers
Custom branding
The business's own logo goes on the handset screen as part of the configuration it downloads, not as a sticker somebody has to remember to order.
Firmware, held to one version
The platform keeps a tested firmware build for every model it supports. A phone that boots on something older is pushed to that build first, and only registers once it is running it, so a handset pulled out of a drawer years later behaves exactly like one bought yesterday.
Which handsets this covers
Four manufacturers, provisioned the way each one expects
Every manufacturer names its settings differently and packages its config file differently. The platform writes each one in its own format.
- Grandstream
- Poly
- Snom
- Yealink
Buying a phone from one of these before ordering service is safe: tell us the model and we will confirm it comes up zero-touch before a single unit ships.
What you get
A MAC address and a model, and the rest of the setup happens on the network rather than at a keyboard. No password to type into a handset, no spreadsheet of them to guard, and a whole office of phones that find the platform themselves the moment they are plugged in.