I (have to) use your WebClient on Debian 9.5 and experience issues since the last google-chrome update. The message from your web client is "Could not start audio source". However, it worked before. After downgrading chrome it did not start working again.
My setup:
The browser console also only states: DOMException: Could not start audio source.
Playing audio in general works, also from chrome. Recording also works, if it works from chrome I cannot tell, its the only service I use which uses audio. I also tried in FireFox. There it works, but I have to switch the audio sink / source after each start (Internal audio to Headset), which is PITA.
By the way: While I was writing this ticket, the headset started ringing for an incoming call, so audio seems to work. But when I click the accept call button, the error message pops up, but it keeps ringing.
I need help identifying the issue, as the error message gives no clue.
My setup:
- OS: Debian 9.5
- Browser: google-chrome (ATM downgraded to 69.0.3497.100), 64bit.
- Jabra Engage 65 headset
The browser console also only states: DOMException: Could not start audio source.
Playing audio in general works, also from chrome. Recording also works, if it works from chrome I cannot tell, its the only service I use which uses audio. I also tried in FireFox. There it works, but I have to switch the audio sink / source after each start (Internal audio to Headset), which is PITA.
By the way: While I was writing this ticket, the headset started ringing for an incoming call, so audio seems to work. But when I click the accept call button, the error message pops up, but it keeps ringing.
I need help identifying the issue, as the error message gives no clue.
