T48G EOL due to missing TLS 1.2

[Kieron_Voip]

I already answered this in another post. No Yealink W52 and T41P are not included and will not be. You can configure them manually. If someone wants to go to another PBX for that, then its up to them. We will not jeopardise our entire user base for a few customers that dont understand.

Hi Nick,

Thank you, we fully understand, i just wanted to ask, if i didn't ask, customers would give push back to us and would demand explainations and evidence !

We do appriacte you spending the time to help us all get these devices updated !

Hope you have a good weekend.

 

[N_G]

@Kieron_Voip - Thanks for your understanding, no problem at all. The DECT handsets can easily be used with manual settings, there is not much need to provision them they dont have BLF buttons. Have a good weekend too.

@luminite - I think the T42G works with this firmware? I am not sure what determines it but i think its very much based on the chipset they have inside them and i guess engineer availability for that chipset. I did ask why there are so many phone models recently and i was told its because of supply issues they have - They have to use different chipsets sometimes because nothing else is available. Even though phone model looks identical to previous phone they are different inside. Different chipset, different firmware....

 

[CentrexJ]

I factory reset 1x T29G, T46G and T48G and put on the new firmware. Then after a slight modification to the T4X EOL template, the phones showed up in 3CX management console under "Phones" tab and I was able to provision them to work with our 3CX system via our local SBC on the first try. Looking forward to them being fully supported through 3CX in v18 SP6 again.

This takes care of 95%+ of my legacy Yealink phones in the field and the most important ones as they have 27+ BLF key options.

While I do have some of the other older models in the field (T41P, T42G, W52, W56), those phones due to less BLF keys (or none for DECT) really don't change often and we can manage them manually as needed until they are retired. Thank you for your persistence to get Yealink to produce the updated firmware that they did.

 

[spaxxilein]

We also updated the fireware with our preconfigured devices. Everything back to normal - except 3CX shows unsupported firmware. But everything is working and i guess the error message will be fixed in the next release.

Thanks Nick!

 

[yesss-de]

Just to make sure I got this right, through this Firmware Update T46G and T48G models will continue to work fully with 3cx v15 Update 5 but will show unsupported version until update 6 rolls out?
Will we have to fiddle with the templates or will this just work as it did before in Update 6?

 

[spaxxilein]

Just to make sure I got this right, through this Firmware Update T46G and T48G models will continue to work fully with 3cx v15 Update 5 but will show unsupported version until update 6 rolls out?
Will we have to fiddle with the templates or will this just work as it did before in Update 6?

For us it works same as before. Only warning in 3CX admin console for incompatbile firmware warning. Everything else works for us.

 

[Remip67]

Hi all,

One of our customers uses hotdesking. After a manual update of the phone firmware the phones worked fine, and only showed the incompatible firmware warning. But next day, after login in and out of the hotdesking user, the phones went back to the old firmware version and stopped working. Is this expected behaviour? Do we have to wait for update 6 for hotdesking to work properly again?
Thanks in advance,

Remi

 

[spaxxilein]

Hi all,

One of our customers uses hotdesking. After a manual update of the phone firmware the phones worked fine, and only showed the incompatible firmware warning. But next day, after login in and out of the hotdesking user, the phones went back to the old firmware version and stopped working. Is this expected behaviour? Do we have to wait for update 6 for hotdesking to work properly again?
Thanks in advance,

Remi

Hello Remi,

phones that are automatically updating to "correct" but non working firmware revisions seems strange. We dont use hotdesking but it sounds strange that you say they switched firmware version automatically. Did you check if somebody triggered a firmware update for the phones in question in 3CX admin console!? Maybe somebody thought they are helpful but infact reverted to "stock" 3cx compatible firmware.

Regards,

spaxxilein