- Joined
- Mar 21, 2022
- Messages
- 5
- Reaction score
- 2
I have two businesses (my own at home and one at an office I manage) that both have Yealink T54W. My customer gave me a spare one of his so I can do testing at home on my own before rolling updates and such to his. When I'm going to do something, I do it on mine (which I have at home) and make sure everything runs smoothly before I do the business side.
For my home network, my 3CX Pi wants to update the firmware from 96.84.0.35 to 96.86.0.72. It does offer a firmware for BENELUX customers but as I don't have BENELUX it clearly doesn't apply.
I tell it to update, and on the phone it says its upgrading, then stops at 82%. I've power cycled the phone a few times and retried, and always stops at 82%. I've left it like that overnight and still nothing.
The phone is on the same subnet as the 3CX Pi, and I can confirm that the Pi is fully updated.
However now the behavior has changed. Now, the phone boots up, all is fine for about a minute, then it starts trying to upgrade again. Thankfully, as this phone is "for looks", its not a big deal for it to have a problem.
But I'm now really suspicious because I've always had issues with updating phones. Sometimes they finish, sometimes they don't, etc. Last time I did a bunch of phone upgrades (March 2022) it did not go well and 50% of the phones required a factory reset (and some required multiple factory resets and resetups and eventually took the firmware). The firmware upgrades just seem very inconsistent to actually succeed.
As I'm the networking person AND the phone person, regardless of whether it's a problem with the PBX or a problem with the network, it's on me to fix it.
How can I troubleshoot this issue in more detail? Normally I'd try to do a tcpdump (which I may do on the Pi) and see what is going on, but to be honest, I'm not sure what ports should be used, etc so I don't think I'd even be able to identify when things go badly except "hey, phone stopped responding". But that's not diagnostically valid unless I know that the phone should have said something back to the 3CX.
As my customer's phones are scattered across the world, firmware updates failing at 50% (or more) is a real problem.
Any advice? From an hour or two of reading online, people say "factory reset and resetup the phones" a lot. That's really not a great solution as these phones are all over the place, and the people using them are not IT people. I need to surgically determine what the failure is, and correct it.
For my home network, my 3CX Pi wants to update the firmware from 96.84.0.35 to 96.86.0.72. It does offer a firmware for BENELUX customers but as I don't have BENELUX it clearly doesn't apply.
I tell it to update, and on the phone it says its upgrading, then stops at 82%. I've power cycled the phone a few times and retried, and always stops at 82%. I've left it like that overnight and still nothing.
The phone is on the same subnet as the 3CX Pi, and I can confirm that the Pi is fully updated.
However now the behavior has changed. Now, the phone boots up, all is fine for about a minute, then it starts trying to upgrade again. Thankfully, as this phone is "for looks", its not a big deal for it to have a problem.
But I'm now really suspicious because I've always had issues with updating phones. Sometimes they finish, sometimes they don't, etc. Last time I did a bunch of phone upgrades (March 2022) it did not go well and 50% of the phones required a factory reset (and some required multiple factory resets and resetups and eventually took the firmware). The firmware upgrades just seem very inconsistent to actually succeed.
As I'm the networking person AND the phone person, regardless of whether it's a problem with the PBX or a problem with the network, it's on me to fix it.
How can I troubleshoot this issue in more detail? Normally I'd try to do a tcpdump (which I may do on the Pi) and see what is going on, but to be honest, I'm not sure what ports should be used, etc so I don't think I'd even be able to identify when things go badly except "hey, phone stopped responding". But that's not diagnostically valid unless I know that the phone should have said something back to the 3CX.
As my customer's phones are scattered across the world, firmware updates failing at 50% (or more) is a real problem.
Any advice? From an hour or two of reading online, people say "factory reset and resetup the phones" a lot. That's really not a great solution as these phones are all over the place, and the people using them are not IT people. I need to surgically determine what the failure is, and correct it.