Managing Existing Phones

  • From within the Sangoma Portal at https://portal.sangoma.com click on the Products > Sangoma Phones > List to view all phones registered with your organization or search by MAC address for any phone registered with your organization.  If you are a reseller, you can also see all Phones registered to sub organizations under you.

     

  • Picking the List All Phones option will show you all phones in a grid view

     

  • Clicking on the Manage button will allow you to edit the settings for that phone.

  • From here you can change the organization the phone is registered with under the General Information section and provide a friendly name for this phone.

     

  • From here we need to enable the redirect service under Zero Touch Configuration and define where the phone should reach the PBX at for configuration information.

    • Redirection Enabled- Enable the redirect server to point phone configuration request to the below destination.

    • Redirection Type

      • IP/FQDN- Provide a IP Address or FQDN to redirect all provisioning requests from this MAC address to.

      • Deployment - This will show a list of PBX Deployments that you have setup in the portal and stored the provisioning information for.

        • For more information on how to store the provisioning information for your Deployment review our Wiki on Redirect Server setup wiki here.

    • If using IP/FQDN for Redirection Type fill in the following information

      • IP/FQDN Protocol-

        • HTTP- Will use HTTP with the IP address you define in the IP/FQDN Address field along with the port number.  Enabled by default on your PBX but your port number may be different so please verify the port used for Phone Provisioning in your PBX System Admin module under Port Management section as shown in this wiki.

        • HTTPS- Will use SSL HTTP known as HTTPS with the IP address you define in the IP/FQDN Address field along with the port number. This will only work if you have HTTPS enabled on your PBX and have setup the proper ports for it in System Admin module Port Management section as shown in this wiki..

        • FTP- Will use FTP to pull configuration files.  This requires your PBX to be setup with FTP provisioning and will require you to provide the username and password for the FTP user that you have setup in System Admin module under Provisioning Protocols section as shown in this wiki.

        • TFTP- Will use TFTP to pull the configuration files.  Not recommended for remote phones.

      • IP/FQDN Address-

        • Define the address for the HTTP, HTTPS, FTP or TFTP.  

        • When using HTTP or HTTPS you need to also define the port number in the IP address.  By default your PBX should be setup for port 83 for HTTP provisioning but verify what port you have setup from the Port Management page of your System Admin module as outlined in this wiki in your PBX and if the phone is remote to the PBX you will need to make sure your firewall has this port opened.  If your PBX is setup with a Username and Password for HTTP/HTTPS/FTP for phone provisioning as defined in the System Admin module under Provisioning Protocols section as shown in this wiki you need to include that in the IP/FQDN string as shown below.

          • If your PBX was setup with HTTP on port 83 your IP/FQDN address would be 10.4.0.1:83

          • If your PBX was setup with HTTP on port 83 and also a username and password enabled for provisioning your IP/FQDN address would be username:password@10.4.0.1:83

        • When using FTP you will need to provide the Username and Password in the URL such as username:password@192.168.0.2

  • If using Deployment for Redirection Type fill in the following information

    • Deployment - Start typing in the deployment ID or location name of the PBX you want to link this phone to.  It will pull the redirection information such as protcol, address and port number from the deployment as outlined on Redirect Server setup wiki here.

  • Press Submit when done to save your changes

Return to Documentation Home I Return to Sangoma Support