Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

video-chat: firefox : chrome #968

Closed
maxlinux2000 opened this issue Oct 2, 2015 · 7 comments
Closed

video-chat: firefox : chrome #968

maxlinux2000 opened this issue Oct 2, 2015 · 7 comments

Comments

@maxlinux2000
Copy link

Now Firefox and chrome under ubuntu 14.04 can't use the micro and the camera.

Under Android 5 + chrome, it's works fine.

@Sing-Li
Copy link
Member

Sing-Li commented Oct 2, 2015

@maxlinux2000 it has A LOT to do with your system hardware and not just the browser versions.

Please check with this link - if your browser + hardware stack works here , it will work:

https://test.webrtc.org/

@Sing-Li Sing-Li closed this as completed Oct 2, 2015
@maxlinux2000
Copy link
Author

xrocket2

ok, firefox works fine.

I just tried too:
https://www.webrtc-experiment.com/RTCMultiConnection/AppRTC-Look.html

from my desktop (ubuntu with firefox) and my phone (android 5 with chrome), ando works just fine

@maxlinux2000
Copy link
Author

OK, I undestand the problem under firefox.
Pressin the Video_chat button, don't appear the message to share the mic & camera, so the video char can't be start.
In the Console I can reat this:

InvalidAccessError: RTCPeerConnection constructor passed invalid RTCConfiguration - missing username: turn:team%40rocket.chat@numb.viagenie.ca:3478 rocketchat_webrtc.js

@geekgonecrazy
Copy link
Contributor

@maxlinux2000 did firefox ask you to share these?

@Sing-Li
Copy link
Member

Sing-Li commented Oct 2, 2015

@maxlinux2000 the screenshot you showed indicates that browser+system is not compatible with webrtc in general. You need all check marks for full compatibility.

@geekgonecrazy
Copy link
Contributor

@Sing-Li ah.. weird that it'd have one resolution but fail completely. But makes sense why it doesn't work then. We do need to be super clear to them when their browser isn't compatible. We need to catch those errors.

@Sing-Li
Copy link
Member

Sing-Li commented Oct 3, 2015

Once the new stack lands in master and is working for most folks. We'll party and tune/tweak. Yes it is likely possible that we can 'query' in such a way to support these edge cases. And also improve the UX when browsers are not compatible ( for example - don't show the button)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants