[triage]: Tommi, can you help with an owner?

henrika: can you confirm or ask for more details if needed?

tornister76: Can you try on the latest stable (52) or a Chrome Beta/Dev/Canary release to see if the same problem occurs? 
See https://www.chromium.org/getting-involved/dev-channel for more info.

+tommi given that the issue seems related to work done in 340377.

tornister76: 
1. Which version produced output on the communications device?
2. Do you have a page where we can reliably reproduce output to the communications device on the old version and output to the default device on the new version?

[triage] tornister76: can you provide more information as requested in comment #6?

Hi, 

We are using zendesk voice functions on zendesk.com.

Until few months ago we were using it on windows 10 computers with chrome, setup with usb headset as communication device for mic and audio and regular realtekaudio as default audio device. So when call was incomming, we heard ring by default audio and after recieve wehrard ans speak trought usb headset. 

Now it is not working. If we want to hear incomming call ring on loud speaker we haw to leave it as w10 default audio and after takeing call we have to manualy change w10 output to usb headset.

Dnia 09.09.2016 o godz. 15:27 kjellan… via monorail <monorail+v2.667012102@chromium.org> napisał(a):

By default, Chrome uses the default device (not the default communications  device) and I believe this has always been the case.

On Windows, the communications device is available by using the device ID "communications", but the application must explicitly request it by specifying that device ID in the constraints passed to getUserMedia.

tommi@: can you confirm this?

Note also that you can select a different default microphone to be used via chrome://settings. This option takes precedence over the OS default.

I konw it, and in adress bar at chrome on zendesk page, (when we select zendesk to use browser audio ) cam icon appears and them we select audio device - communication device. we use to work for many months like this but not any more

Dnia 09.09.2016 o godz. 16:00 gui… via monorail <monorail+v2.422849203@chromium.org> napisał(a):

Can you check chrome://settings and see what microphone you have selected as default?
If you choose the communications device there, then it should work as expected.

HI,

I've checked this settings and I have comunication device selected as
default mic - doesn't work.

2016-09-09 16:09 GMT+02:00 gui… via monorail <
monorail+v2.422849203@chromium.org>:

Thank you for providing more feedback. Adding requester "guidou@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

tornister76@ have you filed a bug at zendesk.com? Just to confirm that they have not changed their web app (as hinted in comment 10)?

tornister76@: ping regarding feedback in #16.

Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919

I have tested this using WebRTC samples on a Windows Laptop and it works as intended.

If getUserMedia is invoked unconstrained and "communications" is the user-preferred device in content settings, communications is used.
If getUserMedia is invoked with explicit constraints to use "communications" as the device, communications is used regardless of what the user-preferred device is.
If getUserMedia is invoked with explicit constraints to use any device that is not "communications", the requested device is used, regardless of the user-preferred device settings.