Looking for something?

You will find your answers here!

Sorry, we didn't find any relevant articles for you.

Send us your question using the form below and we will get back to you with a solution.

Yealink

Troubleshooter: Yealink/Poly - Provisioning

Objective

Meant to serve as an end-to-end guide for provisioning Yealink and Poly phones.
 

User Context

  • Provisioning Flowchart for Polycom and Yealink
     

Procedure

Is it a device we support?

Yes

 

No

 
 

Is it on the recommended firmware?

NOTE: Skip if it's a new customer and the phone was purchased from us

 

Yes

 

No

 
 

For Implementations: 

  1. Ensure that all phones' MAC addresses are added to the Inventory. 
  2. Export list of phones and configure lines as necessary. 
  3. Assign custom configs if necessary.

For Support: 

  1. Add the Phone to the Domain's Inventory and configure it on Snapbuilder. 
  2. Hit Save and re-sync.

    NOTE: It would be a good idea to add notes to the phone, so we know who it points to on NDP

     

Next

 
 

Did it provision as expected?

Yes

 

No

 
 

End.

 

Confirm if the device is hitting the redirect

Yes

 

No

 
 

Is it a Yealink RPS or a Polycom?

Yealink RPS

 

Polycom

 
 

Is the device "Bound" on RPS and pointing to a server?

Yes

 

No

 
 

Reboot and/or factory reset.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (use this wui.http_enable="1" and FR) 

NOTE: wui.https_enable="1" to access GUI if it already hit NDP 2739

 

IF THE DEVICE REACHES NDP, double-check assigned lines for fat-fingering, then re-add/reassign the phone to the user. You will need to enable a global one-time password for a factory reset, then factory reset again.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide.

 
 
 
  1. Check the tickbox beside the MAC address
  2. Check if the IP Address is the same as what is displayed on RPS
  3. Factory reset.
    1. In the VIP Portal, go to Inventory
    2. Go to the Phone Hardware tab
    3. Click Allow Global Credentials (Key icon)
       

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (use this wui.http_enable="1" and FR) 

NOTE: wui.https_enable="1" to access GUI if it already hit NDP 2739

 

IF THE DEVICE REACHES NDP, double-check assigned lines for fat-fingering, then re-add/reassign the phone to the user. You will need to enable a global one-time password for a factory reset, then factory reset again.

Next

 
 

Did it work?

Yes

 

No

 
 

This content will be shown (depending on) when button above is clicked

 

Refer to the VOIPmon guide

 
 
 

Claim the device on the redirect, then reboot and factory reset.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (https.enabled="1" to access GUI if it already hit NDP. Admin/ 7627):

NOTE: If the device reaches NDP, double-check the assigned lines for fat-fingering by re-adding the phone to the user. 

 

Reboot afterwards

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide.

 
 
 

Troubleshoot the internet: 

  • Is the LAN Cable plugged to the LAN port, not the bridge port?
  • Does the phone have an IP address? 
  • Are there any loose wires? 
  • If not on a power adaptor, is the phone properly on a PoE setup?

Next

 
 

Check if the cabling is good

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to VOIPmon guide

 
 
 
 

Upgrade firmware accordingly.

Next

 
 

For Implementations: 

  1. Ensure that all phones' MAC addresses are added to the Inventory. 
  2. Export list of phones and configure lines as necessary. 
  3. Assign custom configs if necessary.

For Support: 

  1. Add the Phone to the Domain's Inventory and configure it on Snapbuilder. 
  2. Hit Save and re-sync.

    NOTE: It would be a good idea to add notes to the phone, so we know who it points to on NDP

     

Next

 
 

Did it provision as expected?

Yes

 

No

 
 

End.

 

Confirm if the device is hitting the redirect

Yes

 

No

 
 

Is it a Yealink RPS or a Polycom?

Yealink RPS

 

Polycom

 
 

Is the device "Bound" on RPS and pointing to a server?

Yes

 

No

 
 

Reboot and/or factory reset.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (use this wui.http_enable="1" and FR) 

NOTE: wui.https_enable="1" to access GUI if it already hit NDP 2739

 

IF THE DEVICE REACHES NDP, double-check assigned lines for fat-fingering, then re-add/reassign the phone to the user. You will need to enable a global one-time password for a factory reset, then factory reset again.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide.

 
 
 
  1. Check the tickbox beside the MAC address
  2. Check if the IP Address is the same as what is displayed on RPS
  3. Click Reset Connection, then factory reset.

    IMPORTANT: Make sure to enable the reset on NDP first.

     

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (use this wui.http_enable="1" and FR) 

NOTE: wui.https_enable="1" to access GUI if it already hit NDP 2739

 

IF THE DEVICE REACHES NDP, double-check assigned lines for fat-fingering, then re-add/reassign the phone to the user. You will need to enable a global one-time password for a factory reset, then factory reset again.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide

 
 
 

Claim the device on the redirect, then reboot and factory reset.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Access the phone's GUI and use the following credentials on the auto provisioning tab (https.enabled="1" to access GUI if it already hit NDP. Admin/ 7627):

NOTE: If the device reaches NDP, double-check the assigned lines for fat-fingering by re-adding the phone to the user. 

 

Reboot afterwards

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide.

 
 
 

Troubleshoot the internet connection 

  • Is the LAN Cable plugged to the LAN port, not the bridge port?
  • Does the phone have an IP address?
  • Are there any loose wires?
  • If not on a power adaptor, is the phone properly on a PoE setup?

Next

 
 

Check if the cabling is good

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer to the VOIPmon guide.

 
 
 
 
 
  1. Add a Phone as “Other” by navigating to Users > Phones > Add
    Phone
  2. Once the phone has been added, get the phone's SIP credentials and paste the credentials into the phone's registration tab.

Next

 
 

Did it work?

Yes

 

No

 
 

End.

 

Refer back to the manufacturer

 
 

 

Additional helpful links:

Escalation Information

Escalation Information: SD2

If you have any questions, concerns, or issues, contact the Service Desk II (SD2) team.

IMPORTANT: Before escalating to SD2, refer to this article.

 


 

Change Log

Date Description
Aug 28, 2026 Changed factory reset process from NDP to VIP Portal
Apr 29, 2026 Article created

 

Was this article helpful?