3CX Client - Windows 10 April Update

[betahr]

Last week I updated my Win 10 Pro to the version 1803 (April Update), after that when I try to call someone with the 3CX client i get the error "call failed", i can't call neither other extensions or external contacts (writing the number in the dialer).
I tried to reinstall and disable Plantronics Hub to use normal system audio device but it didn't resolve anything.
Am I the only one experiencing this problem?

 

[schimanj]

Same here.
It seems as the client tries to open the audio device (no matter what you select) multiple times with different clock-rates.
Here the relevant part of the client log: https://pastebin.com/6gwkzPCE

Note the line that says:
Unable to open sound device: Unknown pjmedia-audiodev error 450001

Right after:
WaveAPI Sound player ... clock_rate=8000 ...

@betahr can you confirm this?

Edit:
The client log can be found in:
C:\Users\<Username>\AppData\Roaming\3CXPhone for Windows\Logs

 

[betahr]

I have the same errors in my logs:
"Unable to open sound device: Unknown pjmedia-audiodev error 450001 [status=450001]"

Last week with old Windows build it worked perfectly, I'm having troubles since the update, same for you?

 

[schimanj]

Yeah, before the update everything was just fine.
I've also ensured up-to-date drivers and even the bios (well knowing it wouldn't help).

 

[betahr]

I tried to rollback to Windows 1709 and now I can finally answer to incoming calls!!

 

[progtech]

@3cx Any fix in progress?

 

[betahr]

Yesterday I wrote an email to the tech support and they told me that there isn't any problem and the client runs perfectly on Windows 1803, they said that the problem is how i configured audio options...

 

[schimanj]

That's non-sense.
I tested everything there is to test in regards to audio devices.
I've reinstalled the client many times ensuring to remove every last bit of it (registry, temp files etc.).

Also, all tested audio devices work just fine in windows itself and with other applications.

I even had a look at the source of pjsip (the open source library they use for all things audio) and if we have a look at the log again (the one I posted yesterday https://pastebin.com/6gwkzPCE) it's clear that wmme_dev_3cx.c tries to open the sound-device over and over with different clock rates.
Unless it actually fails opening it every time (which there's no mention of in the log other than the last try with a clock-rate of 8000), this is wrong.

Observing the log on a Windows 1709 setup, you can see it opens the sound device once and than proceeds with everything else.

 

[John Ha]

Any updates on this as it has been a few days now.

 

[Marios Neophytou]

What version of Windows 3CX client and Plantronics hub are you currently using?
As I can not see any issue on my environment.

 

[[email protected]]

on some soundcard like realtek it works, on some others not like conexant ISS audio

 

[betahr]

I had the problem on my laptop: an HP Spectre X360 with a Conexant ISST board, driver version 9.0.68.61 (16/05/2017) - I checked with HP Support Assistant and it seems to be the latest version.

We also updated some desktop pc to Windows 1803 and there isn't any problem, but they all have a Realtek audio board.

 

[schimanj]

I've the latest version of both the 3CX client (15.5.10795.4) and Plantronics Hub (3.11.0 Build 17287) installed.
I did test both, the Plantronics Headset and internal audio (also closed Plantronics Hub and unplugged the device) of my notebook both resulting in failed calles.

 

[betahr]

I've the latest version of both the 3CX client (15.5.10795.4) and Plantronics Hub (3.11.0 Build 17287) installed.
I did test both, the Plantronics Headset and internal audio (also closed Plantronics Hub and unplugged the device) of my notebook both resulting in failed calles.

Same as me, do you have Realtek or Conexant audio card?

 

[schimanj]

Same as me, do you have Realtek or Conexant audio card?

It's a Realtek card.

I can't believe this.. I just found the issue *sigh*

Everyone else check the following:
Windows Settings -> Privacy -> Microphone

Make sure that apps are allowed to use the microphone.

 

[Marios Neophytou]

Just follow what @schimanj did and it will solve the problem
Nice catch schimanj

 

[schimanj]

@Marios Neophytou Better error messages in the client would be appreciated though

The only reason I figured this out was because I installed teamspeak just to test with another client and teamspeak actually told me that it does not have sufficient permission to access the microphone.

 

[Marios Neophytou]

Thank you for reporting that once again
We will provide a fix in a future release