Yealink Opus Template Support

[ltctech]

I see that 3CX ships a template that supports configuring Opus-WB 16kHz for the Yealink T56A and T58. Nearly all of the other modern Yealink phones support Opus-WB 16kHz, yet the 3CX template has not been updated to enable it. The Web Client is already using Opus as that's part of the WebRTC standard. It's time to enable it on the desk phones, as otherwise there's a whole bunch of transcoding occurring.



All but one phone (T29G) that don't support it have been classified as EOL by Yealink:
https://www.yealink.com/product/voice-communication-t48g

While we could make a custom template to enable Opus, we don't want all of our phones to be unsupported by 3CX. Are there plans to update the built-in templates?

 

[IZT_crobinson]

+1 Our lonely t4 series don't get any love

 

[eddv123]

+1 I would agree with this, OPUS is the a next generation codec and needs support on the handsets.

What I would say however is that having this support on handsets for local extension to extension calls is a good idea, however if you do not use a trunking provider who supports this codec also then there is less point of this.

There are few providers that support this codec (Voxbone is one who do) but most dont as they would require upgrades and licence updates = $$$$

 

[ltctech]

What I would say however is that having this support on handsets for local extension to extension calls is a good idea, however if you do not use a trunking provider who supports this codec also then there is less point of this.

PSTN uses G711, so trunking providers offering anything else are dubious. Mobile networks use AMR-WB though I'm not sure if any allow it via peering.

Where Opus really shines is extension to extension calls. G722 is good, but not good enough when the transcoding source is G711; it sounds tiny and occasionally muffled. Opus-WB 16khz transcodes G711 very cleanly.

None of this would be a big deal if 3CX would intelligently select codecs to avoid transcoding sip trunk calls:
https://www.3cx.com/community/threads/disable-transcoding.61461/#post-337493

 

[cparker_RCT]

I've done some "science" based testing on calling out to the PSTN and can confirm that OPUS <-> G711 transcoding is tolerable. While G722 <-> G711 leaves A LOT to be desired.

 

[jwmilleril]

I was able to turn on Opus manually via the web interface of the phone itself and I get an Opus call to work. But, we really would prefer it be in the standard template.

 

[ltctech]

I was able to turn on Opus manually via the web interface of the phone itself and I get an Opus call to work. But, we really would prefer it be in the standard template.

Yes, that'll work until the phone re-provisions itself. So it's fine for testing, but not production. Production would require a custom template or 3CX to add it into the standard template.

You would also need to move Opus to the top of "Codec Priority for Local/Internal Calls" and "Codec Priority for External Calls" under Settings -> General. Otherwise an extension may initiate an OPUS call but the called (bridged) extension may be transcoded to something else. This is easy to spot as one extension will show an "Opus" badge on screen, while the other will show nothing or "HD" for G722.

3CX "Internal" and "External" nomenclature is a misnomer; Remote STUN phones appear to be treated as "External". Why 3CX doesn't respect the caller's codec order when bridging calls is beyond me.