MT 6 Dynamic Auto Provisioning

From Bicom Systems Wiki

Manufacturers

Contents

General information

In version v3.8.2 we introduced dynamic TFTP/HTTP provisioning.

Instead of writing configuration files to disk, files are now dynamically created by PBXware HTTP application and served to device when it sends a request to the server.

NOTE:

By default (with no username and password set) HTTP provisioning is disabled.

Setting HTTP Username and HTTP Password will automatically enable HTTP provisioning as well. Devices that do not support Digest HTTP authentication (username and password) cannot be auto-provisioned via HTTP, only via TFTP.

HTTP Username and HTTP Password are set under:

Settings -> Servers -> YourServerName (edit) -> Auto Provisioning (section) -> HTTP Username/HTTP Password

HTTP server

HTTP application is running under following location:

http://ip-address/prov
  • MAC configuration requests
Some examples of requests:
http://ip-address/prov/mac.cfg
http://ip-address/prov/cfg.mac
http://ip-address/prov/phonemac.cfg

Check Filename in each device section.

  • Filesystem files (firmwares etc)
http://ip-address/prov/sip.ld
  • Custom config files
http://ip-address/prov/aastra.cfg

MAC configuration files

To get configuration, devices ask for files that contain its MAC address. This configuration requires username and password.

Testing with curl

In order to perform testing of auto provisioning and to verify validity of content, one needs to use curl or web browser.

More information about curl you can find here:

http://curl.haxx.se

Here is an example of command:

 curl -i -u user:pass --digest http://ip-address/prov/mac.cfg

Parameters:

-i

Include HTTP protocol in output

-u 

Specify username:password for authentication

--digest

We support only digest HTTP authentication, therefore this is a mandatory parameter. If you do not specify it, curl will use Basic HTTP Authentication and it won't work.

--user-agent

This is how you can send a different User-Agent string, if you want to test HTML/XML Directory pages.

For instance:

--user-agent "Yealink SIP-T38"

Testing in browser is advisable, if you want to test validity of large XML output. Devices that require XML configuration will be served with text/xml Content-Type and this will be understood by browsers. You will then know if XML document is valid or not.

Testing with wget

In case curl is not installed (this will most often be the case on VPSes), users can use wget to perform testing.

Example command:

 wget -S -q http://username:password@ip-address/prov/mac.cfg -O-

Parameters:

-q

Turns off verbosity and progress bar from wget.

-S

Output should include HTTP headers.

--user

HTTP username, if not specified as part of the URL.

--password

HTTP password, if not specified as part of the URL.

-O-

Output to stdout instead of file.

-U=user-agent

Use it to set User-Agent.

For more options consult:

wget --help

in your PBXware shell.

Test HTTPS mode

HTTPS also works and will work on devices that support HTTPS. Some devices do not support self-signed certificate, therefore you will need to buy signed certificate.

curl command:

curl -i -u user:pass --digest --insecure https://ip-address/prov/mac.cfg

Additional options:

--insecure

This options accepts self-signed certificate as valid certificate.

HTTP response codes

Here is the list of HTTP response codes from HTTP service and its meaning:

 401 Authentication Required

This header will appear when username and password is not supplied. This lets device know it has to send username and password in next request.

 200 OK 

should follow after this request, in all other cases provisioning failed.

 403 Forbidden

This error will appear if you do not specify valid authentication information. It will also appear if tenant/server do not have HTTP username and password set.

 404 Not Found

This error has multiple meanings but some are:

- MAC address doesn't exist
- Device doesn't exist or can't be used for auto provisioning
- Device cannot handle HTML/XML Directory
- Custom route doesn't exist
- File path is wrong
- File doesn't exist
- Request can't be handled
 500 Internal Server Error

Something went horribly wrong. Usually some problematic SQL error. Please consult Bicom Systems support.

 200 OK

This happens if all is good and content is delivered to device.

HTTP logs

You can watch all devices and requests with this command (for HTTP traffic)

 cd /opt/pbxware
 tail -f pw/var/log/nginx/localhost.access_log

