Yealink T21P E2 No provisionning bebind SBC

[AWS2P]

Hi ,
i encountered a provisionning problem (have seen also a closed thread from @Lee Cramman having same problem) with just out of the box Yealink T21P E2, l manually updated FW to latest 52.84.0.35.

My fresh Pbxexpress install V16.2 PBX is running on Amazon Lightsail (middle instance)

phones are behind latest SBC on W10 PC.

phone was seen in bold in console but when I assign an extension nothing happens, no reboot , no provisionning.
After a factory reset and a new try, i've reached once to have provisionning working.

For now phone GUI is not accessible from 3CX console , no provisionning working, no restart

If you have some ideas

 

[AWS2P]

Phonebook is not available also. Date is OK, but time is not updated and start at 00h00

I've plugged a Snom 715, provisionning is directly working like a charm, reprovisioning works, restart too, phonebook too. date and time are OK

So Yealink FW is not working at all

 

[Saqqara]

Have you disable ‘certificate check on the phone’

Check limitations https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/

 

[AWS2P]

Hi Saqqara,
Have seen this limitation but 3CX doc is not applying to T21P E2 or am i wrong ?

Finally you were right on target Saqqara, even if it is not specified to do this for T21P E2 , disabling certificate do the Job. thanks

 

[AWS2P]

I'm becoming crazy with these phones, You need to bet before doing the steps on the phone trying to set it properly this is like it was complete hazard if it works or not.
I've done same settings on 2 new phones, one work other not, no matter what i do nothing change.

why the provisioning link in the extensions is the same for all phones T21P E2, I crack everything mixes, the console tells me that I have already assigned the phone to another extension. What a headache, phones as crappy it had been long since it had not happened to me, but tonight I'm fed up. Normally with Snoms I put a few minutes to use the phones, but this is a real calvary.

I've never passed so much time to finally doing near nothing because provisioning doesn't work.

 

[Lee Cramman]

I no longer have this problem any more and they re-provision without any issues at all (I still have to do this for T190P/T21P, but not T19P E2/T21P E2).

As you've probably gathered, this was caused by an SSL certification issue and the setting you have disabled works around the problem. However, if you want to address the cause I would check to make sure that your phones are using the FQDN of the server rather than IP address and make sure you are using 3CX for your SSL certs.

I wrote the thread when I was quite new to 3CX, I'm sure our original problem was probably me!

 

[FS_Mathieu]

@aws2p I also had problems with provisionning of Yealinks and none with Snom so I'm thinking Yealink's network/provisionning sucks

 

[AWS2P]

Thanks for answers

what I see is that it must actually uncheck the SSL transport and encryption on the side 3CX, it allows to have access to the centralized phonebook, and T21P E2 side must disable the control of certificates to have the provisioning operational.
Still, my phones are behind SBC, it is slow to react, a phone reboot take several minutes to start for example. With Snom it's instantaneous. I will not redeem this type of phones what misery ...

hope to have no others bad surprises

 

[FS_Mathieu]

Hope they'll improve it on next models

Here we use T42S/46S/48S it's a bit better but network is still slow, FW update is slow too

 

[AWS2P]

I no longer have this problem any more and they re-provision without any issues at all (I still have to do this for T190P/T21P, but not T19P E2/T21P E2).

Are you sure because i use only T21P E2 in latest FW and i'm obliged to do this otherwise nothing at all works . This is strange also the first provisioning after FW update is the only one time it's done quickly, after nothing happens when you do something in console, you have time to drink a beer.

 

[Lee Cramman]

Yes, 100%. I've just Factory reset one to make sure and it was fine. I'm on the same firmware version as you. On first reboot it showed up in the console. I assigned it, the phone (slowly) rebooted again and provisioned correctly.

I have noticed the Yealink's are slow to start up and can often hang at the "optaining IP address" prompt for a few minutes. Maybe just enough time to drink a small beer .

 

[AWS2P]

Are your phones in Stun or behind SBC like me ?

 

[Lee Cramman]

Behind an SBC using PNP just like you, but SBC is probably not relevant here as the phones provision over http(s) rather than the SBC (the SBC just handles the plug and play bit).