• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Update your Yealink Firmware Today

Status
Not open for further replies.
Spent 2 days to update the phones on all customer's Phone Systems - everything past smoothly, except two T48G phones (provisioning method - STUN). After performing the firmware update from the 3cx PBX they reboot but didn't update. The second manual reboot fixed issue. This customer has a very slow internet connection - probably that was an issue.
Except for these two phones, the update of around 120 yealink phones to ".55" version passed without any problems. If someone interested here is the approximate list: 15 of T48G, 10 of T46G, 60 of T4xS, 10 of T29G, 5 of T27 and 20 of T5xS models.
3CX thanks for this update! Hope the yealink guys will not miss this type of issues anymore.
Hi phonemaster,
Thanks for your reply.
Yes, the slow network can be the source of the problem.
In the future we (3CX and Yealink teams) are planning to double these timeouts to avoid this type of issues.
 
  • Like
Reactions: phonemaster
Hi phonemaster,
Thanks for your reply.
Yes, the slow network can be the source of the problem.
In the future we (3CX and Yealink teams) are planning to double these timeouts to avoid this type of issues.
Good news! Thanks!
 
I've just started on my systems, and seems the T46s (STUN) are the ones having the most trouble with this update. A few small systems did ok, but some do not. Can't seem to find rhyme or reason.

Worked on about 5 systems this morning before hours. There's always a few oddballs that won't update remotely for whatever reason, but the rhyme, in my case, this time, seems to be T46G's. T42G's seem fine and immediate. T46S I sent command through several times and most finally updated although a couple I thought weren't going to but then after sitting about 20 minutes later they did. I have not had the clients manually reboot the T46G phones to see if that helps.

One client has twelve T46G, ten T42G, one T46S at the same site/IP address. Only the T46G's are not updating.
 
Worked on about 5 systems this morning before hours. There's always a few oddballs that won't update remotely for whatever reason, but the rhyme, in my case, this time, seems to be T46G's. T42G's seem fine and immediate. T46S I sent command through several times and most finally updated although a couple I thought weren't going to but then after sitting about 20 minutes later they did. I have not had the clients manually reboot the T46G phones to see if that helps.

One client has twelve T46G, ten T42G, one T46S at the same site/IP address. Only the T46G's are not updating.
Hi bbaker73,
It's very strange because it works for me.
I just updated my T46G (provisioned remotely) from 28.83.0.20 to 28.83.0.55 without any problem
upload_2018-10-30_19-2-59.png
I even made the video of it (you can find it here).

Please check your settings again.
 
There is certainly in issue with the upgrade. I worked on several systems today. T46 and T29 will not upgrade. T23G will only upgrade 1 at a time. T27 and T5x series seem to upgrade without issues.

These systems are local, or hosted at both OVH and Google.

This seems to be a wide spread issue.
 
Multiple T46G, via stun and SBC impossible to update, wich options ? Don't wan't to update hem all one by one.
 
There is certainly in issue with the upgrade. I worked on several systems today. T46 and T29 will not upgrade. T23G will only upgrade 1 at a time. T27 and T5x series seem to upgrade without issues.

These systems are local, or hosted at both OVH and Google.

This seems to be a wide spread issue.
Hi neville,
As you can see from my video that I mentioned in my previous reply, I successfully updated the T46G phone from "xx.83.0.20" to "xx.83.0.55". Yes, it took more than 6 minutes, but it updates. So, please don't surely write that the "T46 and T29 will not upgrade". As you can see they will update.
We (3CX and Yealink teams) updated a lot of Yealink phones using different scenarios (single phone updates, multiple phone updates, local/remote phones and etc) and all these updates were successful.
At the same time, as we can see, all problems are coming from the T29G, T46G and T48G models, which are the slowest phones in the current generation of the Yealink phones. This is why in the future versions we will increase the timeouts, so even this slow phones will have enough time to download the firmware file, check it, apply and update.

Please try to use all suggestions from this discussion (upgrade the network, check OS limitations, manual reboot or upgrade) and update your phones to the "xx.83.0.55" which is fixing the update issues and contains some improvements.
 
Multiple T46G, via stun and SBC impossible to update, wich options ? Don't wan't to update hem all one by one.
Try to upgrade the network and increase the speed. This will allow the phones to download the firmware faster and they will have enough time to update.
 
