yealink t22 provisioning to cloud pbx

[sbv3000]

Hi All
I'm setting up a clould 3cx for a client test, used the PBX express and AWS, all working ok with android app devices registering and working ok, setup via the extn qr code and on client lan, so I think the various firewalls each end and dns are ok.

However, struggling to get the t22 legacy phone on the same lan to register.
pbx is 15.5.15502.6 yealink firmware 7.73.0.50.

I've followed the rps provisioning guides on 3cx site, the server event shows the provisioning is ready, t22 factory reset, my url pasted from 3cx into the provisioning section etc, made tweaks such as disable 'disallow extn outside of lan'.
The phone boots, sends provision request but no joy.
I've also tried to manually add registration details to a phone account via the phone interface, but also no joy.

Does anyone have any ideas or have successfully registered t22 to a cloud pbx? How?

thanks in advance

 

[YiannisH_3CX]

Hello @sbv3000

Please upgrade your phone to firmware 7.73.0.60 and see if that works for you. You might be facing a certificate issue and you need the latest supported firmware to bypass that.
https://www.3cx.com/support/phone-firmwares/

 

[sbv3000]

Hi Yiannis
Thanks for that advice and the f/w link. I've updated that, reset the phone and tried again, still no success.
I'll look at running some network diagnostics to see what the phone is doing, meantime if you have any other ideas let me know

 

[ppickens]

SBV,

We too have nothing but trouble with the T22Ps. They seem to have major issues trying to pull config files on the latest version with the latest firmware. Try generating the config file in your browser by going to the provisioning url and adding in the MAC address and .cfg. This should allow you to pull the config file and you can then upload it to the phone manually in the settings->configuration menu of the web UI.

URL example:

https://texturl.3cx.us/provisioning/(randomized provisioning folder)/001122334455.cfg

 

[sbv3000]

hi PPickens
thanks for that suggestion
been running some network traces on the server and i have spotted that when the phone attempts to communicate it seems to be using tlsv1 which is fatally failing. other clients (android) seem to use v1.2. cant see anywhere in the yealink interface to choose the security protocol

 

[cobaltit]

You need to disable the PCI compliance setting in 3CX:

 

[sbv3000]

Hi PPickens
Tried your suggestion, worked first time, big thank you

@cobaltit - thanks for the advice too but we seem to be fixed without lowering security

consider this resolved thanks all

 

[cobaltit]

@sbv3000

I guess it depends on your definition of fixed. If all you wanted to do was to manually provision the phone then yes you are done. But legacy phone still won't be able to pull the provisioning file in the way you were originally intending. Also I don't think you need to worry about lowering security. Something tells me that if you had need to be PCI compliant you'd have budget for something a little more current than a T22

 

[cobaltit]

Also, every time 3CX makes template changes you're going to have to manually download the template and upload it into the phones instead of having them pushed down automatically.

 

[YiannisH_3CX]

Glad to see the issue has been resolved, i will however agree with @cobaltit on this one. It will save you a lot of time if you could auto provision the phone. If you cannot provision the phone automatically then you cannot even add blf keys or change a setting from the management console.

 

[sbv3000]

Hi guys
Thanks for the feedback, very useful and appreciated.
You are correct on all counts, my initial issue is moving a client I've taken on from on-premise running a windows 7 vm on version 11 (not joking), to v15 cloud and as usual they want least costs. If I can get them up and running using the current phones that's stage 1. However I'm insisting that they have a maintenance agreement and budget to replace phones longer term. I'll point out the quirks about phone changes, they are low end users, dont use presence/blf etc so manageable in the meantime