Solved Provisioning old yealink phones with SBC

[johnthornstone]

For my part, on a 3cx server in the latest version, I manage to provision a T41P via an SBC as I mentioned above. But I agree that it's not supposed to work.

I've managed to get the T41P handsets to provision by disabling SSL/SecureSIP Transport and Ciphers (under Security > Anti-Hacking). I know this is exactly what you advised but I thought you meant disable "Secure SIP/TLS" (under Security > Secure SIP).

I'm very very happy now and you've saved me a LOT of time so thank-you very much indeed!!

 

[JohnS_3CX]

@johnthornstone just as a quick reminder: for as long as that option is disabled, your system is vulnerable to certain TLS attacks. We recommend you enable it ASAP now that the phones have been provisioned.

 

[JohnS_3CX]

Hi,
I am in the case where I have to provision yealink T41P phones behind an SBC. Provisioning is not natively possible because of protocol error : https://www.3cx.com/community/threa...ealink-t26p-through-an-sbc.75445/#post-341788

By disabling "SSL/SecureSIP Transport and Ciphers" in 3CX server security settings, provisioning works fine.
Phones have not been updated for a long time (firmware 36.80.0.95).

My question: If I update the phones to the latest firmware offered (36.83.0.130), will that fix the problem? Or, in general, do all "end of life" phones have this problem and need to disable "SSL/SecureSIP Transport and Ciphers" ?

Thank you in advance

Also to address Julien's original question:

- At the time this post was made this worked fine

- Much later in U5 this changed due to 3CX ciphers becoming more secure

- If Yealink sends us new firmware that brings back modern TLS we will publish it and you can provision it normally again

- I will lock this thread because it spans almost 3 releases and there will undoubtedly be confusion. If anyone has questions left unanswered, start a new thread in the appropriate category and include relevant information.