search

puavo-org / puavo-os

Puavo OS is an disk image based operating system that is built from Debian GNU/Linux and is specifically designed for learning.
https://puavo.org
GNU General Public License v2.0
13 stars 7 forks source link

WebRTC does not work with Web Browsers in Puavo #730

Open ralf-krause opened 1 month ago

ralf-krause commented 1 month ago

There are a lot of schools which are using learning platforms like Moodle. In this learning platforms you can do you work as a text file or as a graphical document. But sometimes you can also send your work as an audio or a video statement.

To make it easy for the students to record these audio or video statements on the fly the platforms are using WebRTC. By example I set up a forum and I took different personal devices to post audio into this forum. You can see the result on https://bildungsportal.magdeburg.de/moodle2/mod/forum/view.php?id=527 (sorry, the texts and the audios are in german language). As you can see in the thread "Audio aufnehmen mit Puavo Bonna (Bullseye)" the audio recording does not work in first four posts. https://bildungsportal.magdeburg.de/moodle2/mod/forum/discuss.php?d=23

All other devices are working ... but Puavo does not.

I must setup the browsers for activating WebRTC. In Firefox I must set the parameter media.peerconnection.enabled = false. In Chromium and in Chrome I need to install an extension "WebRTC Network Limiter". It would be useful for schools to activate WebRTC for Puavo devices by default or by PuavoConfig.

Mazhoon commented 1 month ago

Testing Single audio stream from https://webrtc.github.io/test-pages/ on Firefox 127.0 and Chrome 126.0.6478.61, on Bullseye O2425 Bonna, I can hear the captured audio in test (after ensuring that my microphone is not muted, and giving the page mic capture permission when it prompts), without changing any parameters in Firefox's about:config or installing any Chrome extensions.

Judging from the config parameter & description of the Chrome extension, your issue is probably related to some properties of the network the device is in (DNS? Firewall?), and not actually WebRTC support.