Auto Provision Akuvox Intercom Device with Yeastar P-Series Software Edition

Requirements

The firmwares of Akuvox Door Phone, Akuvox Indoor Monitor and Yeastar PBX meet the following requirements.

Scenarios

The provisioning methods and operations vary depending on the network environment of Akuvox Intercom Device and Yeastar PBX, as the following table shows:

Auto provision Akuvox intercom device in the same subnet (PnP)

In this example, the Akuvox intercom device (IP: 192.168.28.193) and the Yeastar PBX (IP: 192.168.28.39) are both deployed in 192.168.28.0/24 subnet.

Auto provision Akuvox intercom device in different subnets (DHCP)

In this example, the Akuvox intercom device and a DHCP server are deployed in the 192.168.28.0/24 subnet, with the device receiving its IP from the DHCP server, while the Yeastar PBX (IP: 192.168.20.58) is deployed in the 192.168.20.0/24 subnet.

Prerequisites

• RESET the intercom device if it is previously used.
• Make sure that there is only one DHCP server running in the subnet where the intercom device is deployed, or the intercom device would fail to obtain an IP address.
• Gather information of the intercom device, including Vendor, Model, and MAC address.
• Make sure that the intercom device and the PBX can communicate with each other over the subnets.
• Make sure that you have downloaded the template for the desired device model on the PBX (Path: Auto Provisioning > Resource Repository > Default Templates).
• You have created a SIP extension on the PBX to be assigned to the intercom device.

Procedure

• Step 1. Enable Remote Registration feature for the extension on PBX
• Step 2. Add the Akuvox intercom device on PBX
• Step 3. Configure DHCP option 66 on DHCP server

Step 1. Enable Remote Registration feature for the extension on PBX

Enable the Remote Registration feature for the extension to be assigned to the intercom device, so that the extension can be registered in a different subnet.

1. Log in to PBX web portal, go to Extension and Trunk > Extension, edit the desired extension.
2. Click Security tab, select the checkbox of Allow Remote Registration in the SIP Security section.

   

3. Click Save and Apply.

Step 2. Add the Akuvox intercom device on PBX

Add the intercom device on PBX. The PBX will generate a configuration file based on the device's MAC address.

1. On PBX web portal, go to Auto Provisioning > Phones.
2. Click Add > Add.
3. In the IP Phone section, enter the following device information.

   

   • Vendor: Select Akuvox.
   • Model: Select the device model. In this example, select E16C V2.0.
   • MAC Address: Enter the MAC address of the intercom device.
4. In the Options section, configure the following settings.

   

   • Template: Select a desired template from the drop-down list.
     Note: You can select the default template corresponding to the intercom device, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
   • Provisioning Method: Select DHCP (In the Office).

     A provisioning link is automatically generated and displayed in the Provisioning Link field. This provisioning link points to the location where the device's configuration file is stored.

5. In the Assign Extension section, assign an extension to the intercom device.

   

   Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with a device and it is only allowed to be registered on one SIP endpoint.

   • To release the extension from the associated device, see Release an Extension from a Provisioned IP Phone/Gateway.
   • To assign the extension to the intercom device without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension.
6. Click Save.

Step 3. Configure DHCP option 66 on DHCP server

In the subnet where the intercom device is deployed, use the generated provisioning link to configure option 66 on the DHCP Server.

1. On PBX web portal, copy the provisioning link from the device's detail page.

   

2. On the DHCP server, set up option 66 with the provisioning link.

   In this example, the configuration on a router's DHCP server is shown below.

   

3. Reboot the intercom device.

Result

• The intercom device obtains its IP address from the DHCP server, automatically downloads the configurations from the PBX using the provisioning link acquired from Option 66, and applies the settings.
• The extension has been successfully registered on the intercom device. You can check the registration status on Auto Provisioning > Phone on the PBX web portal.

  

Auto provision Akuvox intercom device in remote network (Provison Link)

