Phone Provisioning¶
Phone provisioning lets you deploy desk phones in bulk: define settings once in a profile, register each phone by MAC address, and let the phone pull its configuration from QVOICE Platform over HTTPS.
Resellers and technical administrators use this area to roll out Yealink, Polycom, Grandstream, and other supported models without manual per-phone programming.
Where to find Provisioning¶
In the QVOICE Platform Admin Portal:
- Open Provisioning.
- Create a Profile (manufacturer, model, SIP settings, optional ACL).
- Create a Phone device for each physical phone (MAC address, profile, user extension).
- Unlock the phone device when you are ready for the phone to download config.
- Point the phone at the correct provisioning URL (see Supported phones below).
flowchart LR
profile[Create profile] --> phone[Add phone by MAC]
phone --> user[Assign user extension]
user --> unlock[Unlock phone]
unlock --> url[Set provisioning URL on phone]
url --> pull[Phone downloads config]
Provisioning server¶
Most manufacturers use HTTPS on port 9443. Replace {manufacturer} with the vendor path from the table below.
| Setting | Value |
|---|---|
| Protocol | HTTPS |
| Server | Your platform hostname (same host as https://qvoice.net:9443) |
| Port | 9443 |
| Path | /provisioning/{manufacturer} |
Example URL pattern:
https://qvoice.net:9443/provisioning/yealink
White-label partners use their own portal hostname; the path and port stay the same.
Portal setup (all manufacturers)¶
What to configure
| Step | Action |
|---|---|
| Profile | Choose manufacturer and model, set SIP transport/port, timezone, and optional HTTP/ACL rules |
| Phone device | Enter MAC address (no colons), select profile, assign user |
| Unlock | Enable provisioning for that MAC — locked phones do not receive config |
| Phone GUI | Set auto-provisioning / config server URL (vendor-specific screens below) |
Good to know
- Each phone MAC must be unique in the account.
- Profiles can be reused across many phones of the same model.
- Use Preview config in the portal to verify generated settings before unlocking.
- HTEK phones also support legacy TFTP provisioning on port 60069 if HTTPS is not used.
Supported phones¶
The portal supports the manufacturers and models below. Models marked HTTPS auto pull configuration from the provisioning server when unlocked. Portal template models are supported for profiles, button maps, and config preview; apply the generated file on the phone using the vendor’s usual method (TFTP, HTTP upload, or local import).
Manufacturer summary¶
| Manufacturer | Provisioning path | Method | Models |
|---|---|---|---|
| Yealink | /provisioning/yealink |
HTTPS auto | T19, T33, T46G, T46S, T46U, CP960, W60P |
| Polycom | /provisioning/polycom |
HTTPS auto | IP330, IP331, IP450, IP550, IP6000, VVX101, VVX150, VVX201, VVX250, VVX311, VVX350, VVX400, VVX450 |
| Grandstream | /provisioning/grandstream |
HTTPS auto | GXP-2130, GXP-2135, GXP-2140, GXP-2160, GXP-2170, HT801, HT802, HT814, GRP-2612, GRP-2613, GRP-2614, GRP-2615, GRP-2616, GRP-2624, GRP-2634, GRP-2636, GRP-2650, GRP-2670 |
| Fanvil | /provisioning/fanvil |
HTTPS auto | X1SP, X3SG, X5U, X6U, I10V |
| Htek | /provisioning/htek |
HTTPS auto (TFTP optional) | UC803, UC903, UC923, UC924, UC926 |
| Mitel | /provisioning/mitel |
HTTPS auto | 6731, 6375, 6867, 6865, 6869 |
| Cisco | — | Portal template | 7912, 7940, 7960, 7962 |
| 4G IP Phone | — | Portal template | S01 |
Expansion modules¶
These models support optional expansion key modules in the portal button editor:
| Manufacturer | Models |
|---|---|
| Polycom | IP550, VVX311, VVX400 |
| Yealink | T46G, T46S, T46U |
| Cisco | 7940, 7960, 7962 |
| Fanvil | X3SG, X5U, X6U |
| Mitel | 6731 |
Yealink¶
Provisioning URL: https://qvoice.net:9443/provisioning/yealink
How to set up
- Create a Yealink Profile and Phone in the portal; assign the user and unlock the device.
- On the phone: Settings → Auto Provision (or equivalent).
- Set server to your platform hostname, path
/provisioning/yealink, port 9443, protocol HTTPS. - Reboot or trigger provisioning.
Suggested screenshot: Yealink web GUI — Auto Provision page with HTTPS URL filled in (phone-system/yealink-auto-provision.png).
Polycom¶
Provisioning URL: https://qvoice.net:9443/provisioning/polycom
How to set up
- Create a Polycom Profile and Phone in the portal; unlock the device.
- On the phone: enable Provisioning Server / Config Server (varies by VVX vs SoundPoint model).
- Point the server at https://qvoice.net:9443/provisioning/polycom (HTTPS, port 9443).
- Reboot the phone.
Suggested screenshots: Polycom web UI provisioning fields; portal Provisioning list with a Polycom phone unlocked (phone-system/polycom-provision-server.png, phone-system/provisioning-phones-list.png).
Grandstream¶
Provisioning URL: https://qvoice.net:9443/provisioning/grandstream
How to set up
- Create a Grandstream Profile and Phone in the portal; unlock the device.
- On the phone: Maintenance → Upgrade and Provisioning → Config Server.
- Set HTTPS config server path to
/provisioning/grandstreamon port 9443. - Save and reboot.
Suggested screenshot: Grandstream GRP web UI — Config Server path (phone-system/grandstream-config-server.png).
Fanvil¶
Provisioning URL: https://qvoice.net:9443/provisioning/fanvil
How to set up
- Create a Fanvil Profile in the portal.
- For each phone, add a Phone device bound to that profile.
- Unlock each phone device.
- On the phone web GUI, set Auto provisioning URL to https://qvoice.net:9443/provisioning/fanvil.
- Reboot or apply provisioning.
Suggested screenshot: Fanvil web GUI — Auto provisioning URL field (phone-system/fanvil-auto-provision-url.png).
Htek¶
Provisioning URL (HTTPS): https://qvoice.net:9443/provisioning/htek
Alternative (TFTP): tftp://{your-hostname}:60069/provisioning/htek
ACL required
HTEK phones are rejected unless the profile ACL includes the phone’s network or its IP address (with subnet mask). Add the office LAN or the phone’s static IP before unlocking.
How to set up
- Create an Htek Profile with ACL entries for the deployment network.
- Add each Phone by MAC, assign users, unlock devices.
- On the phone, set provisioning to the HTTPS or TFTP URL above.
- Reboot the phone.
Mitel¶
Provisioning URL: https://qvoice.net:9443/provisioning/mitel
Configuration server (phone GUI)
| Setting | Value |
|---|---|
| Protocol | HTTPS |
| Server | Your platform hostname |
| Path | /provisioning/mitel |
| Port | 9443 |
Advanced → Network
| Setting | Value |
|---|---|
| HTTPS Client Method | HTTPS |
| Validate Certificates | False |
Restart the phone after saving so it downloads configuration.
Screenshot gallery: Click any thumbnail to zoom.
![]() |
![]() |
![]() |
Cisco¶
Cisco models 7912, 7940, 7960, and 7962 are supported for profiles, programmable keys, and config preview in the portal. There is no dedicated HTTPS auto-provisioning endpoint; export or copy the generated configuration from the portal and apply it using Cisco’s supported method for that model (TFTP, web upload, or manual entry).
Suggested screenshot: Portal config preview for a Cisco 7962 (phone-system/cisco-config-preview.png).
4G IP Phone¶
Model S01 is supported for portal profiles and button programming (10 programmable keys). Use the portal Preview config output and apply it on the device per the manufacturer’s instructions.
Suggested screenshot: Portal profile for 4G IP Phone S01 (phone-system/4g-ip-phone-profile.png).
Suggested images to add¶
Capture these in the Admin Portal or on phone web GUIs to complete this page. Save new shots under brands/qvoice/images/phone-system/ using the filenames shown.
| Filename | What to capture |
|---|---|
provisioning-profiles-list.png |
Admin Portal → Provisioning → Profiles list |
provisioning-phone-form.png |
Add/Edit Phone — MAC, profile, user, Unlock toggle |
provisioning-phones-list.png |
Phones list showing manufacturer/model and locked/unlocked state |
yealink-auto-provision.png |
Yealink web UI — HTTPS auto provision URL |
polycom-provision-server.png |
Polycom/VVX web UI — provisioning server fields |
grandstream-config-server.png |
Grandstream web UI — Config Server path |
fanvil-auto-provision-url.png |
Fanvil web UI — auto provisioning URL |
cisco-config-preview.png |
Portal — Preview config for Cisco model |
4g-ip-phone-profile.png |
Portal — 4G IP Phone S01 profile or button map |
Existing Mitel and HTEK screenshots live in wikijs/ and are already wired on this page.
Related topics¶
- Cloud Phone System Admin — platform overview
- Account Settings — account-wide phone behavior
- Legacy HTEK TFTP notes:
phone-system/tftp-htek-provisioning.md(orphan page; HTTPS method above is preferred)



