Yealink Firmware Management

Yealink firmware can be managed on our platform by utilizing Device and Domain overrides in NDP or advanced configuration overrides in the PBX Portal.

Considerations

Important: Some firmware versions will not work properly with the Yealink Sidecar. You may use the following overrides to resolve this issue. 

firmware.url="http://sipcfg.io/frm/yealink/v86fix"
firmware.url.server_type="http"

Optional Override (Removes "red triangle" default password warning that may appear after firmware upgrade completes. The override below sets the "user" password on the phone):

security.user_password="user:random_pass_here"

1. We do NOT recommend upgrading firmware unless you are addressing a security concern, resolving a bug, or have a specific need for a newer feature.
2. Some firmware upgrades may require a factory reset.
3. While device manufacturers put some protections in place, A firmware upgrade can cause a phone to become unstable, especially if connectivity or power is lost during an upgrade.
4. There may be cases where downgrading firmware can harm or 'brick' a phone.
5. Yealink firmware can be found on Yealink's own website, and it's possible to host their firmware on your own web/file server if you want an alternate firmware.
6. It's possible to use YMCS to manage firmware. For more info see our article How to Sign up for YMCS.
7. We recommend deploying new firmware to a small subset of devices first before deploying to all devices. 
8. Some firmware overrides are added and removed with each firmware revision. You will need to reference the relevant Yealink guide for a full list of overrides. 

Information about Firmware

The following table represents which major firmware revisions we have available for each phone model. Please see the bottom of the page for specific firmware versions.

* Cannot be downgraded after the upgrade.

Support for Firmware

SkySwitch will support all of our hosted firmware, and provide best-effort support for other firmware acquired directly from Yealink. We do not support custom firmware for Yealink phones.

Upgrading Firmware

This section details how to upgrade Yealink Firmware with Device overrides and Domain overrides using SkySwitch hosted firmware. A complete list of firmware can be found at the bottom of this article.

Upgrading firmware with device overrides using SkySwitch hosted firmware

Note: Please be sure to verify your phone model has a hosted firmware version with the override you are using. If a phone doesn't have firmware in the folder, it will not upgrade.

1. Open the NDP portal by clicking on the NDP option under the PBX dropdown menu and click on the appropriate override column.
   Note: You can also manage overrides in the PBX Portal > Device Inventory > Hardware > Edit Phone > Advanced (or inside of Button Builder)
   
2. Apply one of the following sets of overrides using the firmware table found above to reference which firmware is available per phone. Once complete, click the 'Save' button.

   1. firmware.url="http://sipcfg.io/frm/yealink/v83"
      firmware.url.server_type="http"

   2. firmware.url="http://sipcfg.io/frm/yealink/v84"
      firmware.url.server_type="http"

   3. firmware.url="http://sipcfg.io/frm/yealink/v85"
      firmware.url.server_type="http"

   4. firmware.url="http://sipcfg.io/frm/yealink/v86"
      firmware.url.server_type="http"

   5. firmware.url="http://sipcfg.io/frm/yealink/v87"
      firmware.url.server_type="http"

Loading the v87 firmware will restrict you from downgrading to a previous version.

Upgrading firmware with domain overrides using SkySwitch hosted firmware

1. Open the NDP portal by clicking on the NDP option under the PBX dropdown menu and then go to Configuration > Defaults > Domain Specific
   
2. Apply one of the following sets of overrides using the firmware table found above, to reference which firmware is available per phone. Only one set can be used as a domain override at a time.

   1. firmware.url="http://sipcfg.io/frm/yealink/v83"
      firmware.url.server_type="http"

   2. firmware.url="http://sipcfg.io/frm/yealink/v84"
      firmware.url.server_type="http"

   3. firmware.url="http://sipcfg.io/frm/yealink/v85"
      firmware.url.server_type="http"

   4. firmware.url="http://sipcfg.io/frm/yealink/v86"
      firmware.url.server_type="http"

   5. firmware.url="http://sipcfg.io/frm/yealink/v87"
      firmware.url.server_type="http"

Loading the v87 firmware will restrict you from downgrading to a previous version.

Firmware List

Below is the list of supported Yealink devices with their associated firmware files (.rom). The .rom files for each model can be located on the Yealink website, or use an override to push the firmware update.

T19P_E2 - 53.84.0.125.rom

T21P_E2 - 52.84.0.125.rom

T23 - 44.84.0.140.rom

T27G - 69.84.0.125.rom
T27G - 69.85.0.5.rom
T27G - 69.86.0.15.rom

T29 - 46.83.0.120.rom

T31(T30,T30P,T31G,T31P,T33P,T33G) - 124.85.0.40.rom
T31(T30,T30P,T31G,T31P,T33P,T33G) - 124.86.0.20.rom  

T46U(T43U,T46U,T41U,T48U,T42U) - 108.86.0.20.rom

T41P - 36.83.0.120.rom

T42G - 29.83.0.120.rom

T46G - 28.83.0.120.rom

T46S(T48S,T42S,T41S) - 66.84.0.125.rom
T46S(T48S,T42S,T41S) - 66.85.0.5.rom
T46S(T48S,T42S,T41S) - 66.86.0.15.rom

T48G - 35.83.0.120.rom            

T53W(T53) - 95.84.0.125.rom

T54W(T57W,T53W,T53) - 96.86.0.18.rom
T54W(T57W,T53W,T53) - 96.87.0.15.rom

T58 - 58.84.0.25.rom
T58 - 58.85.0.5.rom
T58V(T56A) - 58.86.0.20.rom

VP59_9.0 - 91.85.0.50.rom

W53H - 88.83.0.90.rom

W56H - 61.83.0.90.rom
W56H - 61.85.0.20.rom

W59R - 115.85.0.20.rom

W60B - 77.83.0.85.rom
W60B - 77.85.0.25.rom

W70B - 146.85.0.40.rom

Known Issues

Nonresponsive USB Port with Sidecar on T5x series phone

This issue is confirmed to be resolved by updating the phone to firmware T5x-96.86.254.850.rom.

Please be sure to apply the following override to ensure the fix is implemented properly.

firmware.url="http://sipcfg.io/frm/yealink/v86/9686254850"
firmware.url.server_type="http"

Additionally, if you receive an error message that "User" is using the default password, you may change the password via the following override:

static.security.user_password="user:xxxx"