Yeah the main information in your list that would be needed is: What browser version are you using? What operating system (and version) is the browser being executed?
Between 6.0.0 and 6.2.0 there are hardly any changes to the way the client side code works. Thanks Seb Sebastian Wagner Director Arrakeen Solutions, OM-Hosting.com http://arrakeen-solutions.co.nz/ https://om-hosting.com - Cloud & Server Hosting for HTML5 Video-Conferencing OpenMeetings <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> On Wed, 16 Feb 2022 at 03:55, Maxim Solodovnik <solomax...@gmail.com> wrote: > According to this page > https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection > > This web API should available since FF44 > > so I see 2 options here: > 1) extremely old FF > 2) some add-on/security setting disabling WebRTC > > > from mobile (sorry for typos ;) > > > On Tue, Feb 15, 2022, 20:55 SanKet Parte <sanketpart...@gmail.com> wrote: > >> Hi, >> >> I am facing one issue in *openmeetings version min-6.0.0* i.e In room >> audio and video are not working in windows mozilla firefox browser But it >> is working fine in Chrome and MS Edge browser. >> >> Getting ReferenceError: *RTCPeerConnection is not defined* in the >> firefox browser when I try to turn on the audio or video. >> *Please find the attached screenshots for the details* >> >> Below are the details of system and software used: >> >> OS: Ubuntu 20.04.3 LTS >> >> Docker version: 20.10.12 >> >> Openmeetings docker image: *apache/openmeetings:min-6.0.0* >> >> Kurento media server docker image: *kurento/kurento-media-server:6.13* >> >> >> Please help me with this issue. >> >> >> >> *Thanks & Regards,* >> >> *Sanket Parte* >> >> Associate Software Engineer >> >> Paramatrix Technologies Private Limited >> >
