I’m not quite sure how it would be a driver issue if it works fine with other run of the mill video conferencing software? I’m not a hardware engineer but, drivers are usually an all or none kinda deal.
What do you mean by that? With one command you can install and use it. I’m doing it on DO on regular basis to test some stuff, and it takes around 3-4 minutes to have it running, where most of the time I’m waiting for the VM to be created and started.
For meet.jit.si we use AWS.
So it doesn’t work with Chrome, it doesn’t work with Firefox. It doesn’t work with meet.jit.si, it doesn’t work with appr.tc. These are four different software, the only point where all meet is the OS and the camera drivers.
So my point is that if it doesn’t work with the two major browsers and appr.tc which is google’s webrtc test app, I doubt we can do anything to make it work.
So I tried going to test.webrtc.org, I’m failing a few of the camera settings in both browsers and intermittently on microphone. I’m going to investigate those issues along with installing a test.webrtc server locally and test as well. I will follow up once that’s done, I appreciate all the help so far.
Turn Key Solution meaning a full on webrtc video conferencing solution ready for use in a corporate environment (I know it supports authentication but that needs to be configured after the fact).