for HTTPS:

 cd /opt/pbxware
 tail -f pw/var/log/nginx/localhost.ssl_access_log

Output example:

 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" "-" 

Important bits are:

GET filename

This is what devices asked for.

200 2654

200 OK was sent, Content-Legth was 2654.

Please note, if authentication is needed, correct sequence is 401, then 200 OK.

Yealink SIP-T38G 38.0.23.22

Device User-Agent.

Syslog

Some devices can send logs via syslog.

In order to setup syslog-ng on Gentoo as syslog host, do this:

 Edit /etc/syslog-ng/syslog-ng.conf 
 nano /etc/syslog-ng/syslog-ng.conf

and add these lines on bottom:

 source net { udp(); };
 destination remote { file("/var/log/remote/$FULLHOST"); };
 log { source(net); destination(remote); };

Create directory /var/log/remote/

 mkdir /var/log/remote

Restart syslog-ng with:

 /etc/init.d/syslog-ng restart

Yealink Information

Provisioning method

Either HTTP or TFTP.

HTTPS works with any certificate if "Only Accept Trusted Certificates" is Disabled.

Yealink devices

T41 Series T42 Series T46 Series T48 Series T49G T52S T53 T54S T56A T58V T53W T54W T57W VP59

CP960 CP920 CP860

Filename

  • MAC.cfg

File Format

  • Format is different for T2xP and T3xP devices unless v.70 firmware is used.

Supported features

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
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
T27P 45.83.0.50
T27G 69.84.0.15
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
T31P 124.85.257.55
T31G 124.85.257.55
T32 32.70.1.33
T33P 124.85.257.55
T33G 124.85.257.55
T38 38.70.0.185
T40G 76.84.0.15
T41P 36.83.0.50
T41S 66.84.0.15
T42G 29.83.0.50
T42S 66.84.0.15
T41U 108.84.0.30
T42U 108.84.0.30
T43U 108.84.0.30
T46U 108.84.0.30
T48U 108.84.0.30
T46G 28.83.0.50
T46S 66.84.0.15
T48G 35.83.0.50
T48S 66.84.0.15
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
VP59 91.283.0.30
CP860 37.81.0.10 N/A
CP920 78.81.0.15 N/A
CP960 73.15.0.38
W52P 25.81.0.30 N/A
W56P 25.81.0.30 N/A
W60B 77.83.0.25 N/A
W80B 103.83.0.30 N/A
W90DM 130.85.0.10
T60P
T65P

00-symbols.png

Notes:

  • DST is not supported
  • 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.

Polycom Information

Provisioning method

Both TFTP and HTTP are supported.

HTTPS should work but requires valid certificate signed by pre-installed Certificate Authority. It cannot be a wildcard certificate.

Polycom devices

VVX 1500 VVX 600 VVX 500 VVX 400 VVX 300 VVX 201 VVX 101

Filenames

  • MAC.cfg
Asks for where config files are, where SIP firmware is.
  • phoneMAC.cfg
Main configuration file.
  • MAC-directory.cfg
BLF/Directory list.

Content Type

  • XML format

Supported features

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
IP550 4.0.3
IP560
IP601 3.1.8
IP650 4.0.3
IP670
IP5000
Poly Trio 8300 7.0.0.4265
VVX101 5.9.2
VVX201 5.9.2
VVX300 5.9.2
VVX310 5.7.1
VVX400 5.9.2
VVX410 5.7.1
VVX500 5.9.2
VVX600 5.9.2
VVX1500 5.7.1
VVX150 6.1.0
VVX250 6.1.0
VVX350 6.1.0
VVX450 6.1.0
VVX411 6.1.0
VVX501 6.1.0
VVX601 6.1.0
OBi2182 6.2.2
VVX150 OBi Edition 6.3.0.0
VVX250 OBi Edition 6.3.0.0
VVX350 OBi Edition 6.4.0.2
VVX450 OBi Edition 6.4.0.2

00-symbols.png

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 HowTo create 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 8851 Cisco 8841 Cisco 7821 Cisco 6851

Filename:

  • SIPmac.cnf
  • spa.cfg
  • mac.cfg
  • SEPmac.cnf.xml

