| Scroll export button | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
The Guide describes and explains how to provision Wildix devices. WMS Version: 6.0X/ 7.0X Updated: May 2025 Permalink: https://wildix.atlassian.net/wiki/x/OxnOAQ |
| Table of Contents |
|---|
Introduction
There are several provisioning modes supported by WMS:
- Auto-provisioning (available only for Hardware and Virtual PBXs):
For devices connected to the local LAN or remote network via VPN.
For remote/ unreachable devices behind NAT/ firewall.
- Auto-configuration via auto.wildixin.com:
Automatically add Wildix devices during new installations.
...
Assign devices to PBX via Salesforce Partner Community (for devices, ordered via SFPC)
Assign devices to PBX via WMP (for devices that were ordered via WMP).
...
| Note |
|---|
Note: Starting from WMS 6.03.20230630.3, the logic was updated to avoid HTTP protocol for device provisioning for improved security. With the update to WMS 6.03, devices are switched to HTTPS protocol by default, except for some old devices (e.g. some old FXS/FXO, W01GSM and old WP phones like WP400, WP500). If required, HTTP protocol can be set by the "HTTPForceUse" custom provisioning parameter. Documentation: Provisioning Custom Settings |
Auto-provisioning (Automatic mode) (Hardware, Virtual PBX)
| Anchor | ||||
|---|---|---|---|---|
|
...
Direct access to devices
...
Temporary limitation on WMS 5.0X; starting from WMS 5.02.20210402.1, this limitation is removed.
Direct access is currently possible only after modifying the URL after you connect to a device (after you click on the link “Open”). You need to:
- change https to http
- add custom secure port if PBX uses it
...
After you have provisioned devices, you can access them directly from WMS -> Devices.
...