Hi Maxim, Thanks for answering. I performed tests on Chrome and Firefox. And recording works if the firewall is disabled. As you said that the recording is internal to the server, then it is possible that the firewall is blocking something on the localhost. I'll check, because that must be it.
I perform a quick test by going to "Check the Configuration". When it does not work (firewall active), when clicking on "Start Recording" the second counter is not activated, and a webm file with zero bytes is generated. Once again, disabling the firewall, even without restarting the application, Openmeetings performs the recording normally. Thanks again. Ricardo. > Em 18 de abr de 2020, à(s) 22:11, Maxim Solodovnik <solomax...@gmail.com> > escreveu: > > Hello Ricardo, > > such behavior is really weird > Recording is made on server so the main test should be: start your camera or > screen-sharing > Check using different browser or browser tab if your sharing\camera is visible > > Is it works as expected? > > What browser are you using? > > On Sun, 19 Apr 2020 at 02:22, Ricardo Neves <nevs.rica...@gmail.com > <mailto:nevs.rica...@gmail.com>> wrote: > Hello, I'm using Openmeetings 5.0.0-M3 with Centos 7. Everything works fine, > but it doesn't record with the firewall active (it generates zero size webm > files). I've already released all the doors and more: > iptables -A INPUT -p tcp -m tcp --dport 3478 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport 3479 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport 5443 -j ACCEPT > iptables -A INPUT -p tcp -m tcp --dport 8888 -j ACCEPT > iptables -A INPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT > iptables -A INPUT -p udp -m udp --dport 3478 -j ACCEPT > iptables -A INPUT -p udp -m udp --dport 3479 -j ACCEPT > iptables -A OUTPUT -p udp --match multiport --dports 49152: 65535 -j ACCEPT > > If I disable the firewall, recording occurs normally. > Is there a rule missing from my firewall? > Thanks a lot for the help. > Ricardo. > > > -- > Best regards, > Maxim