# Auto Provision a Flyingvoice IP Phone

Cloud Voice can push an extension's configuration to a Flyingvoice IP (Internet Protocol) phone for you, so the device registers with the PBX (Private Branch Exchange, the phone system that routes your calls) without any manual SIP (Session Initiation Protocol) entry. You add the phone on the PBX, then trigger a one-time authentication on the handset. The steps below use a Flyingvoice P20P (firmware V0.8.18.6) as the example, but the same flow applies to every supported model.

## Supported models and firmware

Auto provisioning works only when both the handset and your Cloud Voice system meet the minimum firmware shown here. Confirm your device's model and running firmware before you begin.

| Model | Minimum phone firmware | Minimum Cloud Voice version |
|-------|------------------------|-----------------------------|
| FIP10 | 0.7.23.1 | 84.8.0.25 |
| FIP11C | 0.7.23.1 | 84.8.0.25 |
| FIP12WP | 0.7.23.1 | 84.8.0.25 |
| FIP13G | 0.7.23.1 | 84.8.0.25 |
| FIP14G | 0.7.23.1 | 84.8.0.25 |
| FIP15G | 0.7.23.1 | 84.8.0.25 |
| FIP15G Plus | 0.7.23.1 | 84.8.0.25 |
| FIP16 | 0.7.23.1 | 84.8.0.25 |
| FIP16 Plus | 0.7.23.1 | 84.8.0.25 |
| P10 | V0.7.56 | 84.9.0.20 |
| P10P | V0.7.56 | 84.9.0.20 |
| P10G | V0.7.56 | 84.9.0.20 |
| P10W | V0.7.56 | 84.9.0.20 |
| P10LTE | V0.7.56 | 84.9.0.20 |
| P11 | V0.7.56 | 84.9.0.20 |
| P11P | V0.7.56 | 84.9.0.20 |
| P11G | V0.7.56 | 84.9.0.20 |
| P11W | V0.7.56 | 84.9.0.20 |
| P11LTE | V0.7.56 | 84.9.0.20 |
| P20 | V0.7.57 | 84.9.0.20 |
| P20P | V0.7.57 | 84.9.0.20 |
| P20W | V0.7.57 | 84.9.0.20 |
| P20G | V0.7.57 | 84.9.0.20 |
| P21 | V0.7.57 | 84.9.0.20 |
| P21P | V0.7.57 | 84.9.0.20 |
| P21W | V0.7.57 | 84.9.0.20 |
| flyphone | V0.7.57 | 84.9.0.20 |
| P22P | V0.7.57 | 84.9.0.20 |
| P22G | V0.7.57 | 84.9.0.20 |
| P23G | V0.7.57 | 84.9.0.20 |
| P23GW | V0.7.57 | 84.9.0.20 |
| P24G | V0.7.57 | 84.9.0.20 |
| i86Box_Basic | V0.0.16.1 | 84.9.0.20 |
| i86Box_Indoor | V0.0.16.1 | 84.9.0.20 |
| i86Box_2Line | V0.0.16.1 | 84.9.0.20 |
| i86Box_PCBA | V0.0.16.1 | 84.9.0.20 |
| i86Box_NFC | V0.0.16.1 | 84.9.0.20 |

:::caution
These firmware versions are hard minimums, not suggestions. If either the phone or your Cloud Voice system is on an older build, provisioning will not complete and the extension will not register. Update whichever side is out of date to a supported version before you add the phone.
:::

## Before you begin

- Download the default provisioning template for your phone model from **Auto Provisioning > Resource Repository > Default Templates**. Without this template, the model has nothing to provision from.
- If the phone was used previously, reset it to factory defaults first.

  :::caution
  Only reset a phone that is not currently in service. A factory reset erases the phone's existing configuration and any account registered on it, so resetting a handset that someone is still using will drop its registration and its calls.
  :::

- Have the phone's details on hand: vendor, model, and MAC (Media Access Control) address. The MAC address is the phone's unique hardware ID, usually printed on a label on the underside of the phone or on its box.

## Step 1: Add the phone on the PBX

1. Sign in to the PBX web portal and open **Auto Provisioning > Phones**.
2. Click **Add > Add**.
3. Under **IP Phone**, fill in the device details:

   ![Adding a Flyingvoice phone by vendor, model, and MAC address](/images/pbx/add-flyingvoice-phone.png)

   - **Vendor**: Choose **Flyingvoice**.
   - **Model**: Choose the phone model. This example uses **P20P**.
   - **MAC Address**: Type the phone's MAC address.

4. Under **Options**, set the following:

   
   ![Cloud Voice, provisioning options with template, provisioning link, and first-time authentication](/images/pbx/flyingvoice-option-cloud.png)

   - **Template**: Pick a template from the list. You can use the default template that matches the model, or a custom template you have created.
   - **Provisioning Link**: This is generated for you and points to where the phone's configuration file is stored. No action needed.
   - **Authentication for the First-time Auto Provisioning**: When on, the phone prompts the user for authentication details before the first provisioning runs.

   :::tip
   Leave **Authentication for the First-time Auto Provisioning** enabled. It protects the initial configuration download so a stranger's device cannot pull the extension's settings.
   :::

5. Under **Assign Extension**, select the extension to bind to this phone.

   ![Assigning an extension to the phone during setup](/images/pbx/assign-an-extension-pnp.png)

   :::note
   If the extension you want isn't in the list, it's already tied to another phone. Either release it from that phone first, or enable concurrent registration on the extension so it can register to more than one device. By default an extension registers to a single SIP endpoint (one device).
   :::

6. Click **Save**. The PBX reports an **RPS Request Success** event notification.

   :::note
   RPS stands for Redirection and Provisioning Service. This event confirms the cloud provisioning service accepted the request, so the phone will be pointed to its configuration file the next time it boots.
   :::

## Step 2: Authenticate the phone

1. Reboot the phone. Once it finishes starting up, an HTTP (web) Authentication prompt appears on the screen.
2. Press **OK** to open the **Auto Provision** page.
3. On the **Auto Provision** page, set these fields:

   1. Scroll to **User Name** and enter the extension number assigned to the phone.

      ![Entering the extension number in the User Name field](/images/pbx/flyingvoice-auth-name.png)

   2. Scroll to **Password** and enter the extension's Voicemail Access PIN (Personal Identification Number).

      ![Entering the Voicemail Access PIN in the Password field](/images/pbx/flyingvoice-auth-pwd.png)

      :::note
      Find the Voicemail Access PIN on the **Voicemail** tab of the extension's configuration page in the PBX.

      
      ![Cloud Voice, Voicemail Access PIN shown on the extension's Voicemail tab](/images/pbx/ext-vm-pin.png)
      :::

   3. Scroll to **HTTP Authentication** and select **Basic**.

      ![Setting HTTP Authentication to Basic on the phone](/images/pbx/flyingvoice-auth-mode.png)

   4. Press **Save**. The phone asks whether to update now.
   5. Press **OK** to start the update.

## Result

- The phone downloads its configuration from the PBX and applies the settings.
- The extension registers on the phone. Confirm the registration status under **Auto Provisioning > Phones** in the PBX web portal.

![Provisioned Flyingvoice phone showing a registered extension in the phone list](/images/pbx/flyingvoice-provisioned-pce.png)
