Bogdan Maris, Desktop QA Reporter
	Description • 10 years ago

STR:
1. Start Firefox
2. On computer A remove the webcam.
3. On computer A start a conversation and give link to computer B.

Expected results: Both participants can join the conversation.

Actual results: Only the person from computer B who has a webcam can join the conversation.

Notes:
1. This is reproducible on Firefox 35RC build 2 across platforms.

	u279076
	Comment 1 • 10 years ago

I think this is wontfix for Firefox 35 but we should investigate it for Firefox 36.

Bogdan, can you please provide more details such as debug output?

	Mark Banner (:standard8)
	Comment 2 • 10 years ago

I'm pretty sure this is going to come down to how the sdk manages things. However, I can't test it at the moment.

Bogdan: If you can do the following for logging, it might help us.

1) Open up the page for a room.
2) Go to Tools -> Web Developer -> Web Console
3) In the console, enter the lines:

 localStorage.setItem("debug.dispatcher", true);
 localStorage.setItem("debug.sdk", true);

4) Reload the page
5) Try to start the conversation as per comment 0
6) Capture the output & upload the log.

You can turn off the logging in future pages by:

 localStorage.removeItem("debug.dispatcher");
 localStorage.removeItem("debug.sdk");

	Bogdan Maris, Desktop QA Reporter
	Comment 3 • 10 years ago

Sure thing, this is the logging info:
> "OT.Publisher.onStreamAvailableError NoDevicesFoundError: No voice or video input devices are  available on this machine." sdk.js:910
> "OT.exception :: title: Unable to Publish (1500) msg: Publisher failed to access camera/mic: No voice or video input devices are available on this machine." sdk.js:910
> 1500 "No voice or video input devices are available on this machine." sdk.js:910
> "OT.exception :: title: Unable to Publish (1500) msg: No voice or video input devices are available on this machine." sdk.js:910

	:shell escalante
	Comment 4 • 10 years ago

moving to 38 as we will investigate there and can evaluate what to do based on results.

	Mark Banner (:standard8)
	Comment 5 • 10 years ago

We're fixing this in bug 1106941.