Yealink "no service" with new 3CX ver!

[wizards]

Just spent ages trying to work out what I'd got wrong on a new 3CX setup... only to realise it wasn't me.

Brand new Yealink T42s obtain their setup, fetch it, and register, get their BLFs, etc., but say NO SERVICE.

Until you upgrade the Yealink firmware.


Any idea what causes this? Good job I had not upgraded customers to the new version yet as it would've left many of them in limbo until I upgraded all the phones. And yuo can't tell from the console - it says the extension is logged in!!

3CX ver - 16.0.910 (Debian - google Cloud hosted) (STUN connecting the phones - not tried with local or SBC connections)
T42s - 66.84.0.35 (this the version that works - what's currently shipping from the factory - 66.84.0.15 - does NOT)

 

[JohnS_3CX]

Hello @wizards

As per our guide you will have to upgrade your firmware first
https://www.3cx.com/sip-phones/yealink-t4-series/

You will need the minimum version 66.84.0.35 we have on our firmware page linked in the above article.

 

[cooper.simpson]

@JohnS_3CX Hi, I am having this same problem.
We are on latest, the phones where all 66.84.0.35.

I have factory reset them, manually updated to the latest available .95 firmware on 3cx website and still no service. This is very problematic and is causing my company an outage. Please treat this as an URGENT bug. This started by itself on Friday for us, I never said to update anything. Please may you help us get this fixed?

I have factory reset, manually updated firmware to .35 and or .95 tried to reprovision, they get all the provision information (account etc) to the phone, but they hang on registering. Oh, and worst part, its not all our phones. All the phones were on the same previously latest .35 firmware version, but only SOME stopped working and are having this bug.

 

[AWS2P]

Are unregistred phones coming back to bad time and date?
All same Model ?
Certificates problem ?

 

[JohnS_3CX]

Hi @cooper.simpson

The templates and firmware work together so if you have older firmware it might not play well with the PBX. Your case is a bit different than wizards's who only solved it after installing the correct firmware (this step is required - if this step is skipped we cannot guarantee compatibility).

I suggest to start a new thread and describe your setup as per https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/