Provisioning Yealink T32G on cloud

[alex0317]

I'm trying to provision a T32G on the cloud with no luck. I've provisioned a T46S with RPS without any issue but the T32G is giving me problems. Does it just not support it on the cloud? I have got it to work on my onsite installation of 3cx by manually provisioning it, but not on the cloud.

 

[CentrexJ]

This phone doesn't support modern SSL certificates.

From the 3CX Guide manual:
https://www.3cx.com/sip-phones/yealink-t32g-t38g-t42g-t46g/ "Incompatible with secure "SSL Transport and Ciphers" setting"

Here is what you have to do:
Login to phone's web management page—go to Security—Trusted Certificates—disable “Only Accept Trusted Certificates”—save the changes

From then it should provision normally. Good luck.

 

[JohnS_3CX]

On top of what @CentrexJ correctly pointed out, you also have to go to your 3CX management console under

Security >> Antihacking >> SSL/SecureSIP Transport and Ciphers

and disable this feature to allow the PBX to accept less secure TLS 1.0 connections because the phone might not be able to establish a TLS 1.2 connection and provisioning will fail.

Please note that this is a very old model, which has reached EOL since 2015 so you might want to consider something a bit more recent like the new T31x series
https://www.yealink.com/products_72.html

 

[alex0317]

On top of what @CentrexJ correctly pointed out, you also have to go to your 3CX management console under

Security >> Antihacking >> SSL/SecureSIP Transport and Ciphers

and disable this feature to allow the PBX to accept less secure TLS 1.0 connections because the phone might not be able to establish a TLS 1.2 connection and provisioning will fail.

Please note that this is a very old model, which has reached EOL since 2015 so you might want to consider something a bit more recent like the new T31x series
https://www.yealink.com/products_72.html

Yeah I know its EOL, but I didn't wanna scratch the whole idea of moving to the cloud because a couple of the phones are old. So, are these EOL life phones not compatible with RPS or do they have to be manually configured?

 

[Saqqara]

Look at limitations for these phones, no rps support https://www.3cx.com/sip-phones/yealink-t32g-t38g-t42g-t46g/

You have to setup the phone within 3cx first as stun configuration, then add the provisioning url into the phone via the phone web gui

As you have multiply stun phones at the same location, you need to configure then the 3cx supported way

 

[alex0317]

Look at limitations for these phones, no rps support https://www.3cx.com/sip-phones/yealink-t32g-t38g-t42g-t46g/

You have to setup the phone within 3cx first as stun configuration, then add the provisioning url into the phone via the phone web gui

Thanks, looks like I got it to provision and call properly.

 

[JohnS_3CX]

Yeah I know its EOL, but I didn't wanna scratch the whole idea of moving to the cloud because a couple of the phones are old. So, are these EOL life phones not compatible with RPS or do they have to be manually configured?

Plain and simple, it can only do TLS v1.0 connections which are considered vulnerable and no longer secure.

The setting I mentioned above tells your PBX to allow TLS v1.0, but at the cost of leaving you vulnerable.

Is this worth reducing security for a couple of old phones the manufacturer EOL'd years ago?

You should re-enable the option now that they have become provisioned, I think they will continue to function normally, albeit without being able to reprovision or update their phonebook.