Solved Yealink T46G issues

[ggri]

I am running into an issue at one of our offices when we have more than one person on their Yealink T46G desktop phones with an external caller, only one of the calls is clear, and any additional calls are choppy and unintelligible to the other caller(s). We are not having this issue when simultaneously using the 3CX Android phone apps using wifi on the same network combined with only one person on their T46G desktop phone.

I have installed and configured the 3CX SBC, but that doesn't appear to be helping. I ran a speed test on our DSL and we have an upload speed of 1.5Mbps, so I don't think that's the issue. Any thoughts?

 

[cobaltit]

So installing the SBC only does something if you reconfigured the phones to use it. You didn't specifically mention that so I just wanted to confirm. Also, 1.5Mbps is a little low by today's standards but you should be able to do 12-15 calls if nothing else is going on at the time. But your description sounds like it's a bandwidth issue. I believe the Android client by default uses a lower bandwidth codec.

 

[ggri]

So installing the SBC only does something if you reconfigured the phones to use it. You didn't specifically mention that so I just wanted to confirm. Also, 1.5Mbps is a little low by today's standards but you should be able to do 12-15 calls if nothing else is going on at the time. But your description sounds like it's a bandwidth issue. I believe the Android client by default uses a lower bandwidth codec.

We only have 5 phones in that office, so I'm pretty sure we have enough upload bandwidth. I have not reconfigured the phones to use the SBC, can you share some insight on how I would do that?

 

[cobaltit]

Easiest thing to do would be to factory reset the phones and then use the PnP method described here:

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

 

[Rhys Haskell]

Are you sharing the connection for both voice and data?

 

[eddv123]

Choppy audio in my experience is normally down to dropped packets either due to lack of bandwidth on the WAN or a need for QoS techniques needed locally.

Try and identify if there are any bottlenecks on the network at all, either WAN or uplink between switches.

You could try a codec change also but since a single call is ok then I doubt it would be this.

The behaviour you are experiencing however I would say would be more related more to multiple STUN phones, not SBC, so it is strange you are experiencing this.

A quick fix might be PBX delivers audio on the extension however if using SBC this should not be required.

 

[Rob Novotny]

Try putting your phones into their own VLAN and then set priority for that voice VLAN over data. You will need a router that can handle VLAN's and also a smart switch to set the OUI of the Yealink to drop into the voice VLAN.

 

[eddv123]

That would be 802.1p (priority) and 802.1q (VLANs) you do not strictly need a VLAN aware router, just one that supports sub/multiple interfaces.

On the layer 3 diffserv would be useful also.

 

[ggri]

Problem is solved. I redeployed the SBC and reprovisioned the phones, and all works as it should. I had originally set up the SBC to use the wireless adapter on the host machine, and after changing it to the wired connection, it cleared up the issues. Thanks for all the advice, I appreciate it!

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.