Audio quality in web client worse compared to desktop client?

[daniel.hartley]

We really like the web client on our end but the hold up with wider adoption across our customer base is the audio quality.

The audio quality on the web-client compared to the desktop client just simply isn't as good. It sounds more compressed, robotic. Like you're talking over a drive-through speaker.

We've tried using USB headsets vs bluetooth headsets and it doesn't make much difference.

We can replicate the audio quality difference across PCs too. All running latest chrome, multiple headsets tried. Same distinct call quality differences.

Is this a known issue? Is there a quality fix in the works?

 

[jmitch11]

Do you have QoS setup across the entirety of your network? I recently moved our users over to the webclient and the feedback I got was nothing but positive when it came to the quality of the call.

 

[gbdoin]

I've noticed a significant difference in audio quality as well on the web client using the Chrome extension. I haven't tested it through, but I'm positive this is easily replicable.

I've asked couple people whether they noticed a drop in audio quality when on the phone with me (while I'm using the Chrome extension), and I haven't had bad feedback. On my end however, audio I receive from sources external to 3CX seems much more compressed. It's not as bad when it comes from other extensions of the same system.

There doesn't seem to be any options yet related to audio quality on the client. How can this be addressed? Audio quality on other 3CX apps is flawless.

 

[Paul Reynolds]

Do you have QoS setup across the entirety of your network? I recently moved our users over to the webclient and the feedback I got was nothing but positive when it came to the quality of the call.

Hi, I work with Dan,

We've double checked and unfortunately there's no QoS at play anywhere.

I didn't think this would make much/any difference but I've re-ordered the Codecs to put the highest quality at the top for internal calls under General settings and for his and my extensions for the App under Phone Provisioning. As expected it didn't make any noticeable improvement.

When we're making calls between the web app the audio isn't breaking up or crackling, but it's noticeably lower quality. The best way I can describe it is it's like speaking through the McDonald's drive in speaker. Distant and tinny. I use a Jabra 930 Pro with no issues when using the PC app.

Thanks
Paul

 

[ECOM GROUP (Mauritius)]

We really like the web client on our end but the hold up with wider adoption across our customer base is the audio quality.

The audio quality on the web-client compared to the desktop client just simply isn't as good. It sounds more compressed, robotic. Like you're talking over a drive-through speaker.

We've tried using USB headsets vs bluetooth headsets and it doesn't make much difference.

We can replicate the audio quality difference across PCs too. All running latest chrome, multiple headsets tried. Same distinct call quality differences.

Is this a known issue? Is there a quality fix in the works?

Can you set your codec to G.722 and check.

 

[Paul Reynolds]

Can you set your codec to G.722 and check.

Hi,

Can I just check, when you say change to G.722, do you mean under 3CX App under the Phone Provisioning? There doesn't seem to be a separate Codec setting for the web app.

Would I remove all other codecs except or G.722 or just make it the first priority?

As it stands, for the "3CX App" under the extensions phone provisioning we have the following set

SIP Transport: UDP
RTP: Normal
DTMF: RFC2833

Codec Priority
opus
G722
G.711 U
G.711 A
G729
GSM



Thanks
Paul

 

[ECOM GROUP (Mauritius)]

Hi,

Can I just check, when you say change to G.722, do you mean under 3CX App under the Phone Provisioning? There doesn't seem to be a separate Codec setting for the web app.

Would I remove all other codecs except or G.722 or just make it the first priority?

As it stands, for the "3CX App" under the extensions phone provisioning we have the following set

SIP Transport: UDP
RTP: Normal
DTMF: RFC2833

Codec Priority
opus
G722
G.711 U
G.711 A
G729
GSM



Thanks
Paul

Coder in user extension (user who is using the web interface. Click on an extension , go to phone provisioning tab, scroll below and use only G.722 as first, second and third use G711.a and u

 

[ECOM GROUP (Mauritius)]

Coder in user extension (user who is using the web interface. Click on an extension , go to phone provisioning tab, scroll below and use only G.722 as first, second and third use G711.a and u

Note after changing the Codec, You have to reprovision the extension. otherwise it will not be updated. and log out first from the webclient

 

[JohnS_3CX]

We really like the web client on our end but the hold up with wider adoption across our customer base is the audio quality.

The audio quality on the web-client compared to the desktop client just simply isn't as good. It sounds more compressed, robotic. Like you're talking over a drive-through speaker.

We've tried using USB headsets vs bluetooth headsets and it doesn't make much difference.

We can replicate the audio quality difference across PCs too. All running latest chrome, multiple headsets tried. Same distinct call quality differences.

Is this a known issue? Is there a quality fix in the works?

Hi Daniel,

Do you have recordings enabled when you make the "low quality" call?

Can you disable them and make a webclient-to-webclient call and compare the before and after?

 

[VoIPQZ]

Oddly enough, on our end it's the other way around. We've noticed an increase in quality going from Desktop Client to Web client. Both Web to Web and Web to External. First the sound is louder (I've had a tons of complaint about calls being hard to hear on the Desktop client, and also a few reports about the volume decreasing every calls on the Desktop client, to the point where you cant hear anything anymore after a few calls).

As for audio quality persay, I had complaints here and there when I first installed the Desktop client across our office, and since the switch to Webclient last week, I've had nothing but good feedback on it.

Using Sennheiser headsets with integration if that makes any difference.