I have updated our Yealink T21P E2 phones (about 60 units over several sites) on Direct SIP (STUN - remote). Some phones took a lot longer than others to do the upgrade (quickest 3 minutes, longest 10 minutes) and they seem to reboot about 3 times during the process.
 
I have updated our Yealink T21P E2 phones (about 60 units over several sites) on Direct SIP (STUN - remote). Some phones took a lot longer than others to do the upgrade (quickest 3 minutes, longest 10 minutes) and they seem to reboot about 3 times during the process.
Hi Sergio Fernandez,

The additional reboot can happen when the Yealink phone detects that the downloaded firmware file is corrupted. It reboots to cleanup the memory and downloading it again.
 
So we are seeing timeouts after 5 seconds based upon the yealink phone logs. The challenge is, we're on a pretty high-speed connection. 250Mbps fiber to the internet & our data center is on 100Mbps fiber. If this is timing out on that kind of connection, we're never going to be able to upgrade anyone.

here's the log from the phone side:

Code:
<134>Oct 31 13:02:49 GUI [1292:1292]: IDUI<6+info  > 369.204.732:CDlgScreenSavers::StartChanging, nUseSysPic = 1
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS change cipher, Client hello (1):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Unknown (67):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: Operation timed out after 5335 milliseconds with 0 out of 0 bytes received
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]Connect is short Cleanup curl.
<131>Oct 31 13:02:49 ATP [1327]: DURL<3+error > [DCMN]download common error, errcode:28.
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]download common error, remove file.
<131>Oct 31 13:02:49 ATP [1327]: ATP <3+error > https to file failed, code = -128, msg = , retry = 2
<134>Oct 31 13:02:49 ATP [1327]: ATP <6+info  > Wait 0 second to next file transfer!
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]download to file...
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]Use new short connect.
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]HTTP request use auth = 0.
<132>Oct 31 13:02:49 ATP [1327]: DURL<4+warnin> [DCMN]no set client cert or file is damaged or does not exist.
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]ssl cipher:AES:!ADH:!LOW:!EXPORT:!NULL
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]I will write to file: /tmp/xxx.cfg
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (IN), TLS handshake, Server hello (2):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
<134>Oct 31 13:02:49 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
<134>Oct 31 13:02:51 sua [1333]: DLG <6+info  > [000] cb_nict_kill_transaction (id=13264)
<134>Oct 31 13:02:51 sua [1333]: DLG <6+info  > [000] cb_nict_kill_transaction (id=13265)
<134>Oct 31 13:02:52 GUI [1292:1292]: IDUI<6+info  > 372.000.530:CDlgScreenSavers::OnReallyChangeBG
<134>Oct 31 13:02:52 GUI [1292:1292]: IDUI<6+info  > 372.001.245:ScreenSaverController::GetNextScreenSaverPicPath, nSSType = 1
<134>Oct 31 13:02:52 GUI [1292:1292]: IDUI<6+info  > 372.001.704:ScreenSaverController::GetUserPicByOrder nListSize = 1
<134>Oct 31 13:02:56 sua [1333]: DLG <6+info  > [255] SIP: 216.201.95.249:5060 Keep Alive sent on UDP!
<134>Oct 31 13:02:56 sua [1333]: FSM <6+info  > [000] free transaction ressource 13264 0_2391940525
<134>Oct 31 13:02:56 sua [1333]: FSM <6+info  > [255] free nict ressource
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS change cipher, Client hello (1):
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Unknown (67):
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]CURL Info: Operation timed out after 7826 milliseconds with 0 out of 0 bytes received
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]Connect is short Cleanup curl.
<131>Oct 31 13:02:57 ATP [1327]: DURL<3+error > [DCMN]download common error, errcode:28.
<134>Oct 31 13:02:57 ATP [1327]: DURL<6+info  > [DCMN]download common error, remove file.
<131>Oct 31 13:02:57 ATP [1327]: ATP <3+error > https to file failed, code = -128, msg = , retry = 3
<134>Oct 31 13:02:57 ATP [1327]: ATP <6+info  > Wait 0 second to next file transfer!
<132>Oct 31 13:02:57 ATP [1327]: ATP <4+warnin> Download mac.cfg fail
<133>Oct 31 13:02:57 ATP [1327]: ATP <5+notice> sync and protect switch not open!
<134>Oct 31 13:02:57 ATP [1327]: ATP <6+info  > send end provision!!
<134>Oct 31 13:02:57 ATP [1327]: ATP <6+info  > auto provision result is 5
<134>Oct 31 13:02:57 GUI [1292:1292]: DIR <6+info  > 377.226.781:Directory: message(0x30002), wparam(0x0), lparam(0x0)
<134>Oct 31 13:02:57 GUI [1292:1292]: ZERO<6+info  > 377.228.063:process autop msg[ATP_MSG_NOTIFY_AUTOP_END] wparam[0] lparam[0]
<134>Oct 31 13:02:57 ATP [1327]: ATP <6+info  > Update fail, and return
 
  • Like
