Provision Yealink IP Phones on Multiple Servers

When you want to conduct IP phone diagnostics and manage the IP phones on the Yealink device management platform, and assign extension, supply configuration files and upgrade device firmware for the IP phones on Yeastar P-Series PBX System, you can provision the IP phones on both servers.

Applications

This topic is applied to the remote deployment of the following Yealink IP phones.

Model Phone Requirement PBX Requirement Supported Auto Provisioning Method
CP920 78.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
CP925 148.86.0.5 or later 37.5.0.9 or later
  • PnP
  • DHCP
  • RPS
CP960 73.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
CP965 143.86.0.5 or later 37.5.0.9 or later
  • PnP
  • DHCP
  • RPS
SIP-CP935W 149.86.0.5 or later 37.5.0.9 or later
  • PnP
  • DHCP
  • RPS
SIP-T19P_E2 53.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T21P_E2 52.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T21_E2 52.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T23P 44.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T23G 44.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T27G 69.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T29G 46.83.0.120 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T30 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T30P 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T31 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T31G 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T31P 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T31W 124.86.0.75 or later

37.11.0.56 or later

  • PnP
  • DHCP
  • RPS
SIP-T33G 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T33P 124.85.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T34W 124.86.0.75 or later

37.12.0.23 or later

  • PnP
  • DHCP
  • RPS
SIP-T40P 54.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T40G 76.84.0.125 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T41P 36.83.0.120 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T41S 66.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T41U 108.85.0.39 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T42G 29.83.0.120 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T42S 66.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T42U 108.85.0.39 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T43U 108.85.0.39 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T44U 108.86.0.90 or later

37.10.0.32 or later

  • PnP
  • DHCP
  • RPS
SIP-T44W 108.86.0.90 or later

37.10.0.32 or later

  • PnP
  • DHCP
  • RPS
SIP-T46G 28.83.0.120 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T46S 66.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T46U 108.85.0.39 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T48G 35.83.0.120 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T48S 66.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T48U 108.85.0.39 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T52S 70.84.0.70 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T53 96.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T53W 96.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T54S 70.84.0.70 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T54W 96.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T56A 58.83.0.15 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T57W 96.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T58 58.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
SIP-T58W 150.86.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
VP59 91.85.0.5 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
W60B (W53P, W41P, W60P, CP930W-Base) 77.83.0.85 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
W70B (W79P, W76P, W73P) 146.85.0.20 or later

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
W80B W80DM-103.83.0.80

37.2.0.7 or later

  • PnP
  • DHCP
  • RPS
W90DM 130.85.0.15 or later

37.2.0.80 or later

  • PnP
  • DHCP
  • RPS

Prerequisites

You have an account of the Yealink Device Management Platform.

Procedure

Step 1. Add IP phones on Yealink device management platform

  1. Log in to the Yealink Device Management Platform.
  2. Go to Device Management > Phone Device, click Add device to add a phone.
    1. Complete the following configurations.

      • Device Name: Specify a device name.
      • Site: Select a site in the drop-down list.
      • Model: Select the phone model in the drop-down list.
      • MAC: Enter the MAC address of the IP phone.
      • Machine ID: Enter the serial number of the IP phone.
      • Synchronize to RPS: Enable this feature to synchronize the IP phone to RPS server.
    2. Click OK.
  3. Reboot the IP phone.

    The phone is connected to the Device Management Platform, and the status displays "Online" on the platform.

Step 2. Add IP phones on the PBX

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

    • Vendor: Select Yealink.
    • Model: Select the phone model. In this example, select SIP-T53W.
    • MAC Address: Enter the MAC address of the IP phone.
  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 phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
    • Provisioning Method: Select RPS (Remote).

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

    • Authentication for the First-time Auto Provisioning: If enabled, users are requested to fill in authentication information on the IP phones before triggering the first-time provisioning.
      Note: We recommend that you keep this option selected.
  5. In the Assign Extension section, assign an extension to the IP phone.

    Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone or gateway.
  6. Click Save.

    The PBX will send an event notification of RPS Request Success.

Configure global Auto Provisioning URL on Yealink Device Management Platform

  1. Log in to 'Yealink Device Management Platform.
  2. Go to Device Configuration > Global Parameter Settings.
  3. Paste the PBX provisioning link in the Auto Provisioning URL.

  4. Click Save and update.
  5. In the pop-up dialog box, click OK to update the settings.