Step 4. Auto Provision Phones

Supported devices

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	Grant remote SIP access permission for the migrated extensions associated with the phones, 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 phone's IP address to the permitted IP list. (Path: System > Network > Yeastar FQDN > Features > Remote Access > Web Access).
  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

Before migrating IP phones, obtain the provisioning link that will serve as the new provisioning server URL to be bound to the phones.

2. Migrate IP phones from 3CX to Yeastar Phone System

You can migrate IP phones from 3CX to Yeastar Phone System according to the provisioning templates originally used to deploy these phones.

• If the phones are originally provisioned via a 3CX custom template, migrate them in bulk by modifying the template.
• If the phones are originally provisioned via a 3CX default template, migrate them one by one by configuring the provisioning server URL on each individual phone.

Tip: You can check provisioning template of a phone on 3CX management console (Path: Admin > Phones > > Edit User > IP Phone > Phone Model (Normal Phone)).

If the value displayed in Phone Model (Standard Phone) follows the format [Device Model]-[Custom Name].ph, this indicates the phone is provisioned via a custom template. Otherwise, it uses the default template.

Reprovision phones originally provisioned via a 3CX custom provisioning template in bulk

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

   

   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 provisioning server URLs used to download configuration files, 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 server URL accordingly.
   4. Click Save.
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.

Reprovision an IP phone originally provisioned via a 3CX default provisioning template

1. Log in to the web interface of the desired phone.
2. Replace the provisioning server URL used to download configuration files.

   

   

   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 reprovision other phones, repeat step 1 - 3.

Result

The phones automatically download configuration files from the provisioning server and apply the new settings.

You can check the phone 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.