Reactions: accentlogic
Hi neville,
As you can see from my video that I mentioned in my previous reply, I successfully updated the T46G phone from "xx.83.0.20" to "xx.83.0.55". Yes, it took more than 6 minutes, but it updates. So, please don't surely write that the "T46 and T29 will not upgrade". As you can see they will update.
We (3CX and Yealink teams) updated a lot of Yealink phones using different scenarios (single phone updates, multiple phone updates, local/remote phones and etc) and all these updates were successful.
At the same time, as we can see, all problems are coming from the T29G, T46G and T48G models, which are the slowest phones in the current generation of the Yealink phones. This is why in the future versions we will increase the timeouts, so even this slow phones will have enough time to download the firmware file, check it, apply and update.

Please try to use all suggestions from this discussion (upgrade the network, check OS limitations, manual reboot or upgrade) and update your phones to the "xx.83.0.55" which is fixing the update issues and contains some improvements.


I worked on the rest of my hosted systems this morning. All cloud hosted, all remote STUN phones. All I can tell you is, aside from a couple of T46S's, all T46S's, T42G's, T42S's update successfully. No T46G's will update on 7 different PBX's and remote networks. Tried repeatedly, one at a time, all together, issued reboots in between. I don't think 7 companies have network issues, especially when other models on these same networks update fine, networks haven't changed, T46G's have updated successfully before. Guess we're left with the time consuming process of manual update on all of these.
 
Sorry, but there is a bug in the update somewhere. All !! Yealink TxxG phones do not make the 0.55 firmware update. I manage more than 15 Cloud 3CX systems. All other devices T40P, T48S etc. without problems. The error occurs with both STUN and SBC systems.
 
I see the T46 patch file and the T42S patch files - they are different sizes - I would expect that. But it almost feels like the T46 patch isn't being sent to the phone & instead the full file is trying to be pushed. Since the update is pulled from the phone using UDP and not HTTPs - what's the best way to try and debug it. If I wireshark it, it's obviously encrypted becuase of the TLS certitficates.


