Auto-provisioning
From Taridium
(Difference between revisions)
(→Auto Provisioning Process) |
|||
| Line 7: | Line 7: | ||
== Auto Provisioning Process == | == Auto Provisioning Process == | ||
| - | #User is created and along with it a file identified by the phone MAC address | + | #User is created and along with it a file identified by the phone MAC address. This file contains SIP/IAX registration information and other phone configuration details. |
#Phone is connected to the network and requests an IP address via DHCP | #Phone is connected to the network and requests an IP address via DHCP | ||
#DHCP server sends IP address and TFTP Boot Server information (usually ipbx IP address) | #DHCP server sends IP address and TFTP Boot Server information (usually ipbx IP address) | ||
#Phone uses DHCP boot server to download configuration file via TFTP/FTP/HTTP | #Phone uses DHCP boot server to download configuration file via TFTP/FTP/HTTP | ||
#Phone uses downloaded information to register with ipbx | #Phone uses downloaded information to register with ipbx | ||
Revision as of 19:46, 24 November 2008
Auto provisioning allows you to connect your phones to ipbx without the need to manually configure anything directly on your phones.
Proper auto-provisioning usually requires special DHCP configuration and correct device templates.
ipbx uses almost exclusively the phone MAC address to identify a phone. This address is usually also part of the configuration file name.
Auto Provisioning Process
- User is created and along with it a file identified by the phone MAC address. This file contains SIP/IAX registration information and other phone configuration details.
- Phone is connected to the network and requests an IP address via DHCP
- DHCP server sends IP address and TFTP Boot Server information (usually ipbx IP address)
- Phone uses DHCP boot server to download configuration file via TFTP/FTP/HTTP
- Phone uses downloaded information to register with ipbx
