T21p_e2 Firmware
Percival Blanco
Juesor we actually use T46, T48 and T42 phones for our installs with a number our clients and a few use the VPN. We use PBXact systems but there shouldnt be a difference as long as your using the commerical EPM.
Sorry I never got back to you on that question from the other week. No we dont have that issue. I also relayed info in an odd way. What I meant about needing the phone on the network is only for initially setting it up. After it downloads the files through endpoint manager then you can take the phone off network and it works great
We have done with no special modifications or changes to EPM or VPN. This worked with T46 and T48 phones running firmware 80 or 81. I have not tried with other models yet. We only use those when selling phone systems for the most part.
Just want to give everyone a solution that I have been dealing with almost 3 weeks. As usual, I had to get this resolved by myself. Zoom support was unwilling to help me because I did not purchase or lease the Yealink phone directly from them - even though on Yealink support article states otherwise.
You will need the correct recovery files to resolved this issue. I was given the first set files that did not work, but I had another support assistance sent me the correct files. Apparently, there are more than several different recovery files located on the internet, all of them failed for me. I received error messages "Failed -1" or "Network Failed 3,2,1". Luckily, I was able to received the correct files. Please see attachment (screenshot) of the files I used to recover my Yealink phone. Please pay close attention to the sizes of the files.
We know it can be frustrating when we are unable to assist during times when we are not the phone providers, and for that, we are truly sorry. However, we are happy to see that your account executive here at Zoom was able to connect you with your phone provider. It appears that they were able to provide assistance for the correct files to help get this issue resolved.
And the cause for this error was due to a firmware corruption on the phone. The Auto Provision URL: on the phone provides firmware updates to my Yealink Phones - that is being administered by Zoom network.
I also would like to add that this can be a security concern. I was told by a Zoom support representative, sometime back, that Zoom's Auto Provision handles the firmware updates. Those firmware updates are being supplied first by Yealink and then checked by Zoom developers for any security issues before allowing Yealink phones to be download from Zoom's provisioning URL:
If I'm contacting Yealink support directly to receive files from them without having Zoom developers to do their security check - that is a potential security risk for my company. Zoom should be protecting its customers from this type of lack of security.
Thanks for the great tips! I've got the correct recovery files from Yealink Support and I've named them accordingly and ensured that they are the correct size. However I'm still getting an error message (Update Failed (-1))
Note: A hash value is a unique value that corresponds to the content of the file. Rather than identifying the contents of a file by its file name, extension, or other designation, a hash assigns a unique value to the contents of a file. If someone modifies the file, the unique value will change.
While Zoom definitely should've provided a full set of steps to be good support agents, this is entirely on you, dictionary bullshittery aside. If you bought it form zoom, they'd do the legwork for you, but nickel and dime shaving means your expecting support for something that could be locked to some ebay/amazon provider, could be already security breached, but would definitely see no risk from a reputable manufacturer like Yealink m8.
SIP Gateway lets your organization use any compatible SIP device with Microsoft Teams to preserve your investments in SIP devices. Now you can sign-in to Teams with your corporate credentials and make and receive calls with a compatible SIP device. Compatible devices can be Skype for Business IP phones with standard SIP firmware, Cisco IP phones with multiplatform SIP firmware, or SIP devices from vendors such as Poly, Yealink, and AudioCodes. To find out how to configure your SIP devices for SIP Gateway, see Configure SIP Gateway.
For some devices, the minimum firmware version is greater than the approved firmware version. This is because the 3.X version is the Skype for Business version. We update the SIP version which is 2.X.
For support queries, customers using the Algo Solutions' SIP enabled endpoints listed with Teams SIP Gateway should reach out directly to Algo Solutions.General Information on Algo integration with TeamsConfiguration GuideTroubleshooting Guide
Emergency Calling - Emergency calling is supported from the Tango Extend eSIM and this uses the Teams number. Teams isn't notified of emergency calls made from the eSIM but will receive returned calls towards the Teams number.
Tango Extend Supported Features - Sign-in/out using Tango Extend Teams App with Teams policy sync, Make/receive calls with hold/resume and DTMF, dial-in to meeting, request to join, voicemail and MWI, Teams DND and Call Forwarding.
Note: Do not unplug the network and power cables during the IP phone firmware upgrading process. Also do not close/refresh the browser when the IP phone is upgrading firmware via web user interface.
IP phones support the use of FTP, TFTP, HTTP, and HTTPS protocols to download configuration files and firmware from provisioning server, and then upgrade firmware automatically. You can configure the way your IP phones download firmware stored on provisioning server in one of two ways:
You can upgrade your base station to the latest firmware version. The latest firmware version not only improves the performance of the base station, but also provides more features compared to the previous version. This section provides you with instruction on upgrading the base station via web user interface (Refer to Yealink W52P IP DECT Phones Auto Provisioning Guide for information on upgrading via auto provisioning).
Once the base station firmware has been successfully upgraded, the base station reboots automatically. The handset will perform an auto registration to the base station. You can check the firmware version of the base station using the handset. For more information, refer to Yealink_W52P_User_Guide_V40_1
You can upgrade W52x handset firmware via a USB tool or over the air (OTA). Upgrading handset firmware via the USB tool (developed by Yealink), you need to purchase a USB cable in advance, and then upgrade the handset firmware one by one.
Upgrading handset firmware via OTA means that the handset firmware can be upgraded through a wireless DECT connection (L2CAP). So a USB cable does not have to be plugged to the handset for firmware upgrade. OTA enables the distribution of new firmware to the subscribed handsets.
NOTE: Before upgrading the firmware, refer to Preferred Phones to identify the most current firmware version. Use the most current firmware to guarantee all features function properly.
Overview: Also known as a Recovery Mode Update, the TFTP process can be used to save what can be seen as an otherwise dead phone. This process is most useful in the scenario that a phone either gets stuck in a boot loop, or stays on a Welcome Initializing...Please Wait screen. However, it can also be useful on a device where a factory reset does not seem to be resetting the device correctly. If you find that your device fits into any of these categories, the TFTP recovery can be performed; it will reflash the firmware on the device in the case of a corrupt firmware and if successful, will allow your device to fully boot again.
You will be able to find the necessary recovery files for your device at the following URL Yealink Support. You will need to provide the proper .rom file renamed. So for example, if your device is a T46U you would rename your rom file to T46U.rom. All rom files can be obtained from the yealink website.
From here, you can navigate to the folder for the device that you will be trying to recover, inside of that folder you will find all of the files necessary to perform the TFTP recovery on that device. Download these files and place them in a folder that you will have easy access to. Make sure that you have downloaded all the files in your devices folder, the process will not be successful if you have not acquired all of the files necessary for your device.
On this screen, you are going to want to set the TFTP filesystem root to the folder that you downloaded the files from above in, in this examples case, they are located in a TFTP folder that is on my desktop. You will also want to ensure that you change the read request behavior to give all files and the write request behavior to take all files, so that way the TFTP program will know to allow the phone to request all of the files it is looking for in that folder. Once this is done you can click OK to save your changes and you are ready to move on to the next step.
Product Compatibility Matrices--For additional compatibility information for specific product components, click any of the Compatibility Matrix or Interoperability DB links to view a Matrix that is specific to that component.
After an initial Cisco Collaboration Systems Release, some product versions may be updated. For details about any post-release changes to product versions, see the Documentation Changes section of the Collaboration System Release Notes.
1Early Deployment (ED): Software releases that provide new features and new platform support in addition to bug fixes.
Maintenance Deployment (MD): Software releases that provide bug fix support and ongoing software maintenance.
2Phone models that are End of Software Maintenance will continue to be supported on the latest Unified Communications Manager releases. However, they will not take advantage of any new Unified Communications Manager or firmware features associated with that release. For more information on End-of-Sale phone models, reference the model's End-of-Sale announcement for information on level of firmware and hardware support.