Supported features

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
8841 11-3-3
8851 11-3-3
8865 11.2.3
7821 11.0.1 N/A
6851 11.0.1
7940 8.12
7941 8.5.4
7942
7945
7960 8.12
7961 8.5.4
7962
7965
7971
7975
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
SPA901
SPA941 5.1.8
SPA942
SPA962 6.1.5
SPA112 1.4.1 N/A N/A N/A
PAP2 5.1.6 N/A N/A N/A
SPA8000

00-symbols.png

Cisco 79X1 have very complicated XML output.

It is possible to provide default XML template for each device by creating template in:

/tftp/SEP_Default.xml /tftp/SEP_Device_7941.xml Template is attached in the document.

Documentation: http://www.voip-info.org/wiki/view/Asterisk+phone+cisco+79x1+xml+configuration+files+for+SIP

Firmware: http://software.cisco.com/download/navigator.html?mdfid=269065653&flowid=5255 (requires Cisco login)

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

HTTPS, HTTP & TFTP.

Some Grandstream devices support HTTP, but Basic authentication only.

Grandstream devices

GXV-3380 GXV-3370 GXV-3350 GXV-3275 GXV-2170 GXV-1782 GXV-1630 GXV-1628 GXV-1625 DP-750 DP-752

Filename

  • cfgMAC

File Format Format is binary and is not really human-readable. It consists of PXX=value fields.

You can pipe output to following command:

curl ... | hexdump -C -v

Supported features

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
GXP2000 1.2.5.3
GXP2124
GXP2160
DP750 1.0.3.23 N/A N/A
DP752 1.0.13.0 N/A N/A
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
GXP2130 1.0.9.69
GXP2135 1.0.9.108
GXP2140 1.0.11.3
GXP2170 1.0.8.53
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
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

00-symbols.png

Obihai Information

Provisioning Method

TFTP & HTTP

Obihai devices

OBi 1062 OBi 1032 OBi 1022 OBi 508 OBi 504 OBi 302 OBi 300

Filenames:

Main configuration file:

  • mac.xml

BLF/Directory list:

  • mac.xml

Supported features

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
OBi1022 5.0.0
OBi1032 5.0.0
OBi1062 5.0.0
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

00-symbols.png

VTech Information

Provisioning Method

TFTP

VTech devices

ET 605 ET 617 ET 635 ET 685 VDP 650 VSP 600 VSP 608 VSP 715 VSP 725 VSP 726 VSP 735 VSP 736

VCS 754

Filenames:

Main configuration file

  • xxx_mac.cfg (xxx = phone model)

BLF/Directory list

  • mac.xml

File Format:

Supported features

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
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
VCS754 1.1.4.0 N/A N/A

00-symbols.png

HTek Information

Provisioning Method

HTTP or TFTP

Htek devices

UC 926 UC 924 UC 923 UC 903 UC 902 UC 862 UC 842 UC 802

Filenames:

Main configuration file:

  • cfgMAC

Supported features

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
UC862
UC802
UC803
UC804
UC806
UC840
UC842
UC860
UC902P 2.0.4.4.25
UC903 2.0.4.4.25
UC912P 2.0.4.4.33
UC912G 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

00-symbols.png

Denwa Information

Provisioning Method

HTTPS, HTTP or TFTP

Denwa devices

Denwa DW-610P Denwa DW-310P Denwa DW-210P

Filenames:

Main configuration file:

Supported features

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

00-symbols.png

Mitel Information

Provisioning method

TFTP only, HTTP not possible as Mitel devices does not support username and password.

Mitel devices

Mitel 6867i

Filenames:

  • aastra.cfg
  • mac-directory.csv
Directory list in CSV format.

Supported features

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
6867i 4.3.0.2036

00-symbols.png

Gigaset Information

Provisioning method

HTTP only

Gigaset devices

Gigaset N720 Gigaset N510 Gigaset Maxwell Basic Gigaset Maxwell 2 Gigaset Maxwell 3 Gigaset Maxwell 4 Gigaset Maxwell 10

Filenames:

  • MAC

