CefGlue, Cef, and WebRTC - Permission Denied Error

[brian2314245]

So I'm trying to use CefGlue to give me a Chromium control with working WebRTC.

Dmitry over on the Google cefglue forum got me going with "--enable-media-stream" but nothing actually seems to work. Going to apprtc.appspot.com I get the error "Failed to get access to local media. Error code was 1." And over at the OpenTok demo page I get a similar-ish "Permission Denied" from their JS API.

I assume the issue is that in the Chromium browser I would get a pop-up permission dialog allowing me to grant access and here with Cef without that dialog it just fails instead. I may be stupid but I'm not seeing anything that would let me programmatically grant that permissions.

Anyone know what I should do?

[fddima]

Linked original topic https://groups.google.com/forum/#!topic ... nEDCMCafxo .
It has some sensitive information:

Code: Select all

For OpenTok:

[0313/081008:INFO:CONSOLE(23)] "WebSocket message recieved: {"type":1018,"payload":{"payload":{"timestamp":"1363176606726","message":"ping!"}}}", source: http://static.opentok.com/webrtc/v2.0/js/TB.min.js (23)
[0313/081008:ERROR:rtc_video_capture_delegate.cc(88)] NOT IMPLEMENTED
[0313/081008:INFO:CONSOLE(23)] "OT.rtc.Publisher.onStreamAvailableError Permission Denied", source: http://static.opentok.com/webrtc/v2.0/js/TB.min.js (23)

And with apprtc.appspot.com:

[0313/081910:INFO:CONSOLE(165)] "Requested access to local media with mediaConstraints:
  "{"mandatory":{},"optional":[]}"", source: https://apprtc.appspot.com/?r=98616905 (165)
[0313/081910:ERROR:rtc_video_capture_delegate.cc(88)] NOT IMPLEMENTED
[0313/081910:INFO:CONSOLE(311)] "Failed to get access to local media. Error code was 1", source: https://apprtc.appspot.com/?r=98616905 (311)


[magreenblatt]

What CEF3 version/revision are you using? It was most recently fixed in trunk revision 1131.

[brian2314245]

Thanks, I was using R1135 but I just got R1138 and it's working now.

Given that it was so recently not working, should the WebRTC in CEF be regarded as unreliable or do I just need to make sure it hasn't been broken with an update before upgrading the CEF I'm using in my app?

[fddima]

Thanks, I was using R1135 but I just got R1138 and it's working now.

Given that it was so recently not working, should the WebRTC in CEF be regarded as unreliable or do I just need to make sure it hasn't been broken with an update before upgrading the CEF I'm using in my app?

I'm not sure that i'm understand your's question.
CEF 3.1436.1138 - it is '1436' chrome internal version, it changed not with every cef update.
CEF 3.1423.1135 - it is little older chrome version.
both of them match to some versions of chrome from development branches.
So anything can be broken in future, and testing required features - is not bad idea.

[magreenblatt]

Thanks, I was using R1135 but I just got R1138 and it's working now.

Given that it was so recently not working, should the WebRTC in CEF be regarded as unreliable or do I just need to make sure it hasn't been broken with an update before upgrading the CEF I'm using in my app?

Testing is always a good idea. You're using trunk which is an unstable development branch. Also, CEF contains no automated WebRTC tests so it's possible we won't notice when it breaks (feel free to report any problems that you notice). This is also why WebRTC is behind a feature flag instead of enabled by default.

[brian2314245]

Off topic, but is there a way to control which camera is used for WebRTC? I see nothing in a real Chrome browser, nothing in any WebRTC JS libraries, and find nothing relevant in Googling. I have to believe there's a way to do it.