In this example, the Akuvox intercom device and a DHCP server are deployed in Network A, with the device receiving its IP from the DHCP server, and the Yeastar PBX is deployed in Network B.

Prerequisites

• Set up remote access on the PBX.

  Yeastar P-Series Software Edition supports to auto provision Akuvox intercom device remotely either using Yeastar FQDN or using Public IP address / external host / Yeastar domain name. According to the provisioning method you intend to use, make sure that you have completed the corresponding setup shown below.

  Method	Setting
  Using Yeastar FQDN	Subscribe to Enterprise Plan or Ultimate Plan for the PBX and ensure the FQDN is available. Create a SIP extension on the PBX and grant remote access permission for it to be registered with the intercom device: Grant remote SIP access permission for the extension, so that the extension can be registered remotely via FQDN (Path: System > Network > Yeastar FQDN > Features > SIP Access). If you have enabled IP restriction for Yeastar FQDN remote Web access, make sure that you have added the intercom device's IP address to the permitted IP list, so that the device can obtain configuration files from the PBX (Path: System > Network > Yeastar FQDN > Features > Remote Access > Web Access).
  Using Public IP address / external host / Yeastar domain name	Configure PBX network for remote access by a public IP address, by an external host domain name, or by a Yeastar domain name. Important: The following PBX ports MUST be forwarded for RPS provisioning. RTP ports SIP port Web Server port Create a SIP extension on the PBX and set up it for remote registration. Enable NAT for the extension (Path: Extension and Trunk > Extension > > Advanced > VoIP Settings > NAT). Enable Remote Registration feature for the extension (Path: Extension and Trunk > Extension > > Security > SIP Security > Allow Remote Registration).

• Make sure that you have downloaded the template for the desired device model on the PBX (Path: Auto Provisioning > Resource Repository > Default Templates).
• RESET the intercom device if it is previously used.
• Make sure that there is only one DHCP server running in the subnet where the intercom device is deployed, or the intercom device would fail to obtain an IP address.
• Gather information of the intercom device, including Vendor, Model, and MAC address.

Procedure

• Step 1. Add the Akuvox intercom device on PBX
• Step 2. Configure DHCP option 66 on DHCP server

Step 1. Add the Akuvox intercom device on PBX

Add the intercom device on PBX. The PBX will generate a configuration file based on the device's MAC address.

1. On PBX web portal, go to Auto Provisioning > Phones.
2. Click Add > Add.
3. In the IP Phone section, enter the following device information.

   

   • Vendor: Select Akuvox.
   • Model: Select the device model. In this example, select E16C V2.0.
   • MAC Address: Enter the MAC address of the intercom device.
4. In the Options section, configure the following settings based on your method.

   

   • Template: Select a desired template from the drop-down list.
     Note: You can select the default template corresponding to the intercom device, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
   • Provisioning Method: Select Provision Link - FQDN (Remote) or Provision Link (Remote) according to your need.

     A provisioning link is automatically generated and displayed in the Provisioning Link field. This provisioning link points to the location where the device's configuration file is stored.

5. In the Assign Extension section, assign an extension to the intercom device.

   

   Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with a device and it is only allowed to be registered on one SIP endpoint.

   • To release the extension from the associated device, see Release an Extension from a Provisioned IP Phone/Gateway.
   • To assign the extension to the intercom device without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension.
6. Click Save.

Step 2. Configure DHCP option 66 on DHCP server

In the subnet where the intercom device is deployed, use the generated provisioning link to configure option 66 on the DHCP Server.

1. On PBX web portal, copy the corresponding provisioning link from the device's detail page.

   

2. On the DHCP server, set up option 66 with the provisioning link.

   In this example, the configuration on a router's DHCP server is shown below.

   

3. Reboot the intercom device.

Result

• The intercom device obtains its IP address from the DHCP server, automatically downloads the configurations from the PBX using the provisioning link acquired from Option 66, and applies the settings.
• The extension has been successfully registered on the intercom device. You can check the registration status on Auto Provisioning > Phone on the PBX web portal.