Toggle sidebar Toggle sidebar

Solved Provisioning old yealink phones with SBC

Status
Not open for further replies.
JulienM

JulienM

Platinum Partner
Advanced Certified
Joined
Jan 4, 2022
Messages
66
Reaction score
32
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
 
  • Like
Reactions: JohnS_3CX
Hi Julien,

That post was for an entirely different model, and it doesn't apply to the T41P

Disabling "SSL/SecureSIP Transport and Ciphers" in 3CX server security settings is not required for the T41P.
I can confirm that it will happily provision on the latest version of 3CX V18 U3 just like the newer models would.

We always recommend to upgrade to the latest 3CX-provided firmware before you provision the phone for the first time. You can see it as Step 1 in our guide: https://www.3cx.com/sip-phones/yealink-t4-series/

If you provision it using the latest firmware 36.83.0.130 it won't give you any trouble.
As for the older firmware (36.80.0.95), we do not test it nor do we support it so I have no clue whether it will work as intended.
 
Hi,

We are having a similar problem. We cannot provision a Yealink T26P phone through SBC.

Version 18 - Hosted by 3CX

I have disabled Secure SIP/TLS under Dashboard/Security/Secure SIP. Is there something I am missing?

The phone shows up as a new phone under plug and play but does not provision and does not provision by manually entering the provision link.

Thanks
Carl
 
Last edited:
@2way
I think you may have disabled the wrong setting. What you have to disable is the following:
1649248872866.png

This is under "Security >> Anti-hacking" scroll to the end.

Try again and let me know if it works.
 
Thats it! TY sir
 
  • Like
Reactions: ChrisC_3CX
@2way

You're very welcome!
 
Hi @johnthornstone
Since update 18U5, T41 models are no longer displayed in the list of EOL phones. However, it seems to me that provisioning behind an SBC works, the model goes up and it is still possible to provision it. This requires: updating the phone's firmware if it has not already been done and disabling "SSL/SecureSIP Transport and Ciphers" in 3CX server security settings.
I had tested this in 18U5 but I have not tested again since the last updates.
 
JulienM said:
Hi @johnthornstone
Since update 18U5, T41 models are no longer displayed in the list of EOL phones. However, it seems to me that provisioning behind an SBC works, the model goes up and it is still possible to provision it. This requires: updating the phone's firmware if it has not already been done and disabling "SSL/SecureSIP Transport and Ciphers" in 3CX server security settings.
I had tested this in 18U5 but I have not tested again since the last updates.
Click to expand...
I updated the T41P to the latest supported 3CX firmware (36.83.0.130) and factory reset it, disabled Secure SIP/TLS, restarted everything but unfortunetely the T41P still wouldn't provision. Looks like my only option is to painfully manually provision each one :(
 
johnthornstone said:
I updated the T41P to the latest supported 3CX firmware (36.83.0.130) and factory reset it, disabled Secure SIP/TLS, restarted everything but unfortunetely the T41P still wouldn't provision. Looks like my only option is to painfully manually provision each one :(
Click to expand...

I just tested on my side, I have no problem provisioning a T41P behind an SBC with the option "SSL/SecureSIP Transport and Ciphers" disabled. Is your phone well discovered by the SBC ?
 
@johnthornstone Yealink might consider upgrading the firmware on a couple more older models like they did with T29G, T46G, T48G. If they do we will announce it, and you should be able to provision them normally again.

For now, you will have to do them manually. The method Julien mentioned also works, but you have to make sure to enable it afterwards otherwise there will be a compromise in security making your system vulnerable.
 
  • Like
Reactions: accentlogic
JohnS_3CX said:
@johnthornstone Yealink might consider upgrading the firmware on a couple more older models like they did with T29G, T46G, T48G. If they do we will announce it, and you should be able to provision them normally again.
Click to expand...
That would be very good news :)
 
JulienM said:
I just tested on my side, I have no problem provisioning a T41P behind an SBC with the option "SSL/SecureSIP Transport and Ciphers" disabled. Is your phone well discovered by the SBC ?
Click to expand...
That's very interesting you managed to provision via the SBC, was that using firmware version 36.83.0.130? I can provision a T42G and T42S via the SBC but not T41P. I've lost count how many times I've factory reset the phones. The SBC does detect and show the T41P handsets, yes.
 
johnthornstone said:
That's very interesting you managed to provision via the SBC, was that using firmware version 36.83.0.130? I can provision a T42G and T42S via the SBC but not T41P. I've lost count how many times I've factory reset the phones. The SBC does detect and show the T41P handsets, yes.
Click to expand...

Yes, the T41P is in firmware 36.83.0.130. When you assign the phone to an extension, nothing happens I guess? On my side, this is what happens when "SSL/SecureSIP Transport and Ciphers" is activated.
 
JulienM said:
Yes, the T41P is in firmware 36.83.0.130. When you assign the phone to an extension, nothing happens I guess? On my side, this is what happens when "SSL/SecureSIP Transport and Ciphers" is activated.
Click to expand...
Nope does nothing. I also tried the STUN provisioning method as well but that didn't work either. I'm going to try setting up the SBC on a Linux environment tomorrow to see if that makes any difference.
 
johnthornstone said:
Nope does nothing. I also tried the STUN provisioning method as well but that didn't work either. I'm going to try setting up the SBC on a Linux environment tomorrow to see if that makes any difference.
Click to expand...
The T41P phones, as already mentioned by my colleague, are no longer supported. In all new systems currently, there is no template for th T41P, so you will not be able to provision it regardless of which method is used, I'm afraid. Only manual connections will work.

You did, though, also mention you tried with STUN. Which phone template have you assigned to the extension?

https://www.3cx.com/sip-phones/yealink-t4-series/
 
Charles_3CX said:
The T41P phones, as already mentioned by my colleague, are no longer supported. In all new systems currently, there is no template for th T41P, so you will not be able to provision it regardless of which method is used, I'm afraid. Only manual connections will work.

You did, though, also mention you tried with STUN. Which phone template have you assigned to the extension?

https://www.3cx.com/sip-phones/yealink-t4-series/
Click to expand...

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.
 
johnthornstone said:
Nope does nothing. I also tried the STUN provisioning method as well but that didn't work either. I'm going to try setting up the SBC on a Linux environment tomorrow to see if that makes any difference.
Click to expand...

I just thought of this, did you enable the "alternative firmware" option in the Phones section ?
 
Charles_3CX said:
The T41P phones, as already mentioned by my colleague, are no longer supported. In all new systems currently, there is no template for th T41P, so you will not be able to provision it regardless of which method is used, I'm afraid. Only manual connections will work.

You did, though, also mention you tried with STUN. Which phone template have you assigned to the extension?

https://www.3cx.com/sip-phones/yealink-t4-series/
Click to expand...
Sorry I'm sort of new to 3CX so not sure what you mean by phone template. I pretty much just select ther T41P handset in the phone section and assign it to a user, select 3CX SBC (remote) as the provisioning method + the SBC01 controller and then leave everything else as default. This has worked for the T42G and T42S handsets at least.
JulienM said:
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.
Click to expand...
What version are you using? My SBC version is 18.1.36
JulienM said:
I just thought of this, did you enable the "alternative firmware" option in the Phones section ?
Click to expand...
Yes that's already enabled but good shout.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,973
Messages
590,078
Members
164,896
Latest member
sameage
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom