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.
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
Yealink
Filename
- MAC.cfg
File Format
- Format is different for T2xP and T3xP devices unless v.70 firmware is used.
Polycom
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
Cisco
Filename
- SIPmac.cnf
- spa.cfg
- mac.cfg
- SEPmac.cnf.xml
Grandstream
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
Snom
Filenames:
- snomXXX-mac.htm (XXX=320, 360..)
File Format:
- Plain text
Fanvil
Filename:
- mac.cfg
BLF/Directory list:
- mac.csv