Cannot provision Yealink T26p through an SBC

[FuTech-Nel]

I have a yealink T26p on firmware 6.73.0.6 and I am trying to provision it through an SBC to my 3CX v 16.0.5.

The phone shows up on the list and I can assign it to the extension that I want. But the extension still shows as unregistered and the phone still shows on the phone tab as unassigned.

I go into the phone interface and use the provisioning link and click "auto provision" but that still does not work.

All the correct ports are open on my firewalls.

Is there something that I am missing.

 

[cobaltit]

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

 

[SweetAction]

What SSL cert are you using with 3CX? If you turn off trusted certs in the phone UI, does it work?

 

[Saqqara]

Device is end of life - look at the limitations - https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/

You need to untick ' SSL/SecureSIP Transport and Ciphers' under Security Settings within 3cx management console

 

[JohnS_3CX]

Hi @FuTech-Nel

As mentioned above, the devices are end of life and do not support modern TLS.

This means that when they try to connect to the PBX and download their settings, the connection will be refused.

You can go to Dashboard > Settings > Security > SSL/SecureSIP Transport and Ciphers {disable}

This will allow the system to negotiate TLS 1.0 which is less secure, but the provisioning should work.
If you then re-enable this option, the phones should still work afterwards but they won't be able to re-provision in case you make any changes to their extensions.

 

[FuTech-Nel]

@Saqqara and @JohnS_3CX, I provisioned a T26P phone via an SBC 5 months ago and I did not have to untick 'SSL/SecureSIP Transport and Ciphers' Why would i have to do that now? Did something change between then and now?

 

[JohnS_3CX]

Not sure how you did it 5 months ago, this is something you will have to explain to us

Run a capture on your phone and you will see why it cannot provision automatically.

 

[cobaltit]

@Saqqara and @JohnS_3CX, I provisioned a T26P phone via an SBC 5 months ago and I did not have to untick 'SSL/SecureSIP Transport and Ciphers' Why would i have to do that now? Did something change between then and now?

Unless you have a time machine this really doesn't matter. But the logical conclusion is that you were on an older version of the PBX at the time.