# Auto Provision Yealink IP Phone With auto provisioning, Cloud Voice delivers a complete configuration to a Yealink handset, and the phone registers its assigned extension on its own, with nothing to type on the device. The walkthrough below uses a Yealink SIP-T53W (firmware 96.85.0.5) as the example, but the same procedure covers every supported model. :::note - Yealink phones on firmware **V87** or later force a password change the first time they are used. For provisioning to run smoothly, turn on automatic random password generation for phones in the Auto Provisioning global settings. If you prefer not to, you can instead set an administrator password on each phone individually after adding it to the system, as described in Step 1 below. - By default, Cloud Voice encrypts the configuration files it builds for Yealink phones during provisioning. A phone that cannot decrypt these files will not apply the settings. If your phones lack decryption support, disable configuration file encryption for Yealink phones in the Auto Provisioning global settings. ::: ## Supported models and firmware Confirm that both the phone and your Cloud Voice system meet the minimum firmware levels for the model you plan to provision. | Model | Minimum phone firmware | Minimum system firmware | |-------|------------------------|-------------------------| | AX83H | 180.86.0.5 | 84.16.0.25 | | AX86R | 180.86.0.5 | 84.18.0.59 | | CP920 | 78.85.0.5 | 84.5.0.86 | | CP925 | 148.86.0.5 | 84.5.0.86 | | CP960 | 73.85.0.5 | 84.5.0.86 | | CP965 | 143.86.0.5 | 84.5.0.86 | | SIP-CP935W | 149.86.0.5 | 84.6.0.24 | | SIP-T19P_E2 | 53.84.0.125 | 84.5.0.86 | | SIP-T20P | 9.73.0.50 | 84.18.0.102 | | SIP-T21_E2 | 52.84.0.125 | 84.5.0.86 | | SIP-T21P_E2 | 52.84.0.125 | 84.5.0.86 | | SIP-T22P | 7.73.0.50 | 84.18.0.102 | | SIP-T23P | 44.84.0.125 | 84.5.0.86 | | SIP-T23G | 44.84.0.125 | 84.5.0.86 | | SIP-T26P | 6.73.0.50 | 84.18.0.102 | | SIP-T27G | 69.85.0.5 | 84.5.0.86 | | SIP-T28P | 2.73.0.50 | 84.18.0.102 | | SIP-T29G | 46.83.0.120 | 84.5.0.86 | | SIP-T30 | 124.85.0.15 | 84.5.0.86 | | SIP-T30P | 124.85.0.15 | 84.5.0.86 | | SIP-T31 | 124.85.0.15 | 84.5.0.86 | | SIP-T31G | 124.85.0.15 | 84.5.0.86 | | SIP-T31P | 124.85.0.15 | 84.5.0.86 | | SIP-T31W | 124.86.0.75 | 84.12.0.32 | | SIP-T32G | 32.70.0.125 | 84.18.0.102 | | SIP-T33G | 124.85.0.15 | 84.5.0.86 | | SIP-T33P | 124.85.0.15 | 84.5.0.86 | | SIP-T34W | 124.86.0.75 | 84.12.0.32 | | SIP-T38G | 38.70.0.185 | 84.18.0.102 | | SIP-T40P | 54.84.0.125 | 84.5.0.86 | | SIP-T40G | 76.84.0.125 | 84.5.0.86 | | SIP-T41P | 36.83.0.120 | 84.5.0.86 | | SIP-T41S | 66.85.0.5 | 84.5.0.86 | | SIP-T41U | 108.85.0.39 | 84.5.0.86 | | SIP-T42G | 29.83.0.120 | 84.5.0.86 | | SIP-T42S | 66.85.0.5 | 84.5.0.86 | | SIP-T42U | 108.85.0.39 | 84.5.0.86 | | SIP-T43U | 108.85.0.39 | 84.5.0.86 | | SIP-T44U | 108.86.0.90 | 84.10.0.32 | | SIP-T44W | 108.86.0.90 | 84.10.0.32 | | SIP-T46G | 28.83.0.120 | 84.5.0.86 | | SIP-T46S | 66.85.0.5 | 84.5.0.86 | | SIP-T46U | 108.85.0.39 | 84.5.0.86 | | SIP-T48G | 35.83.0.120 | 84.5.0.86 | | SIP-T48S | 66.85.0.5 | 84.5.0.86 | | SIP-T48U | 108.85.0.39 | 84.5.0.86 | | SIP-T52S | 70.84.0.70 | 84.5.0.86 | | SIP-T53 | 96.85.0.5 | 84.5.0.86 | | SIP-T53W | 96.85.0.5 | 84.5.0.86 | | SIP-T54S | 70.84.0.70 | 84.5.0.86 | | SIP-T54W | 96.85.0.5 | 84.5.0.86 | | SIP-T56A | 58.83.0.15 | 84.5.0.86 | | SIP-T57W | 96.85.0.5 | 84.5.0.86 | | SIP-T58 | 58.85.0.5 | 84.5.0.86 | | SIP-T58W | 150.86.0.5 | 84.5.0.86 | | SIP-T73W | 185.87.0.15 | 84.19.0.70 | | SIP-T73U | 185.87.0.15 | 84.19.0.70 | | SIP-T74LTE | 185.87.0.33 | 84.19.0.70 | | SIP-T74W | 185.87.0.15 | 84.19.0.70 | | SIP-T74U | 185.87.0.15 | 84.19.0.70 | | SIP-T77U | 185.87.0.15 | 84.19.0.70 | | SIP-T85W | 185.87.0.15 | 84.19.0.70 | | SIP-T87W | 185.87.0.15 | 84.19.0.70 | | SIP-T88W | 192.87.0.5 | 84.19.0.70 | | SIP-T88V | 192.87.0.5 | 84.19.0.70 | | SIP-W90DM | 130.85.0.15 | 84.5.0.86 | | VP59 | 91.85.0.5 | 84.5.0.86 | | W60B (W53P, W41P, W60P, CP930W-Base) | 77.83.0.85 | 84.5.0.86 | | W70B (W79P, W76P, W73P) | 146.85.0.20 | 84.5.0.86 | | W75DM | 175.85.0.5 | 84.14.0.26 | | W80B | W80DM-103.83.0.80 | 84.5.0.86 | | W90DM | 130.85.0.15 | 84.5.0.86 | | T64LTE | 132.86.0.25 | 84.16.0.71 | | T67LTE | 132.86.0.35 | 84.16.0.71 | ## Before you begin - Make sure the default provisioning template for your phone model has been added under **Auto Provisioning > Resource Repository > Default Templates**. - If the phone was in service before, reset it to factory defaults so old settings do not interfere. - Have the phone's vendor, model, and MAC (Media Access Control) address ready. The MAC address is the phone's unique hardware ID, usually printed on a label on the underside of the device. :::caution A factory reset wipes every setting on the handset, including any account it is currently registered to. Only reset a phone that is not in active use. ::: ## Step 1: Add the phone in Cloud Voice 1. Sign in to the management portal and go to **Auto Provisioning > Phones**. 2. Click **Add > Add**. 3. In the **IP Phone** section, identify the device: ![Add phone form with the vendor, model, and MAC address fields](/images/pbx/add-yealink-phone.png) - **Vendor**: Choose **Yealink**. - **Model**: Choose the phone model. This example uses **SIP-T53W**. - **MAC Address**: Type the phone's MAC address. :::caution Enter the MAC address exactly as printed on the phone. Auto provisioning ties each configuration file to one specific MAC address, so a single wrong character means the phone never receives its settings. ::: 4. In the **Options** section, set the provisioning behavior: ![Cloud Voice, provisioning options showing the template, provisioning link, and authentication settings](/images/pbx/yealink-option-cloud.png) - **Template**: Pick a template from the list. Use the default template that matches the phone model, or a custom template you have built. - **Provisioning Link**: This link is generated for you and points to where the phone's configuration file is stored. No action is needed. - **Authentication for the First-time Auto Provisioning**: When turned on, the user must enter credentials on the phone before the first provisioning run can proceed. :::tip Keep **Authentication for the First-time Auto Provisioning** enabled so an unauthorized device cannot claim the configuration. ::: 5. In the **Assign Extension** section, select the extension to bind to this phone. ![Assign extension drop-down for the new phone](/images/pbx/assign-an-extension-pnp.png) :::note If the extension you want is missing from the list, it is already tied to another phone. You can either release it from that device first, or enable concurrent registration on the extension so it can register to more than one endpoint. By default, an extension registers to a single SIP (Session Initiation Protocol) endpoint only. ::: 6. Click **Save**. The system posts an **RPS Request Success** event notification to confirm the request. RPS (Redirection and Provisioning Service) is the cloud service that, when the phone boots, points it to the location where its configuration file is stored. 7. Set a password for the phone's Admin account. :::note If automatic random password generation for phones is enabled, you can skip this step. ::: 1. Click the edit icon ![Edit icon](/images/pbx/wizard-previous.png) next to the phone. 2. In the **Preference** section, enter a password in the **Admin Phone Password** field. ![Cloud Voice, Preference section with the Admin Phone Password field](/images/pbx/set-admin-password.png) 3. Click **Save**. ## Step 2: Trigger provisioning on the phone 1. Reboot the Yealink phone. 2. If you left **Authentication for the First-time Auto Provisioning** enabled, the phone prompts for credentials. Enter them on the handset: ![Authentication prompt on the phone requesting a user name and password](/images/pbx/yealink-auth-login-pce.png) - **Username**: The extension number assigned to the phone. - **Password**: The extension's Voicemail Access PIN. :::note You can find the Voicemail Access PIN on the **Voicemail** tab of the extension's configuration page. ![Cloud Voice, Voicemail tab showing the extension's Voicemail Access PIN](/images/pbx/ext-vm-pin.png) ::: ## Result - The phone downloads its configuration from Cloud Voice and applies the settings on its own. - The extension registers on the phone. Confirm the registration state under **Auto Provisioning > Phones** in the portal. ![Phones list showing the Yealink device with a registered extension](/images/pbx/yealink-provisioned-pce.png)