# Provision Akuvox Intercom Device with Cloud Voice

Cloud Voice can provision Akuvox IP intercom hardware the same way it provisions desk phones. Assign an extension to a door phone and another to an indoor monitor, and Cloud Voice (the PBX, short for Private Branch Exchange) routes an entry call from the door phone straight to the monitor. Whoever answers can talk to the visitor and trigger the door release without leaving their desk.

The workflow below adds the intercom to Cloud Voice, then points it at the PBX using DHCP option 66 so it pulls its configuration automatically on boot.

:::note
Every supported Akuvox intercom is provisioned the same way. The steps here use the E16C V2.0 door phone (firmware 216.30.10.85) as a worked example.
:::

## Supported models and firmware

Confirm that your intercom hardware and the PBX are running compatible firmware before you begin.

| Device | Type | Minimum device firmware | Minimum PBX firmware |
|--------|------|-------------------------|----------------------|
| E16C V2.0 | Door phone | 216.30.10.85 | 84.21.0.66 |
| R20A | Door phone | 320.30.11.112 | 84.21.0.66 |
| S562W | Indoor monitor | 562.30.14.48 | 84.21.0.66 |
| S563W | Indoor monitor | 563.30.13.202 | 84.21.0.66 |

## Before you start

- Factory-reset the Akuvox device if it has been used previously.
- Make sure the subnet where the intercom will live has exactly one DHCP (Dynamic Host Configuration Protocol) server running. A second DHCP server prevents the device from obtaining an IP address.
- Note the device's vendor, model, and MAC (Media Access Control) address.
- Download the default provisioning template for your device model in Cloud Voice, under **Auto Provisioning > Resource Repository > Default Templates**.
- Create the SIP (Session Initiation Protocol) extension you plan to assign to the intercom.

:::caution
A factory reset erases the intercom's current configuration, including any existing SIP registration and door-release settings. Only reset a device that is new to this deployment or one you are certain you can reconfigure.
:::

## Step 1. Add the intercom to Cloud Voice

Registering the device in the PBX generates a configuration file keyed to its MAC address.

1. In the Cloud Voice portal, go to **Auto Provisioning > Phones**.
2. Click **Add > Add**.
3. Under **IP Phone**, fill in the device details.

   ![Adding an Akuvox intercom with vendor, model, and MAC address fields](/images/pbx/add-akuvox-phone.png)

   - **Vendor**: Select **Akuvox**.
   - **Model**: Select your device model, **E16C V2.0** in this example.
   - **MAC Address**: Enter the intercom's MAC address.

4. Under **Options**, pick a template from the **Template** drop-down list.

   :::note
   Use the default template that matches your device, or build your own custom template if you need to change the defaults.
   :::

   
   ![Cloud Voice, template selection with an auto-generated provisioning link](/images/pbx/akuvox-option-cloud.png)

   Cloud Voice fills in the **Provisioning Link** field automatically. This link points to where the device's configuration file is stored, and you will need it in Step 2.

5. Under **Assign Extension**, assign an extension to the intercom.

   ![Assigning a SIP extension to the intercom device](/images/pbx/assign-an-extension-pnp.png)

   :::note
   If the extension you want isn't in the list, it's already bound to another device and can register on only one SIP endpoint. You have two options:

   - Release the extension from the device it's currently provisioned to, then assign it here.
   - Enable concurrent registration on the extension so it can register on more than one endpoint at once.
   :::

6. Click **Save**.

## Step 2. Set DHCP option 66 on the DHCP server

Hand the provisioning link to the DHCP server that serves the intercom's subnet, using option 66.

:::note
DHCP option 66 is the field a DHCP server uses to tell devices where to download their configuration (the provisioning server address). On boot, the intercom reads this value and fetches its settings from Cloud Voice. Option 66 is served to every device in the subnet, so confirm nothing else there relies on a different provisioning server before you change it.
:::

1. In the Cloud Voice portal, open the device's detail page and copy its provisioning link.

   
   ![Cloud Voice, copying the provisioning link from the device detail page](/images/pbx/akuvox-dhcp-link-pce.png)

2. On the DHCP server, set option 66 to the provisioning link. The example below shows the setting on a router's built-in DHCP server.

   
   ![Cloud Voice, DHCP option 66 configured with the provisioning link on a router](/images/pbx/gs-dhcp-setting-pce.png)

3. Reboot the intercom.

## Result

- On boot, the intercom pulls an IP address from the DHCP server, reads the provisioning link from option 66, downloads its configuration from Cloud Voice, and applies it.
- The extension registers on the device. Confirm the registration status under **Auto Provisioning > Phones** in the Cloud Voice portal.

![Provisioned Akuvox intercom showing a registered extension in the phones list](/images/pbx/akuvox-provisioned-pce.png)