3CX with Yealink T54W dutch language use router function

[Rogé]

I have some customers which are using Yealink T54W phones with the Lydis firmware so they support the dutch language. These phones where used by STUN and not work with the router function as this is not supported in the Lydis firmware. I know its not recommended but worked fine for the 2 or max 3 devices my customers have.

Now iam testing a V20 version with one of these phones and cannot connect them to 3CX anymore without placing an 3CX SBC inside the network which required extra hardware and software to maintain. Also i don't want to tell my customers that they need to buy some extra hardware and pay me for installing it because 3CX updates their software.

Is there anyone else with this problem and where they be able to use these phones with 3CX and Dutch language wihtout placing extra hardware/software?
- And to avoid any discussion, i want to provide dutch language on the phones. -

 

[JohnS_3CX]

Ok since the firmware change is out of the question, then your only option is an SBC.

If they worked in V18 they would have continued to work in V20 (we did test and confirm the migration), however its clear that they are not. And now you know why STUN is no longer supported - it's an unreliable method that can sometimes work and other times not.

You can host the SBC on an machine that is already at the customer's premises (it has to always be on and have a reserved/static IP), or you can use a Raspberry Pi or small Linux PC which should keep costs low.

Just to be clear, this is not related to V20 - STUN can stop working at any moment at any version for a long list of reasons. You either live with it, or use an SBC. The cost is totally worth it compared to troubleshooting STUN phones causing unhappy customers.

 

[Rogé]

Ok since the firmware change is out of the question, then your only option is an SBC.

If they worked in V18 they would have continued to work in V20 (we did test and confirm the migration), however its clear that they are not. And now you know why STUN is no longer supported - it's an unreliable method that can sometimes work and other times not.

You can host the SBC on an machine that is already at the customer's premises (it has to always be on and have a reserved/static IP), or you can use a Raspberry Pi or small Linux PC which should keep costs low.

Just to be clear, this is not related to V20 - STUN can stop working at any moment at any version for a long list of reasons. You either live with it, or use an SBC. The cost is totally worth it compared to troubleshooting STUN phones causing unhappy customers.

Ok, at some customers i have a machine that i can also use as SBC but then the next issue pops up. Not all of these customers have a fixed IP or an IP4 address at all on their internet connection. So how to deal with this? Is there no way to keep using STUN with V20?

 

[NicholasP_3CX]

There is no need for a static public IP Address for their internet. The static IP Address my colleague mentioned is for the INTERNAL IP for the device.

The SBC works in an identical fashion to the tunnel in the 3CX mobile apps. It will establish a secure connection back to the PBX. Once the connection is established, the PBX will be able to send calls to and from the extensions.

 

[JohnS_3CX]

k, at some customers i have a machine that i can also use as SBC but then the next issue pops up. Not all of these customers have a fixed IP or an IP4 address at all on their internet connection.

Actually the SBC is very good with this and is designed to handle it. As soon as the public IP changes, the SBC will reconnect shortly from the new IP.

Is there no way to keep using STUN with V20?

But you already have them as STUN and they don't work. Plus we no longer provide support for STUN.


By the way a suggestion, if you have one user who is friendly and doesn't mind to use english on their T54W, you can convert just one in the office to the new firmware and it will act as the SBC for all the other phones in the office too.

 

[noord]

I was also really a fan of STUN and direct connections, but I can tell you an SBC makes your life 100 points easier. Yes, also when customers have only one or two phones that seem to work fine.
It's a lot easier to deploy new phones, but it's also a whole lot safer since your port 5060 is no longer open for SIP-credentials guessing. Also, internal calls never leave the network and are handled locally by the SBC.
No more issues with one-way audio. No more strangeness.

And since the introduction of the router phones, no more need for a separate hardware SBC either.
You can even just get an extra T54W or other phone just to configure it as a router phone.

And now the real issue:
The real problem is Lydis and Yealink.
Yealink firmware supports dozens of languages out of the box.
But, the Dutch language is made by Lydis and has it's own special version number.
They are always some versions behind.
And, you cannot download it from the Lydis website either. You need to contact them directly (or have it done via 3CX).

Yealink and Lydis should stop making the Dutch language a separate version and just integrate Dutch in the normal firmware like every other language. Problem solved