T46S Firmware 66.83.x.x

[Chris708]

I was looking for firmware updates and the range of firmware for the Yealink T46S 66.83.x.x is nowhere to be found.

Is there a problem with that firmware?

[complex1]

(05-05-2020 09:35 PM)Chris708 Wrote:  I was looking for firmware updates and the range of firmware for the Yealink T46S 66.83.x.x is nowhere to be found.

Is there a problem with that firmware?

Hi Chris,

As far as I know there where no problems with this firmware release.
But I also noticed that almost all .83 releases of the Yealink website have disappeared.
Why do you want to use a 2 year old firmware, why not upgrade to the latest .85 ones?

[Chris708]

(05-06-2020 10:32 AM)complex1 Wrote:  

(05-05-2020 09:35 PM)Chris708 Wrote:  I was looking for firmware updates and the range of firmware for the Yealink T46S 66.83.x.x is nowhere to be found.

Is there a problem with that firmware?

Hi Chris,

As far as I know there where no problems with this firmware release.
But I also noticed that almost all .83 releases of the Yealink website have disappeared.
Why do you want to use a 2 year old firmware, why not upgrade to the latest .85 ones?

I have seen some folks still using that firmware (no need to change apparently?) and wanted to to know how crucial it is to upgrade.

There is a reason it is no longer available from Yealink when even older versions are available so I will see about upgrading.

Thanks.

[Yisroel_MongoTEL]

I was coincidentally looking for an 83 firmware and also wondered about it.

I'm also not aware of any major issues with 83 (using it on many many phones.)

(I had an issue using the URL DSS key on 84 firmware, which is fixed in 85 but 85 has another major issue so I needed something else. In the end I found it somewhere on my server... and the URL key is working...)

[jolouis]

(05-06-2020 02:16 PM)MongoTEL_Support Wrote:  I was coincidentally looking for an 83 firmware and also wondered about it.

I'm also not aware of any major issues with 83 (using it on many many phones.)

Well other than that it's now two releases old and they probably just wanted to clear up their public facing servers, V83 was the notorious "OpenVPN randomly broken/doesnt work as it used to" firmware. V82 worked fine, and in my own testing V83 seemed to be OK but the OpenVPN client built in obviously had some configuration settings or features missing as others reported all kinds of problems. Just search the forums for VPN doesnt work and you'll see... somebody figured it out by V84 and magically those who had problems were happy enough again (at least about OpenVPN).

[Yisroel_MongoTEL]

(05-07-2020 03:29 PM)jolouis Wrote:  Well other than that it's now two releases old and they probably just wanted to clear up their public-facing servers, V83 was the notorious "OpenVPN randomly broken/doesn't work as it used to" firmware. V82 worked fine, and in my own testing V83 seemed to be OK but the OpenVPN client built-in obviously had some configuration settings or features missing as others reported all kinds of problems. Just search the forums for VPN doesn't work and you'll see... somebody figured it out by V84 and magically those who had problems were happy enough again (at least about OpenVPN).

The fact that it's two releases old isn't really relevant because they have on the site several versions before that as well and only this specific one is missing.

(As mentioned I'm using 83 now because on 84 I have an issue with the URL DSS key not working in some cases, and in 85 I have a bad issue with transferred calls getting lost.

[Chris708]

I believe V83 also was the first firmware to allow the WF40 USB wifi dongle to be used so there is value in that firmware.

None of my clients use the VPN so that is a non-issue for me.

I am doubtful that removing V83 from their public facing servers is part of a general clean up when they have much older firmware still listed.

Anyway, I too was able to find various versions of the V83 in our systems. It was just sometimes more convenient to download the firmware. I'll have to make my own repository I suppose.