t46g sound quality problem vs t20

[asinshesq]

Hi, everyone. I have been running t20 phones on my local lan 3cx system (tied to my external pstn telephone service with a patton 4114 fxo gateway) for a few months. The sound quality from the handset (and via a plantronics 361n headset) has always been fine. A week ago I replaced the t20 with a t46g phone (and the 361N headset with a cs510 headset) and the sound is now awful. On the handset, the sound seems over-processed (it sounds robotic) with some cutouts that I never had with the t20. And the sound through headset is really bad (seems like the sound problems get exacerbated when I go via dect to the headset). I tried using the cs510 'wideband' setting and that was even worse. People I am talking to, however, report that I sound fine to them.

I am thinking there must be a setting I have screwed up (maybe in 3cx or maybe in the t46 settings?). For example, maybe I need to activate different codecs?

Anyone have a suggestion? The phone is pretty bad this way, and the phone/headset combo is almost unusable (well, I can use it but my wife can't ).

Thanks.

Alan

[asinshesq]

I just checked the active codecs on my t46g and they appear in the following priority:
pcmu
pcma
g722
g729

I saw a list somewhere else that had the last two switched (g729 and then g722) so I tried that but no difference. If the only calls I am worried about are via a patton 4114 fxo gateway to a US pstn, what codec should I be listing first? Also, do these codecs have anything to do with how my plantronics headset communicates with the t46g? If so, how should I be setting things up to make sure the connection to the headset sounds good?

One other suggestion I saw was to change the jitter setting from adaptive to fixed at 120ms/120ms/120ms. Is that something that will help with drop outs?

Any other ideas?

[asinshesq]

Getting closer: the handset audio is now fine but the headset port audio is really bad compared to the handset port audio (in each case when using my plantronics cs510). Is there some hidden settings that will make the headset port behave like the handset port so I don't need to use my headset with a lifter?

[asinshesq]

Sorry to bump, but is there a way to tinker with the config files (either the y00000028.cfg file or the full config.bin dump from the phone) to change the behavior of the headset so that it is identical to the handset? Thanks.

[Yealink Support]

Hi asinshesq,

Do you mean you use the plantronics cs510 headset with Yealink T46, the sound quality of headset is awful, but the sound quality of handset is fine? Is it right?
I have some confusions about this, could you please provide more details?
1. Is the plantronics 361n a wired headset?
2. How about the sound quality of speaker phone?
3. If the plantronics cs510 is a wireless headset, how did you connet the headset with T46?

Because if you want to use wireless headset with T46, you need use EHS36 to connect with phone.
Please refer to the guide. >>EHS36_User_Guide<<

[asinshesq]

(08-19-2014 01:56 PM)Yealink Support Wrote:  Do you mean you use the plantronics cs510 headset with Yealink T46, the sound quality of headset is awful, but the sound quality of handset is fine? Is it right?

Not quite. I mean that the sound quality of the headset is awful when I plug it into the t46g headset port, but the sound quality of that same headset is fine when I plug it into the t46g handset port.

(08-19-2014 01:56 PM)Yealink Support Wrote:  1. Is the plantronics 361n a wired headset?
2. How about the sound quality of speaker phone?
3. If the plantronics cs510 is a wireless headset, how did you connet the headset with T46?

The 361n and the cs510 are BOTH wireless headsets. The 361n does not use an ehs36 connection but instead plugs into the handset port and uses an hl10 lifter, and that's how I discovered that the handset port and headset port are totally different in quality on my t46g phone. Then I tried plugging the cs510 in the handset port of the t46g and that works fine too. It's only when I plug the cs510 in to the headset port of the t46g the way it is supposed to be when using the ehs36 that I have a problem.

(08-19-2014 01:56 PM)Yealink Support Wrote:  Because if you want to use wireless headset with T46, you need use EHS36 to connect with phone.

Yes, that's what I have been using when I had the headset plugged in to the headset port. One additional question occurs to me: is it possible that there's something about the ehs36 connection that is causing the distortion? This seems unlikely (it seems like that connection should either work or not) but I figured I would ask.

[Yealink Support]

Hi asinshesq,

Sorry, we suggest you not to plug wireless headset into handset/headset port directly. Some headset can hear the voice via this method, but this operation will hurt your phone/headset.
Please use EHS36 to connect the phone and the wireless headset correctly.
If you use EHS36 connection but it still doesn't work, it maybe Yealink phone haven't done compatibility with that module headset.
Please refer to Tested headset list compatible with Yealink IP Phone.
>>Tested headset list compatible with Yealink IP Phone<<

thanks

[asinshesq]

Thanks, but as I mentioned I am using the ehs36. In particular, I am using the ehs36 patch cord (the one that has an rj45 on one end and an rj9/11 on the other and an extra rj9/11 port in the middle) to connect the headset audio to the t46g headset or handset port. (When I moved from the headset port to the handset port, I started using an hl10 lifter rather than the ehs36 patch cable that goes into the 'ext' port on the t46g, but I think that just determines how the phone gets picked up to go off hook so should have nothing to do with the audio quality, right?).

I also know that this headset and the t46g (and ehs36) are compatible, and I further know that the combo works fine when I use the t46g handset port rather than the t46g headset port. I'm pretty sure this is a hardware problem (i.e. that there is something wrong with the headset port on this particular t46g). I am using .45 firmware and my understanding is that headset and handset ports should sound identical for any firmware after .37 so the fact that they are different is suspicious.

[Wilson_Yealink]

Thank you for prompting. About the hardware problem you mentioned, we need to confirm with our hardware engineer. Gennerally, users won't plug the wireless headset to handset/headset port. If so, the headset only can here voice but can't do pick up or hang up operation.
We only suggest that the wireless headset need to connect the EHS36, and plug ehs36 patch cable that goes into the 'ext' port on the t46g. Please refer to the guide to connect your headset and ehs36 correctly.
>>EHS36_User_Guide<<

If you have any issue after correct connection, I am so glad to help you.

[vkeven]

Same problem here the headset sound bad and handset sound muffled , T28P sound perfect . .37 firmware sound correct ( handset ) but its a one time firmware , we could not depend on this for "production" deployement ,