Forcing a Yealink T42S to use TLS instead of UDP

[mike9055]

Hello,
i have several STUN phones on a lightsail hosted 3CX, and we don't want to use SBC, we would need 20 of them, we have 180 extensions in several branches, everything is running perfectly, using/removing STUN (phone side) makes no difference

Some of our T4x phone somehow don't register using the default UDP 5060, some do, others just don't. Same supported firmware, same network.

Every phone DOES register using TCP 5060 or TLS 5060 BUT if i reboot the phone goes back to UDP

So i went in Templates, copied the T4x template to T4xTLS deleted a couple lines

account.1.sip_server.1.transport_type =
account.1.sip_server.2.transport_type =

And now the phone starts in UDP but if set to TLS or TCP it stays that way after a reboot/reprovision, i guess editing line 2948 account.1.sip_server.1.transport_type = 0 to account.1.sip_server.1.transport_type = 2 would do the trick, but i'm fine with the phone starting in UDP and manually switching if needed

What is the problem? I'm stuck with the red ! Phones and red named phones, and i don't like it

- i tried editing /var/lib/3cxpbx/Instance1/Data/Http/Templates/phones/yealinkT4x.ph.xml but no success as "admin"
- tried restarting MC

So, how do i elevate to root to make this simple change?
Tried su with admin password with no luck, i did not set up a root password (LIGHTSAIL does not require this step)
Is there a more subtle way to get this simple change without the annoying warning?

Thank you very much


PS: also, i show up as Customer/intermediate, but we are a new Bronze Partner with Advanced certification, how do i correct that?

 

[JohnS_3CX]

Hi Mike!

We would strongly advise against modifying the system files. This would immediately render your installation as unsupported.

If you want to modify the templates use this method, but make sure you also read the important note at the bottom:
https://www.3cx.com/docs/custom-ip-phone-templates/#h.lbdvgcnoj4wf

 

[mike9055]

Understood, i'll try that guide, thank you

But let's say we want the root password for our lighstsail instance, i can't find any documentation about that.
We like to have keys to our homes and this is our own company pbx

I HAVE root password for other cloud instances installed with the iso, why is is so difficult to get that for Lightsail?

 

[JohnS_3CX]

I'm afraid that won't go away if you use anything other than our supported templates. And perhaps the customer should be aware that their phones are using modified templates (because there is a risk vs reward relationship there). There's always a chance that a change that was made will cause unexpected issues in the future, and hiding the red marks would basically be hiding the first thing that should come under scrutiny during troubleshooting.

If the customer contacts us directly will inform them that we do not provide support for it, and if they are facing issues that stem from STUN (and believe me, there were enough issues that we dedicated company resources to building and maintaining the 3CX SBC) we will advise them to switch to using the SBC to see if their issues go away.

By the way, are you aware of the new feature we just released in V18 Update 6? Certain Fanvil and Yealink phones (T53, T53C, T53W, T54W, T57W) now have the 3CX SBC built right into their firmware. Each phone can act as its own SBC, and also act as the SBC for a few more phones. This should pretty much reduce the need for STUN to practically zero, while saving you bandwidth on extension to extension calls, securing communications via the built-in SBC TLS encryption, and allowing easy remote provisioning of your devices. Upgrade one of your lab PBXs to the latest U6 Beta build and give it a spin, I think you will be pleasantly surprised!

 

[mike9055]

I am aware of the new feature, i actually tried to use my personal T53W as a SBC but could not find HOW to do that, both on U6 alpha and beta, no updates were offered to my phone, i couldn't find a "sbc" firmware anywhere.

I will avoid opening tickets about this but i just changed a 0 to 2 to have the phone start in TLS instead of UDP and by the way, the linked guide provides a longer way to just copy a default template and edit the copied one, the only result i got was the new template showing as "personalized" instead of "custom", but still red text.

I opened a ticket to have the root password of our installation

I am the customer in this case, i am aware, i just don't want to be reminded, and i manage our customers pbxs

Thank you

 

[JohnS_3CX]

Understood!

If you want to give the T53W SBC phone a spin, you can do it via the webclient admin panel.
You will have to delete it from your current extension and factory reset it first.

We've now updated our guides (including firmware links) to help you set this up, just follow the instructions here and you will get a prompt to add a "Router" phone: https://www.3cx.com/sip-phones/yealink-t5-series/#h.2xub9hfvs4dw

Once your phone is up and running, you can even add a second "Normal" phone (ie. a T4x model), and you can set it to use your T53W as its SBC. Give it a go and let us know what you think!

 

[mike9055]

I tried, it works, really nice feature
I also solved my problem on Lightsail

Flaws:
- no SBC or compatible phones? You can't add any phone via webclient
- sbc/phone reboots/breaks > no phone will work

We don't want simple devices to be the single point of failure in a voice network, we don't want do deploy multiple redundant simple devices, we don't want do install software sbc on a dedicated server, we don't want to add hardware when one of the point of going cloud is removing unnecessary hardware

Thank you for your replies