Zero Touch Provisioning through the Phone Import Wizard

 

 

The Phone Import Wizard allows for easy uploading the information of a bulk of phones to the Portal under your Organization´s account. The Zero Touch Provisioning redirection service can also be easily configured for all of those phones through here, we'll detail the process for this provisioning in this article.

Pre-requisites

For Zero Touch Provisioning,  you need to make sure the following parameters are configured on your FreePBX/PBXact server:

I. "HTTP Provisioning" as well as "RESTful Phone Apps" ports are enabled for HTTP/HTTPS (under: Modules > Admin > System Admin > Port Management):

II. For security reasons, it is recommended to password protect the provisioning of the phones (under: Modules > Admin > System Admin > Provisioning Protocols):

The possibility to password protect the provisioning is available in the "System Admin Pro" module only. It is already is included in PBXact.

Take note of the "HTTP(s) Username" and "HTTP(s) Password" credentials as you will be using them later in the Sangoma Portal.

 

III. In the EndPoint Manager's "Global Settings", configure the IP-PBX's Internal and/or External Addresses (under: Modules > Settings > EndPoint Manager > Global Settings) accordingly if your Sangoma s series phones are located in the same LAN as the IP-PBX and/or they reach the IP-PBX via a WAN/Internet interface respectively. Also, for later being able to use the "Login Int" / "Login Ext" HotDesking PhoneApp provisioning method, make sure the "XML-API (RestAPI) Default Login" parameter is enabled (set to 'Yes'):

If going through the IP-PBX's firewall, make sure that the provisioning ports, shown inside the green square above, are accessible by the phones (can be modified under: Modules > Connectivity > Firewall > Services > Extra Services). Access to those ports must also be open in any other firewall that may be in the path between the IP-PBX and the phones.

 

Enabling the Zero Touch Provisioning redirection service for the phones with the Phone Import Wizard

1. Go to the "Phone Import Wizard" page inside the Sangoma Portal (under: My Products > Sangoma Phones > Phone Import Wizard):

2. Fill the text box that will be displayed with the MAC addresses of all of the Sangoma s series phones for which you want to enable the Zero Touch Provisioning redirection service, each MAC address must be separated by a comma ( "," ). Then click Next

3. Click en "Enable Redirection" and fill out the parameters that get displayed: "Redirection Type", "Protocol", "IP/FQDN for PBX", "Username", and "Password" as follows (note that the Username and Password credentials are the ones obtained from the IP-PBX under "Provisioning Protocols", see Pre-requisite II above):

4. After clicking on "Review and import phones", the result of the phone import process will be displayed:

5. By now you should boot/reboot your Sangoma s series phones. Right after the booting process is completed, your phone should display a "Login Int" and/or "Login Ext" HotDesking PhoneApp button(s) on the top left of the screen as follows (example taken from an s705):

6. Just press the corresponding Login soft button, depending if your phone is within the same LAN the IP-PBX is located (Login Int) or if it reaches the IP-PBX via a WAN/Internet interface (Login Ext). You will then be required to authenticate: as the 'Extension' just enter the extension number you want to provision that phone with, and, as the 'Password', that extension's voicemail password; if that extension does not have voicemail enabled, then use the "Phone Admin Password" or the "Phone User Password" defined in the Global Settings of the EndPoint Manager (see Pre-requisite III above).

7. The phone should automatically reboot once more after which it will remain properly registered to the extension used on step 6.

 

Appendix

If, for some reason the phone does not show the Login button(s) after the first reboot, or fails to register after the second, automatic, reboot, it may be that some previous configurations (mainly the currently stored provisioning server parameters) are interfering with it. Just Factory Reset it (in its webUI under: Management > Upgrade > Reset to Factory):

Return to Documentation Home I Return to Sangoma Support