This is the T42S files (we don't have any T46G on this customer system)
-rw-r--r-- 1 phonesystem phonesystem 253872 Oct 25 07:50 patchT4XS-66.83.0.55.rom
-rwxr--r-- 1 phonesystem phonesystem 26664256 Dec 4 2017 T4XS-66.82.0.20.rom



And this is the T46G files (we don't have any T4xS phones on this customer system any longer)
-rw-r--r-- 1 phonesystem phonesystem 253216 Oct 25 07:42 patchT46-28.83.0.55.rom
-rw------- 1 phonesystem phonesystem 23112864 May 13 2017 T46-28.80.0.130.rom
-rw------- 1 phonesystem phonesystem 23017744 May 13 2017 T46-28.81.0.25.rom
-rw------- 1 phonesystem phonesystem 23018672 May 13 2017 T46-28.81.0.60.rom
-rwxr--r-- 1 phonesystem phonesystem 23234624 Nov 3 2017 T46-28.82.0.20.rom
-rw-r--r-- 1 phonesystem phonesystem 23585792 Jun 18 08:09 T46-28.83.0.20.rom
-rw-r--r-- 1 phonesystem phonesystem 23624736 Oct 25 07:42 T46-28.83.0.55.rom
-rwxr--r-- 1 phonesystem phonesystem 23194736 Aug 2 2017 T46G-28.81.0.110.rom
-rw------- 1 phonesystem phonesystem 23058560 May 13 2017 T46G-28.81.0.61.rom
-rwxr--r-- 1 phonesystem phonesystem 26664256 Dec 21 2017 T4XS-66.82.0.20.rom
 
  • Like
Reactions: accentlogic
We have dozens of sites that cannot update T29G and T46G phones behind an SBC - Windows or Debian. Local PBX and they update fine. Any other Yealink model works fine, even when using an SBC.
 
Hi guys,
We are again wasting our time.
3cx already informed as that the "xx.83.0.20" version provided by yealink had the update issues. And, as I can see, it was 100% yealink issue (red card to them :mad:).
Anyway, 3cx and yealink guys tried to fix it for us. They prepared a patches that works for 99% of exited installations. Aram, from 3cx, even prepared a video where he updated the T46G provisioned behind the SBC, so we can see that it works.
Yes, we already know that in some specific networks (you can have a fast internet, but Firewall can add some delays) the update for the slow phones like T29G, T46G and 48G can fail, but we were already informed that they are problematic and slow. For example, the T46G is two times slower than T46S. Probably, this is why they are discontinued from yealink side. Why I think that they are "discontinued"? Because, on the yealink website, I can see the new V84 (xx.84.0.10) for the all models except the T29G, T41P, T42G, T46G and T48G. Probably it's delayed or these models are discontinued. I'm not sure.

So, let's appreciate our time and, instead of typing the long comments here, update our problematic models manually. In any cases we need to do this - we already have this problematic firmware installed on our phones and yealink or 3cx guys can't come to our offices and update them for us. We need to do this our self, so let's do it once and forget about this issue.
I already did this for one customer and planning to keep doing it for all customers who will have update problems. I advise you to do the same.

Thanks to all.
 
  • Like
Reactions: Nick Galea and Aram
Hi phonemaster,

Thanks for understanding!
Just to inform you about the T29G, T41P, T42G, T46G and T48G models.
They are not discontinued yet. The Yealink guys informed us that they are planing to skip the V84 for these models, but they are planning to prepare the V85 for them. They don't have final decision yet.
As soon as we will get an updates from the Yealink team, we will make the appropriate updates on our side and our customers will be informed about them.
 
@phonemaster - I get all that, except for the client isn't going to pay for the labor to do the manual updates, there's no machine that can be used to do the updates (since they are remote) and suddenly I have to engage the local IT consultant to help out (and pay them out of my pocket to help) for remote customers who are hundreds of miles away. It quickly becomes unprofitable for an extended period. Especially when we are trying to do ~100 sites with about 10K phones. So spending 1-2 hour or so trying to figure out a fix is immensely cheaper and more profitable then spending 100+ hours updating phones manually.
 
  • Like
Reactions: accentlogic
@phonemaster - I get all that, except for the client isn't going to pay for the labor to do the manual updates, there's no machine that can be used to do the updates (since they are remote) and suddenly I have to engage the local IT consultant to help out (and pay them out of my pocket to help) for remote customers who are hundreds of miles away. It quickly becomes unprofitable for an extended period. Especially when we are trying to do ~100 sites with about 10K phones. So spending 1-2 hour or so trying to figure out a fix is immensely cheaper and more profitable then spending 100+ hours updating phones manually.
I'm 100% agree with you. I wroth that post for the guys who are continuously typing the same info/issue and not trying to find the ways to fix it.
Even more, if you have 10K of the slow/problematic phones and can't update them using 3cx solution, I can suggest to you to contact to yealink directly and ask them for the compensation. This issue is their fault and they have to pay for it!
We like the yealink phones (price+quality+appearance), but this type of issues are not acceptable. Hope yealink will not do the same mistake again.

From my side, I can just provide our statistic of updating the yealink phones:
During the last 3 days we updated around 1100 yealink phones. Only one customer (with slow network) had the update problems and we manually updated his 12 yealink phones (3 of T48G and 9 of T46G).
 
Maybe related, maybe not. I have T46S and T42G on the new .55 FW.

I wanted to test something on a different downloaded Yealink FW version on the 46S.
Update from the web UI fails.
Reset to defaults, same thing.
Tried a 2 or 3 FW versions from Yealink site. Updated failed.
Tried another PC browser, moved phone to another network. Update failed.

Tried on a second T46S that is on .55. Tried to upgrade to newest Yealink website FW 66.84.0.10. Update failed.

Then I decided to try a T42G that's on the new .55 FW. Tried to downgrade it to Yealink FW 29.83.0.50 and 29.83.0.30. Update failed.

Has anyone else tried to manually change the FW version once the phone is on this new .55 version as I don't seem to be successful.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,618
Messages
748,846
Members
144,729
Latest member
yparker0320
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.