Search results

  1. 3CX Client - Windows 10 April Update

    @Marios Neophytou Better error messages in the client would be appreciated though :P 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.
  2. 3CX Client - Windows 10 April Update

    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.
  3. 3CX Client - Windows 10 April Update

    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.
  4. 3CX Client - Windows 10 April Update

    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...
  5. 3CX Client - Windows 10 April Update

    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).
  6. 3CX Client - Windows 10 April Update

    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...