Supported features

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
N510 42.247
N720 70.110.00.000.00
N870 2.26.0
Maxwell Basic 2.22.7
Maxwell 2 2.22.7
Maxwell 3 2.22.7
Maxwell 4 3.13.13
Maxwell 10 5.1.1-195

00-symbols.png

Snom Information

Provisioning Method

TFTP or HTTP

Snom devices

Snom 320 Snom 360 Snom 710 Snom D120 Snom D315 Snom D335 Snom D345 Snom D375 Snom D385 Snom D715 Snom D717 Snom D735 Snom D745 Snom D765 Snom D785 Snom PA1 Snom M300 Snom M900


Filenames:

  • snomXXX-mac.htm (XXX=320, 360..)

File Format:

  • Plain text

Supported features

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
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
PA1 8.7.5.75
M300 IPDECT-V2/05.00/B0001
M900 IPDECT-V2/05.00/B0001

00-symbols.png

Huawei Information

Provisioning Method

OPTION 246 only

Huawei devices

eSpace 7910 eSpace 7950

Filenames:

  • mac.xml

Supported features

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

00-symbols.png

Fanvil Information

Provisioning Method

HTTPS, HTTP & TFTP

Fanvil devices

Fanvil X6 Fanvil X5S Fanvil X4G Fanvil X4 Fanvil X3SP Fanvil X3G Fanvil X2P Fanvil H5 Fanvil H3 Fanvil X7 Fanvil X7C Fanvil X210

Filenames:

Main Configuration file:

  • mac.cfg

BLF/Directory list:

  • mac.csv

Supported features

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
X2P 2.2.0.3753 N/A
X3G 2.2.0.3685
X3SP 2.2.0.3685
X4 2.0.3.3019
X4G 2.2.0.3685
X5S 0.9.0
X6 0.7.0.1
X7 1.0.15
X7C 1.0.15
X210 1.0.13

00-symbols.png

Panasonic Information

Provisioning Method

HTTP & TFTP

Panasonic devices

Panasonic UTG300B Panasonic TGP550

Filenames:

Main Configuration file:

  • mac.cfg

Supported features

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-UTG300B 3.137 N/A
KX-TGP550 12.9 N/A N/A
KX-HDV130
KX-HDV230C HDV230/11.180 N/A
KX-HDV330C HDV330/11.100 N/A
KX-UT113
KX-UT123
KX-UT133
KX-UT136

00-symbols.png

Alcatel Information

Provisioning Method

HTTPS, HTTP & TFTP

Alcatel devices

Alcatel IP800 Alcatel IP600 Alcatel IP300 Alcatel IP200 Alcatel IP150 Alcatel IP100 Alcatel IP2015

Filenames:

Main Configuration file:

  • Alcatel_IPxxx-MAC.cfg

Supported features

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
IP800 15.70.0.136
IP600 14.70.0.144
IP300 1.0.5b
IP200 13.70.0.144 N/A
IP150 0.64.2a
IP100 0.64.6b N/A N/A N/A
IP2015 1.0.5b N/A N/A N/A
IP1020
M3 2.12.07.010.1828
M7 2.12.04.000.1720

00-symbols.png

Aastra Information

Provisioning method

TFTP only, HTTP not possible as Aastra devices does not support username and password.

Aastra devices

Aastra 57i Aastra 55i Aastra 53i

Filenames:

  • aastra.cfg
  • mac.cfg
  • mac-directory.csv
Directory list in CSV format.

File Format

  • Plain text

Supported features

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

00-symbols.png

ReadyNet devices

Provisioning method

TFTP only, HTTP not possible as ReadyNet devices does not support username and password.

ReadyNet devices

AC1200MS AC1000MS AC1100MSF QX300

Filenames:

  • MAC.conf

File Format

  • Plain text

Supported features

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

00-symbols.png

Sangoma Information

Provisioning method

TFTP only, HTTP not possible as Sangoma devices do not support username and password.

Sangoma devices

Sangoma S500 Sangoma S505 Sangoma S700 Sangoma S705

Filenames:

  • cfgMAC

Supported features

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

00-symbols.png


Next -> 27. Account Settings