Auto Provisioning - FAQ

Use this page to troubleshoot common auto-provisioning questions and to understand how Cloud Voice pushes configuration to your IP phones and devices.

Auto provisioning is the process of sending configuration (account credentials, function keys, and other phone settings) to a device automatically, so you do not have to program each phone by hand.

Note

Throughout this page, “PBX” (Private Branch Exchange) refers to your Cloud Voice phone system, and “IP phone” means a desk phone that connects over your data network rather than a traditional analog line.

Which protocol is used for auto provisioning?

Cloud Voice delivers configuration files to your devices over HTTP (HyperText Transfer Protocol, the same protocol web browsers use).

Note

Because provisioning happens over HTTP, each device has to be able to reach the PBX across the network to download its configuration. If a phone cannot connect to the PBX, it will not receive its settings.

My devices aren’t being provisioned. What’s wrong?

If a device fails to pick up its configuration, work through the possible causes below.

Possible cause	What to do
The device model isn’t supported for auto provisioning by Cloud Voice.	Confirm your device appears on the list of supported models before continuing.
A feature or parameter you’re trying to push isn’t supported by the device itself.	Check with the device manufacturer to verify the device supports the feature or parameter.
You changed an extension user’s settings but never re-sent the configuration to the device.	Open Auto Provisioning > Phone and re-provision the affected device after making changes.
A parameter in your advanced custom template is set incorrectly.	Review the custom template and correct the parameter.
A parameter variable in the advanced custom template was altered, so the configuration can no longer be applied from the PBX web portal.	Review the custom template and confirm the variables are correct.

Tip

Any time you edit an extension user’s settings, remember to re-provision the device from Auto Provisioning > Phone. Configuration changes don’t reach the phone until you push them.

Why don’t all of my function keys appear on the phone?

Function keys (also called programmable keys, including BLF keys, where BLF is Busy Lamp Field, a key that shows another extension’s status) are the assignable buttons on a desk phone. Each phone has a fixed number of them. If you assign more function keys to an extension than the phone physically supports, the extra keys are ignored and won’t appear on the device.

Tip

If a key you expected is missing, count the keys you assigned against the number of programmable keys the phone model actually has, then remove the extras so the ones you need fit within the limit.