Step 4. Auto Provision Phones

After migrating phones to Yeastar Phone System, you need to take further actions to make the phones provisioned. This topic takes Fanvil X4U (firmware: 2.4.13) as an example to introduce how to provision phones with Yeastar Phone System.

Supported devices

Note: The following table shows the 3CX-supported phones that can be migrated. Many more phones of different vendors are supported on Yeastar Phone System. For more information, see (Software Edition) Auto Provisioning - Supported Devices and (Cloud Edition) Auto Provisioning - Supported Devices.
Vendor Model Supported Auto Provisioning Method
Fanvil
  • H2U, H2U-V2, H3, H3W, H5, H5W
  • i10S, i10SD, i10SV, i16S, i16SV, i18S, i20S, i23S, i30, i31S, i56A, i61, i62, i63, i64
  • PA2, PA3
  • V62, V64, V65
  • X1S, X1SG, X2, X210, X210-V2, X210i-V2, X2C, X301, X301G, X303, X303G, X3S, X3S(P) Lite, X3S(P) Pro, X3SG, X3SG Lite, X3SG Pro, X3U, X3U Pro, X4, X4U, X4U-V2, X5S, X5U, X5U-V2, X6, X6U, X6U-V2, X7, X7-V2, X7A, X7C, X7C-V2
  • PnP
  • DHCP
  • RPS
  • Provision Link
GrandStream
  • GRP-2601, GRP-2601P, GRP-2602, GRP-2602P, GRP-2602W, GRP-2603, GRP-2603P, GRP-2604, GRP-2604P, GRP-2612, GRP-2612P, GRP-2612W, GRP-2613, GRP-2614, GRP-2615, GRP-2616
  • GXP-1610, GXP-1620, GXP-1625, GXP-1628, GXP-1630, GXP-2130, GXP-2135, GXP-2140, GXP-2170
  • GXW4216, GXW4224, GXW4232, GXW4248
  • HT801, HT802, HT812, HT814, HT818
  • PnP
  • DHCP
  • Provision Link
Htek UC902, UC902S, UC903, UC912, UC912E, UC912G, UC921, UC923, UC924, UC924E, UC926, UC926E
  • PnP
  • DHCP
  • RPS
  • Provision Link
Polycom VVX 101, VVX 150, VVX 201, VVX 250, VVX 301, VVX 310, VVX 311, VVX 350, VVX 401, VVX 410, VVX 411, VVX 450, VVX 501, VVX 601
  • DHCP
  • RPS
  • Provision Link
Snom
  • D120, D315, D335, D385, D713, D717, D735, D785, D862, D865
  • M300, M400, M900
  • PnP
  • DHCP
  • RPS
  • Provision Link
Yealink
  • CP920, CP925, CP960, CP965
  • T19P E2, T21 E2, T21P E2, T23G, T23P, T27G, T30P, T31G, T31P, T33G, T33P, T40G, T40P, T41S, T41U, T42S, T42U, T43U, T46S, T46U, T48S, T48U, T52S, T53, T53W, T54S, T54W, T56A, T57W, T58, T58W, T29G
  • T73U, T73W, T74U, T74W, T77U, T85W, T87W
  • W60B, W70B, W75DM, W80DM, W90DM
  • PnP
  • DHCP
  • RPS
  • Provision Link

Prerequisites

The prerequisites vary based on your Yeastar Phone System.

Software Edition
The prerequisites vary depending on the phones' original provisioned method on 3CX.
  • For phones originally provisioned via Local LAN / VPN method on 3CX, the device and network deployment differs depending on whether the Prioritize Onsite Proxy for Auto Provisioning option is enabled for migration, as the following table shows:
    Prioritize Onsite Proxy for Auto Provisioning Prerequisites
    Enabled
    • The Yeastar Onsite Proxy is deployed in the same subnet as the phones and connected to the Software Edition.
    • The phones support PnP provisioning.
    Disabled
    • The phones and the Software Edition must be in the same LAN subnet.
    • The phones support PnP provisioning.
  • For phones originally provisioned via SBC / Router phone method on 3CX, the remote access settings differ depending on your configured PBX network settings, as the following table shows:
    Network Prerequisites
    Yeastar FQDN
    Public IP and Ports
    • Make sure RTP ports, SIP port, and Web Server port must be forwarded. For more information, see Configure Network for Remote Access by Public IP and Ports.
    • Enable NAT for the migrated extensions associated with the phones (Path: Extension and Trunk > Extension > > Advanced > VoIP Settings > NAT).

    • Enable Remote Registration feature for the migrated extensions associated with the phones (Path: Extension and Trunk > Extension > > Security > SIP Security > Allow Remote Registration).

Cloud Edition
Note: The following device and network deployment is required only if the Prioritize Onsite Proxy for Auto Provisioning option is enabled for migration.
  • The Yeastar Onsite Proxy is deployed in the same subnet as the phones and connected to the Cloud Edition.
  • The phones support PnP provisioning.

Procedure

1. Obtain provisioning link from Yeastar Phone System

  1. Log into Yeastar Phone System, go to Auto Provisioning > Phones.
  2. Click beside any phone.

2. Provision phones originally provisioned via 3CX custom provisioning templates in bulk

  1. Log in to 3CX management console.
  2. Modify the custom provisioning templates.

    1. Go to Admin > Advanced > Template.
    2. In the Phone Templates drop-down list, select the custom provisioning template currently used by your phones.
    3. In the template editing text box, locate the server IP addresses for downloading provisioning file, and replace them with the provisioning link obtained from Yeastar Phone System.
      In this example, search for "%%PROVLINKLOCAL%%" and "%%PROVLINK%%", replace them with provisioning link.
      Note: There may be multiple matching results in the template. Please identify and update the provisioning file URL accordingly.
    4. Click Save.
    5. To modify other custom provisioning templates used by your phones, repeat step b - d.
  3. Reprovision the phones.

    1. Go to Admin > Phones.
    2. Select all IP phones.
    3. Click Reprovision.
    4. In pop-up confirm window, click OK.

  4. Reboot the phones.

3. Provision phones originally provisioned via 3CX default provisioning templates

  1. Log in to phone web interface.
  2. Replace the server IP address for downloading provisioning file.

    1. Go to System > Auto Provision > Static Provisioning Server.
    2. In the Server Address field, replace the 3CX server IP address with the provisioning link obtained from Yeastar Phone System.
    3. Click Apply.
  3. Reprovision the phone using one of the following methods.
    • Click Autoprovision Now.

    • Reboot the phone.
  4. To provision other phones, repeat step 1 - 3.

Result

The phones are successfully provisioned with Yeastar Phone System. You can check the status on Yeastar Phone System (Path: Auto Provisioning > Phones).
Note: If the provisioning fails, you can troubleshoot as follows:
  • Check if the phone is provisioned by another PBX.
  • Factory reset the phone, then reboot it.