Yes, I would like to confirm that it is (still) impossible to use only one tcp port for OM. You should also have UDP ports open in your firewall, it is a requirement :(
I even tried to use udptunnel which can operate on tcp port to handle upd flow, but my attempt was unsuccessful too. On Mon, Apr 6, 2020 at 4:42 PM Maxim Solodovnik <solomax...@gmail.com> wrote: > > Hello George, > > Welcome back :) > I'm not sure about "any Video Conferencing systems" > OM 4.0.10 will work almost the same as 2.0.x (it will additionally require > websocket connection on the same port as OM) [will use Flash] > OM 5.0.x CAN work be set up to work over single SSL port but additional > server for TURN will be required :( > > @Yarema, at this ML try to get everything configured via single HTTPS port, > but this seems to be impossible > > On Mon, 6 Apr 2020 at 05:30, Kirkham, George <openmeeti...@goproject.info> > wrote: >> >> Hi, >> >> Background >> >> Reading about Jitsi and BigBlueButton, it seems the underlying software they >> the use required "direct connection to the internet" and exclusive use of >> port 443. >> >> While my infrastructure has a single external IP address, Router that >> changes Internet facing IP address to internal IP address, DMZ via NAT >> firewall which handles UPD, changing IP address to yet another IP address. >> This is a common configuration for small business. >> I also have an Apache Web server which uses both port 80 and port 433. I >> believe while you can redirect port 80 traffic to another server, because >> port 443 traffic is encrypted, it cannot be redirected. The above two >> systems do not use Apache, but do want to have use of port 443. >> >> Reading documentation for Openmeetings which pointed to Kurento Media Server >> documetation: "If Kurento Media Server, its Application Server, or any of >> the clients are located behind a NAT, you need to use a STUN or a TURN >> server in order to achieve NAT traversal." >> >> >> Questions >> >> Is there any Video Conferencing systems that can work from inside a NAT DMZ >> ? Note: I used to use OpenMeeting 2.0 quite effectively inside a NAT DMZ, >> and because it did not require the use of port 443, it ran nicely in our >> environment. >> >> Would OpenMeetings work in Debian 10 (Buster) environment, it did work in >> Debian Squeeze, but a lot of underlying software has been updated since that >> time? >> >> Does OpenMeetings work in a single Docker container? (not that I use >> Docker). I have seen some implementations of the above to systems where part >> of the system is in side Docker but not the WebRTC component. >> >> Any useful thoughts on the above ? >> >> Regards, >> >> George. >> >> >> >> >> >> >> > > > -- > Best regards, > Maxim
