¶ General Information
Starting with PBXware v3.8.2, dynamic HTTP/TFTP provisioning is supported.
Instead of generating configuration files on disk, PBXware creates them dynamically when a provisioning request is received from a device.
-
By default, HTTP provisioning is disabled if no HTTP username and password are configured.
-
Configuring an HTTP Username and HTTP Password automatically enables HTTP provisioning.
-
Devices that do not support HTTP Digest Authentication cannot be provisioned over HTTP and must use TFTP instead.
-
The HTTP Username and HTTP Password can be configured under:
Settings → Servers → YourServerName (Edit) → Auto Provisioning → HTTP Username / HTTP Password
¶ HTTP Server
The PBXware HTTP provisioning service is available at the following URL:
http://ip-address/prov
¶ MAC Configuration Requests
Devices download their configuration files by requesting the appropriate file based on their MAC address.
Example requests:
http://ip-address/prov/mac.cfg
http://ip-address/prov/cfg.mac
http://ip-address/prov/phonemac.cfg
NOTE: The required filename format depends on the device model. Refer to the Filename field in the corresponding device documentation.
¶ Filesystem Files (Firmware and Other Files)
Firmware images and other provisioning files can be accessed at:
http://ip-address/prov/sip.ld
¶ Custom Configuration Files
Custom configuration files are available at:
http://ip-address/prov/aastra.cfg
¶ MAC Configuration Files
Devices retrieve configuration files based on their MAC addresses. Access to these files requires HTTP Digest authentication using a valid username and password.
¶ Testing with cURL
You can use cURL to verify the auto provisioning service and validate the generated configuration files. Alternatively, you can open the provisioning URL directly in a web browser.
For more information, visit the official cURL website: https://curl.se
Example Command
curl -i -u user:pass --digest http://ip-address/prov/mac.cfg
Command Parameters
-
-i – Include the HTTP response headers in the output.
-
-u – Specify the HTTP username and password (
username:password). -
--digest – Enable HTTP Digest authentication. This parameter is required because PBXware does not support Basic HTTP authentication for provisioning.
-
--user-agent – This is how you can send a different User-Agent string, if you want to test HTML/XML Directory pages. Example:
--user-agent "Yealink SIP-T38"
For devices that use XML configuration files, testing in a web browser is recommended. PBXware returns these files with the text/xml content type, allowing the browser to display the XML document for easier validation.
¶ Testing with wget
If curl is not available on your system, you can use wget to test the provisioning service.
Example Command
wget -S -q http://username:password@ip-address/prov/mac.cfg -O-
Command Parameters
-
-q – Turns off verbosity and progress bar from wget.
-
-S – Display the HTTP response headers.
-
--user – Specify the HTTP username (if it is not included in the URL).
-
--password – Specify the HTTP password (if it is not included in the URL).
-
-O- – Write the output to standard output instead of saving it to a file.
-
-U=user-agent – Use it to set User-Agent.
For additional options, run the following command in your PBXware shell: wget --help
¶ Testing HTTPS Mode
PBXware supports HTTPS provisioning for devices that support HTTPS connections. Some devices do not accept self-signed certificates, in which case a certificate signed by a trusted Certificate Authority (CA) is required.
cURL Command Example
curl -i -u user:pass --digest --insecure https://ip-address/prov/mac.cfg
Additional Options
- --insecure – This option accepts self-signed certificates as valid.
¶ HTTP Response Codes
The HTTP provisioning service may return the following response codes:
¶ 401 Unauthorized
This status indicates that the username and password were not provided. It signals to the device that authentication credentials must be included in the next request.
¶ 200 OK
The request was processed successfully. If this code is not received, it implies that provisioning has failed.
¶ 403 Forbidden
This error occurs when invalid authentication credentials are provided. It can also appear if the tenant or server does not have valid HTTP username and password configured.
¶ 404 Not Found
The requested resource could not be found. This may occur for one of the following reasons:
- The specified MAC address does not exist.
- The device is not supported for auto provisioning.
- The requested HTML/XML directory page is not available for the device.
- The requested custom provisioning route does not exist.
- The requested file path is incorrect.
- The requested file does not exist.
- The request cannot be processed by the provisioning service.
¶ 500 Internal Server Error
An unexpected server-side error occurred while processing the request. If this occurs, please contact Bicom Systems Support for assistance.
¶ HTTP Logs
To monitor device requests and HTTP traffic, use the following commands:
- For HTTP traffic:
cd /opt/pbxware tail -f pw/var/log/nginx/localhost.access\_log
- For HTTPS traffic:
cd /opt/pbxware tail -f pw/var/log/nginx/localhost.ssl\_access\_log
Example Output:
10.1.0.138 - - \[23/Apr/2013:11:43:27 +0200\] "GET /prov/\_directory/001565267db9 HTTP/1.0" 200 2654 "-" "Yealink SIP-T38G 38.0.23.22 00:15:65:26:7d:b9" "-"
Key Information:
- GET filename - The file requested by the device.
- 200 2654 - The request was successful with a 200 OK status, and the Content-Length is 2654 bytes.
- Authentication Flow - If authentication is required, the sequence should be 401 (Authentication Required) followed by 200 OK.
- Yealink SIP-T38G 38.0.23.22 - The User-Agent string, identifying the device model and version.
¶ Syslog
Some devices are capable of sending logs via syslog. To set up syslog-ng as the syslog host on Gentoo, follow these steps:
-
Edit the syslog-ng configuration file:
/etc/syslog-ng/syslog-ng.conf nano /etc/syslog-ng/syslog-ng.conf -
Add the following lines at the bottom of the file:
source net { udp(); }; destination remote { file("/var/log/remote/$FULLHOST"); }; log { source(net); destination(remote); }; -
Create the directory for storing remote logs:
mkdir /var/log/remote -
Restart syslog-ng to apply the changes:
/etc/init.d/syslog-ng restart
¶ Yealink Information
¶ Provisioning Method
-
Yealink devices support provisioning via either HTTP or TFTP.
-
HTTPS works with any certificate if "Only Accept Trusted Certificates" is Disabled.
¶ Yealink Devices
Filename
- MAC.cfg
File Format
- The configuration file format differs between the T2xP and T3xP series unless the device is running firmware version 70 or later.
¶ Supported Features
The following table lists all Yealink device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | LDAP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CP860 | 37.81.0.10 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| CP920 | 78.81.0.15 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| CP925 | 148.86.0.5 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| CP935W | 149.86.0.5 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| CP960 | 73.15.0.38 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| CP965 | 143.86.254.36 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T18 | 18.0.23.5 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✔ |
| T19P | 53.84.0.15 | ✘ | ✔ | ||||||||||
| T20 | 9.61.23.9 | ✔ | ★ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T21PE2 | 52.84.0.15 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T22 | 7.73.0.50 | ✔ | ★ | ✔ | ✘ | N/A | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T23G | 44.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T26 | 6.73.0.50 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ★ | ✔ |
| T27G | 69.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T27P | 45.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T28 | 2.73.0.50 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T29G | 46.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T30 | 124.85.0.40 | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T30P | 124.85.0.40 | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T31 | 124.85.257.55 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T31G | 124.85.257.55 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T31P | 124.85.257.55 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T31W | 124.86.0.75 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T32 | 32.70.1.33 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T33G | 124.85.257.55 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T33P | 124.85.257.55 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T34W | 124.86.0.75 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T38 | 38.70.0.185 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ |
| T40G | 76.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T41P | 36.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T41S | 66.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T41U | 108.84.0.30 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T42G | 29.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T42S | 66.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T42U | 108.84.0.30 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T43U | 108.84.0.30 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T44U | 108.86.254.310 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T44W | 108.86.254.310 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T46G | 28.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T46S | 66.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T46U | 108.84.0.30 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T48G | 35.83.0.50 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T48S | 66.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T48U | 108.84.0.30 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T49G | 51.80.0.100 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T52S | 70.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T53 | 95.84.0.30 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T53W | 95.84.0.30 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T54S | 70.84.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T54W | 96.84.0.30 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T56A | 58.83.0.15 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T57W | 97.84.0.30 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T58V | 58.80.0.10 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T58W | 150.86.254.11 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T60P | ✘ | ||||||||||||
| T64LTE | 132.86.0.35 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| T65P | ✘ | ||||||||||||
| VP59 | 91.283.0.30 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W52P | 25.81.0.30 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W56P | 25.81.0.30 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W60B | 77.83.0.25 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W70B | 146.85.0.20 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W80B | 103.83.0.30 | ✔ | ★ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
| W90DM | 130.85.0.10 | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ |
Notes:
- Yealink T18 has auto provisioning bug. If provisioning server is assigned through Option 66, manually assigned provisioning server will not work unless phone is set to work with static IP address.
¶ Firmware v70
Due to Yealink omission, we are not able to detect phone firmware version, when using TFTP. If you would like to auto provision Yealink phone with v70 firmware, please create file v70.txt in tftp directory, like this:
cd /opt/pbxware/pw/tftp touch v70.txt
If file v70.txt exists in /opt/pbxware/pw/tftp folder, all auto provisioning data for Yealink phones will be in v70 format, hence all phones should be on v70 or pre-v70 version. Mixing is not supported.
¶ Known issues
Make sure you do factory reset after upgrade to latest V70 firmware. This is known to fix at least one problem - wrong User-Agent string for T46G device.
Wrong User-Agent:
- Yealink-T46G 28.71.0.85 28.1.0.128.0.0.0
Correct User-Agent:
- Yealink SIP-T46G 28.71.0.85 00:15:65:45:70:71
Problem with firmware older than 28.71.0.85 and T46G
Yealink T46G does not send User-Agent when requesting remote directory file, which is required due to security reasons, hence remote directory will not work. This issue has been fixed in 28.71.0.85 firmware.
¶ Poly Information
¶ Provisioning Method
-
Poly devices support provisioning over HTTP or TFTP.
-
HTTPS provisioning is supported and requires a valid certificate signed by a trusted Certificate Authority (CA). Wildcard certificates are not supported.
¶ Poly Devices
¶ Configuration Files
- MAC.cfg
Specifies the location of the main configuration file and firmware.
- phoneMAC.cfg
Contains the main device configuration.
- MAC-directory.cfg
Contains the BLF/Directory list.
Content Type
- XML format
¶ Supported Features
The following table lists all Poly device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | LDAP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CCX400 | 7.3.2.0.182 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| CCX600 | 7.3.2.0182 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| CCX700 | 7.3.2.0.182 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge B20 | 1.0.1 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge B30 | 1.0.1 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge E100 | 8.1.0.12774 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge E220 | 8.1.0.12774 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge E320 | 8.1.0.12774 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge E400 | 8.1.0.12774 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Edge E500 | 8.1.0.12774 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Rove B2 | 8.0.2 | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| Rove B4 | 8.0.2 | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| Trio 8300 | 7.0.0.4265 | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| Trio C60 | 7.2.0.12361 | ✔ | ✔ | ✘ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| VVX350 | 6.4.3.5059 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| VVX450 | 7.3.2.0.182 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| VVX D230 | 7.1.2 | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
¶ General UAD Config
NOTE: General UAD config must be valid XML for that particular firmware otherwise all configuration will fail.
PUT requests Poly phones will send PUT requests to server and these files can be saved on disk if upload mode is turned on.
Poly phones may send the following:
- Log files
- Configuration override files
- Configuration saved in web interface, set on phone.
- Directory
This is not supported, as it conflicts with Enhanced Services Directory. It is not safe to turn this feature on public internet. To turn it on, create upload directory:
Please note that the directory feature is not supported, as it conflicts with the Enhanced Services Directory. Additionally, enabling this feature over the public internet is not secure. To enable it, create an upload directory as follows:
cd /opt/pbxware/pw/tftp mkdir upload chown 101:1003 upload
It is not required to have WebDAV enabled in nginx for above to work.
For detailed instructions on preparing your PBXware system for Poly firmware support, please refer to our How-To Guide on Creating a Poly/Polycom Firmware Pack
NOTE: If you are unsure about how to create the Poly/Polycom firmware package, please contact our support team, and we will be happy to assist you.
¶ Polycom Information
¶ Provisioning Method
-
Polycom devices support provisioning over HTTP or TFTP.
-
HTTPS provisioning is supported and requires a valid certificate signed by a trusted Certificate Authority (CA). Wildcard certificates are not supported.
¶ Polycom Devices
Filenames
- MAC.cfg
Specifies the location of the main configuration file and firmware.
- phoneMAC.cfg
Contains the main device configuration.
- MAC-directory.cfg
Contains the BLF/Directory list.
Content Type
- XML format
¶ Supported features
The following table lists all Polycom device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | LDAP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IP301 | 3.1.8 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP320 | ✘ | ||||||||||||
| IP321 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP330 | ✘ | ||||||||||||
| IP331 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP335 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP450 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP501 | ✘ | ||||||||||||
| IP5000 | ✘ | ||||||||||||
| IP550 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP560 | ✘ | ||||||||||||
| IP601 | 3.1.8 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP650 | 4.0.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | ★ | |
| IP670 | ✘ | ||||||||||||
| OBi2182 | 6.2.2 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX101 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX150 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX150 OBi Edition | 6.3.0.0 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX1500 | 5.7.1 | ✘ | ✔ | ||||||||||
| VVX201 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX250 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX250 OBi Edition | 6.3.0.0 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX300 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX310 | 5.7.1 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX350 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX350 OBi Edition | 6.4.0.2 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX400 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX410 | 5.7.1 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX411 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX450 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX450 OBi Edition | 6.4.0.2 | ✔ | ★ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX500 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX501 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX600 | 5.9.2 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
| VVX601 | 6.1.0 | ✔ | ★ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ★ | ✔ |
¶ General UAD Config
NOTE: General UAD config must be valid XML for that particular firmware otherwise all configuration will fail.
PUT requests Polycom phones will send PUT requests to server and these files can be saved on disk if upload mode is turned on.
What Polycom phones like to send:
- Log files
- Configuration override files
- Configuration saved in web interface, set on phone.
- Directory
This is not supported, as it conflicts with Enhanced Services Directory. It is not safe to turn this feature on public internet. To turn it on, create upload directory:
cd /opt/pbxware/pw/tftp mkdir upload chown 101:1003 upload
It is not required to have WebDAV enabled in nginx for above to work.
For information on how to prepare your PBXware for Polycom multiple firmware support please check our How-To Guide on Creating a Poly/Polycom Firmware Pack
NOTE: If you are not sure how to create Polycom firmware package please contact our support and we will be glad to help you.
¶ Cisco/Linksys Information
¶ Cisco Devices
Filename:
- SIPmac.cnf – Main configuration file for Cisco SIP devices.
- spa.cfg – Main configuration file for Cisco SPA devices.
- mac.cfg – Main configuration file for Linksys devices.
- SEPmac.cnf.xml – Main configuration file for Cisco Enterprise devices.
¶ Supported Features
The following table lists all Cisco device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | LDAP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6851 | 11.0.1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| 7821 | 11.0.1 | ✔ | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| 7861 | 12.0.3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ |
| 7940 | 8.12 | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
| 7941 | 8.5.4 | ✔ | ✘ | ✔ | ✘ | ✘ | ★ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
| 7942 | ✘ | ||||||||||||
| 7945 | ✘ | ||||||||||||
| 7960 | 8.12 | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ |
| 7961 | 8.5.4 | ✔ | ✘ | ✔ | ✘ | ✘ | ★ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ |
| 7962 | ✘ | ||||||||||||
| 7965 | ✘ | ||||||||||||
| 7971 | ✘ | ||||||||||||
| 7975 | ✘ | ||||||||||||
| 8841 | 11-3-3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| 8851 | 11-3-3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| 8865 | 11.2.3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| PAP2 | 5.1.6 | ✔ | N/A | N/A | ✘ | N/A | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| SPA112 | 1.4.1 | ✔ | N/A | N/A | ✘ | N/A | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| SPA301G | 7.5.4 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA501G | 7.4.8a | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA502G | 7.4.8a | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA504G | ✘ | ||||||||||||
| SPA508G | 7.4.8a | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA509G | 7.5.1a | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA514G | 7.5.2 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA525G2 | 7.4.7 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ |
| SPA8000 | ✘ | ||||||||||||
| SPA901 | ✘ | ||||||||||||
| SPA941 | 5.1.8 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| SPA942 | ✘ | ||||||||||||
| SPA962 | 6.1.5 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
Cisco 79X1 devices use a complex XML configuration format.
You can provide a default XML template for each device by creating template files in the TFTP directory, for example:
/tftp/SEP_Default.xml
/tftp/SEP_Device_7941.xml
Template is attached in the document.
Documentation
Firmware
- Cisco Firmware Download (Cisco account required)
Asterisk NAT
Make sure nat=no is set in sip.conf, otherwise nothing will work.
WARNING: Cisco 79xx devices, other than 7940 and 7960, will not be able to work if PBXware is not in the same LAN.
These devices send UDP SIP requests from a high source port but expect a reply on port 5060. Because of this behavior and the way NAT works, phones will always receive response on the port their UDP SIP request was sent from and will not be able to register. Even if devices are in the same LAN, customers will have to manually set option NAT to No on PBXware, in Extensions -> Edit EXT -> Network Related section, in order for Cisco 79xx devices to successfully register.
¶ Grandstream Information
¶ Provisioning method
- Grandstream devices support provisioning over HTTP, HTTPS, and TFTP.
- Some Grandstream devices support HTTP, but Basic authentication only.
¶ Grandstream Devices
Filename
- cfgMAC
File Format
The cfgMAC file uses Grandstream's proprietary binary format and is not human-readable. The configuration is based on Pxxx=value parameters, which are encoded in the binary file.
You can pipe output to following command: curl ... | hexdump -C -v
¶ Supported Features
The following table lists all Grandstream device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | LDAP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DP750 | 1.0.3.23 | ✔ | ✘ | N/A | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| DP752 | 1.0.13.0 | ✔ | ✔ | N/A | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GRP2601P | 1.0.3.42 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2602P | 1.0.3.42 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2603P | 1.0.3.42 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2604P | 1.0.3.83 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2612 | 1.0.1.7 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2613 | 1.0.1.23 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2614 | 1.0.1.23 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2615 | 1.0.1.23 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GRP2616 | 1.0.1.23 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXP1615 | 1.0.4.152 | ✔ | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXP1625 | 1.0.4.82 | ✔ | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXP1628 | 1.0.4.82 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXP1630 | 1.0.4.67 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXP1760w | 1.0.1.98 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXP1782 | 1.0.1.8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXP2000 | 1.2.5.3 | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| GXP2124 | |||||||||||||
| GXP2130 | 1.0.9.69 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXP2135 | 1.0.9.108 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXP2140 | 1.0.11.3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXP2160 | ✔ | ✔ | ✘ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | |
| GXP2170 | 1.0.8.53 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| GXV3240 | 1.0.3.277 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| GXV3275 | 1.0.3.177 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXV3350 | 1.0.3.13 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXV3370 | 1.0.3.8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| GXV3380 | 1.0.1.19 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| HT286 | 1.1.0.45 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT386 | 1.0.3.96 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT486 | 1.1.0.45 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT488 | 1.0.3.96 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT496 | 1.0.3.96 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT502 | 1.0.9.1 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT503 | 1.0.9.1 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT701 | 1.0.4.8 | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| HT702 | |||||||||||||
| HT704 | |||||||||||||
| HT802 | 1.0.17.5 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| HT814 | 1.0.3.2 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| HT818 | 1.0.17.5 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
¶ Obihai Information
¶ Provisioning Method
- Obihai devices support provisioning over HTTP or TFTP.
¶ Obihai Devices
Filenames:
Main configuration file:
- mac.xml
BLF/Directory list:
- mac.xml
¶ Supported Features
The following table lists all Obihai device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 110 | ||||||||||||
| 202 | ||||||||||||
| 300 | 3.1.1 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | N/A | N/A | ✔ | ✘ |
| 302 | 3.1.1 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ |
| 504 | 4.0.1 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ |
| 508 | 4.0.1 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✘ |
| OBi1022 | 5.0.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| OBi1032 | 5.0.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| OBi1062 | 5.0.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
¶ VTech Information
¶ Provisioning Method
- VTech devices support provisioning over TFTP.
¶ VTech Devices
Filenames:
Main configuration file
- xxx_mac.cfg (xxx = phone model)
BLF/Directory list
- mac.xml
File Format:
¶ Supported Features
The following table lists all VTech device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ET605 | 8.10.2.62 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| ET617 | 8.10.1.34 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| ET635 | 8.10.1.35 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| ET685 | 8.10.2.62 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| VCS754 | 1.1.4.0 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VDP650 | 1.0.0.7 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| VSP600 | 1.1.4.1 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP715 | 1.1.4.0 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP716A | 2.0.5.1 | ✔ | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| VSP725 | 1.1.4.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP726 | 2.0.3.2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP726A | 2.0.5.1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| VSP735 | 1.1.4.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP736 | 2.0.3.2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ |
| VSP736A | 2.0.5.1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
¶ HTek Information
¶ Provisioning Method
- Htek devices support provisioning over HTTP or TFTP.
¶ Htek Devices
Filenames:
Main configuration file:
- cfgMAC
¶ Supported Features
The following table lists all HTek device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| UC802 | ✔ | ✘ | ✘ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC803 | ✔ | ✘ | ✘ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC804 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC806 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC840 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC842 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC860 | ✔ | ✘ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC862 | ✔ | ✘ | ✘ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | ✘ | ✔ | |
| UC902P | 2.0.4.4.25 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC903 | 2.0.4.4.25 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC912G | 2.0.4.4.33 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC912P | 2.0.4.4.33 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC923 | 2.0.4.4.25 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC924 | 2.0.4.4.25 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC924E | 2.0.4.4.33 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC926 | 2.0.4.4.25 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| UC926E | 2.0.4.4.33 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
¶ Denwa Information
¶ Provisioning Method
- Denwa devices support provisioning over HTTP, HTTPS, and TFTP.
¶ Denwa Devices
Filenames:
Main configuration file:
¶ Supported Features
The following table lists all Denwa device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DW-210P | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | |||||
| DW-310P | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | |||||
| DW-610P | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
¶ Mitel Information
¶ Provisioning Method
- Mitel devices support provisioning over TFTP only.
- HTTP provisioning is not supported because Mitel devices do not support HTTP authentication using a username and password.
¶ Mitel Devices
Filenames:
- aastra.cfg – Main device configuration.
- mac-directory.csv – BLF and directory configuration in CSV format.
¶ Supported Features
The following table lists all Mitel device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6930 | 6.1.0.187 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ |
| 6940 | 6.2.0.14 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ |
| 6867i | 4.3.0.2036 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ |
¶ Gigaset Information
¶ Provisioning Method
- Gigaset devices support provisioning over HTTP only.
¶ Gigaset Devices
Filenames:
- MAC
¶ Supported Features
The following table lists all Gigaset device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Maxwell 2 | 2.22.7 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| Maxwell 3 | 2.22.7 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| Maxwell 4 | 3.13.13 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| Maxwell 10 | 5.1.1-195 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ |
| Maxwell Basic | 2.22.7 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| N510 | 42.247 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| N720 | 70.110.00.000.00 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| N870 | 2.26.0 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
¶ Snom Information
¶ Provisioning Method
- Snom devices support provisioning over HTTP, HTTPS, and TFTP.
¶ Snom Devices
Filenames:
- snomdXXX-mac.htm (XXX = 320, 360..)
- snommXXX-mac.xml (XXX = 100, 400, 500, 900)
- snomd8XXX-mac.xml (XXX = 862, 865)
File Format:
- Plain text
¶ Supported Features
The following table lists all Snom device models integrated with PBXware, including both currently supported and End-of-Life (EOL) models. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 320 | 8.7.3.7 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| 360 | 8.7.3.25 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| 710 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D120 | 10.1.33.33 | ✔ | ✔ | ✘ | N/A | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| D315 | 8.9.3.80 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D335 | 10.1.57.14 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| D345 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D375 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D385 | 10.1.57.14 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| D713 | 10.1.137.15 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| D715 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D717 | 10.1.33.1 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| D735 | 10.1.33.33 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| D745 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D765 | 8.9.3.80 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D785 | 10.1.33.33 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ | |
| D862 | 10.1.159.12 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| D865 | 10.1.159.12 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| M100 | 1.0.5.7 | ✔ | ✔ | ✘ | ✔ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| M300 | IPDECT-V2/05.00/B0001 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| M400 | IPDECT-V2/06.10/B0004 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ | |
| M500 | 1.11.3 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| M900 | IPDECT-V2/05.00/B0001 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| PA1 | 8.7.5.75 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ | |
| PA1+ | 10.1.137.15 | ✔ | ✘ | ✘ | ✘ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✘ |
¶ Huawei Information
¶ Provisioning Method
- Huawei devices must be provisioned using DHCP Option 246.
¶ Huawei Devices
Filenames:
- mac.xml
¶ Supported Features
The following table lists all Huawei device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| eSpace 7910 | xxxSPCh00 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
| eSpace 7950 | xxxSPCh00 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
¶ Fanvil Information
¶ Provisioning Method
- Fanvil devices support provisioning over HTTP, HTTPS, and TFTP.
¶ Fanvil Devices
Filenames:
Main Configuration file:
- mac.cfg
BLF/Directory list:
- mac.csv
¶ Supported Features
The following table lists all Fanvil device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| H3 | 2.0.2.2822 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| H5 | 2.0.2.2818 | ✔ | ✘ | N/A | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| V62 | 2.12.15.1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| V64 | 2.12.2 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| V65 | 2.12.15.1 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| V67 | 2.6.6.112 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| W610W | 2.14.0.22 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X2P | 2.2.0.3753 | ✔ | ✘ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X3G | 2.2.0.3685 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X3SP | 2.2.0.3685 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X3U | 2.4.8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X4 | 2.0.3.3019 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X4G | 2.2.0.3685 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X4U | 2.4.3 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X4U-V2 | 2.12.16.17 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X5S | 0.9.0 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X5U | 2.4.5 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X5U-V2 | 2.12.16.17 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X6 | 0.7.0.1 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| X6U | 2.4.5 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X6U-V2 | 2.12.16.17 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X7 | 1.0.15 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X7A | 2.6.0.1153 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X7C | 1.0.15 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| X210 | 1.0.13 | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
¶ Flyingvoice Information
¶ Provisioning Method
- Flyingvoice devices support provisioning over HTTP, HTTPS, and TFTP.
¶ Flyingvoice Devices
Filenames:
Main Configuration file:
- mac.cfg
¶ Supported Features
The following table lists all Flyingvoice device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FIP10 | 0.7.73 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| FIP12WP | 0.7.72 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| FIP16 Plus | 0.2.28 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| P10 | 0.8.18.3 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| P10P | 0.7.74 | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| P23G | 0.9.19 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| P23GW | 0.7.73 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
¶ Wildix Information
¶ Provisioning Method
- Wildix devices support provisioning over HTTP, HTTPS, and TFTP.
¶ Wildix Devices
Filenames:
Main Configuration file:
- mac.cfg
¶ Supported Features
The following table lists all Wildix device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| WP410 | 150.145.2.13 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| WP480 | 65.145.6.32 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| WP490G | 67.145.7.104 | ✔ | ✔ | ✘ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
¶ Panasonic Information
¶ Provisioning Method
- Panasonic devices support provisioning over HTTP or TFTP.
¶ Panasonic Devices
Filenames:
Main Configuration file:
- mac.cfg
¶ Supported Features
The following table lists all Panasonic device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| KX-HDV130 | ||||||||||||
| KX-HDV230C | HDV230/11.180 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| KX-HDV330C | HDV330/11.100 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
| KX-TGP550 | 12.9 | ✔ | ✔ | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
| KX-UT113 | ||||||||||||
| KX-UT123 | ||||||||||||
| KX-UT133 | ||||||||||||
| KX-UT136 | ||||||||||||
| KX-UTG300B | 3.137 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |
¶ Avaya Information
¶ Provisioning Method
Avaya devices support provisioning via either HTTP or TFTP.
¶ Avaya Devices
Filenames:
- mac.txt
- mac-directory.csv
File Format
- Plain text
¶ Supported Features
The following table lists all Avaya device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| J139 | 4.1.5.0.6 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
| J179 | 4.1.5.0.6 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ | ✔ | ✘ | ✘ |
¶ Alcatel Information
¶ Provisioning Method
- Alcatel devices support provisioning over HTTP, HTTPS or TFTP.
¶ Alcatel Devices
Filenames:
Main Configuration file:
- Alcatel_IPxxx-MAC.cfg
¶ Supported Features
The following table lists all Alcatel device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| H2P | 2.10.00.0001060 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ |
| H3G | 2.12.07.000.1214 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| H6 | 2.12.07.000.1214 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
| IP100 | 0.64.6b | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP150 | 0.64.2a | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP200 | 13.70.0.144 | ✔ | ✔ | N/A | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP300 | 1.0.5b | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP600 | 14.70.0.144 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP800 | 15.70.0.136 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| IP1020 | ||||||||||||
| IP2015 | 1.0.5b | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✘ |
| M3 | 2.12.07.010.1828 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| M5 | 2.13.01.000.1899 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| M7 | 2.12.04.000.1720 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
| M8 | 2.13.32.000.2113 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✘ | ✔ |
¶ Aastra Information
¶ Provisioning Method
- Aastra devices support provisioning only via TFTP.
¶ Aastra Devices
Filenames:
- aastra.cfg
- mac.cfg
- mac-directory.csv
Directory list in CSV format.
File Format
- Plain text
¶ Supported Features
The following table lists all Aastra device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 6757i | 3.2.0.70 | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✘ | ✔ | ✘ | ✘ | ✘ |
| 6755i | ||||||||||||
| 6753i | ||||||||||||
| 480i | ||||||||||||
| 9112i | ||||||||||||
| 9133i |
¶ ReadyNet Information
¶ Provisioning Method
- ReadyNet devices support provisioning over TFTP only.
- HTTP provisioning is not supported because ReadyNet devices do not support HTTP authentication using a username and password.
¶ ReadyNet Devices
Filenames:
- MAC.conf
File Format
- Plain text
¶ Supported Features
The following table lists all ReadyNet device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AC1200MS | 3.20 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
| AC1100MSF | 3.20 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
| AC1000MS | 3.20 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
| QX300 | 3.20 | ✔ | N/A | N/A | N/A | ✔ | ✔ | ✘ | ✘ | ✘ | ✘ | ✘ |
¶ Sangoma Information
¶ Provisioning Method
- Sangoma devices support provisioning over TFTP only.
- HTTP provisioning is not supported because Sangoma devices do not support HTTP authentication using a username and password.
¶ Sangoma Devices
Filenames:
- cfgMAC
¶ Supported Features
The following table lists all Sangoma device models integrated with PBXware. The table also shows the minimum tested firmware version and the provisioning features available for each device.
| Model | Firmware | Basic | Time/Date | HTTP Directory | Directory/BLF | UAD General Template | UAD Template (extension) | Preffered Codec | DHCP Settings | HTTP Provisioning | HTTPS Provisioning | Hot Desking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| S500 | 2.0.4 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | |
| S505 | 3.0.4 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | |
| S700 | 2.0.4 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ | |
| S705 | 3.0.4 | ✔ | ✔ | ✘ | ✘ | ✔ | ✔ | ✔ | ✔ | ✘ | ✘ |