Re: OpenMeetings
Hello, please do not write personal emails, write to the list instead I only can test using my old Sony Xperia phone OM works as expected in Google Chrome what browser is being used by your users? On Thu, 12 Mar 2020 at 17:44, TaHa.Net wrote: > > Greetings and Regards > I used OpenMeetings 5.0.0-M3 (with tomcat) and thank you very much for your > good platform > > The problem I have is that : audio and video are not transmitted when users > are connected by mobile phones. > > When they arrive in Rome it gives the following Errors: > > openmeetings typeError: c is undefined > or > openmeetings unable to get list of multimedia devices > > Is there software for Android phones so they can use the classes? > Or how can this be fixed? > > Next version (5.0.0-M4) when will it be published? > thanks for your help -- WBR Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
Hello Yarema, I'm afraid you need to set-up turn server "visible to KMS" Which means 1) your KMS port should be opened OR 2) TURN server should be on the same server as KMS and TURN ports should be opened 3*) (I'm not nginx expert) maybe you can proxy TURN requests/responses, I'm not aware on such option ... On Fri, 13 Mar 2020 at 07:10, YUP wrote: > > Hello all, > Could someone help me with configuration of my OM setup? Any help will > be greatly appreciated. > I have a server which is for several reasons behind NAT, only 443 port > is open. There is sslh balancer, which redirect external traffic to > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > installed in container behind nginx proxy and works well, except audio > and video. When I perform setup check after logged in (video camera > and microphone) I can see myself in camera and can also see increasing > and decreasing green line, which indicate microphone level, but I > can't save and replay the testing record. As far I understand the > problem is in NAT, so I had to use kurento server with TURN server. I > did that by adding the environment variables for kurento server in > docker container with the corresponding data for turn.anyfirewall.com: > > - KMS_STUN_IP=130.211.143.110 > - KMS_STUN_PORT=443 > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > and the same for openmeetings docker container: > > - TURN_USER=webrtc > - TURN_PASS=webrtc > - TURN_URL=130.211.143.110:443?transport=tcp > > After restarting it allowed me immediately to perform network test > (except ip ping), but not resolved the issue with camera and > microphone. > When I connect to OM server with help of vpn (so I and OM server are > in the same network) everything works as needed. I can save and replay > video, I can hear myself, two OM users connected by vpn to OM server > can talk to each other, etc. But it is not an option use vpn > connection... > I spent two days to find what I did wrong. I tried another TURN and > STUN servers, different type of configurations and so on, nothing > helped. > > Regards, > Yarema -- WBR Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
It seems to me that I found what is happening. Firewall blocks all non http requests out to all ports except 443, 80, 8080 and 22. That is why I don't have connection to outside turn ans stun servers. Is it possible to connect to those server in such conditions? Tunnels? On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > Hello all, > Could someone help me with configuration of my OM setup? Any help will > be greatly appreciated. > I have a server which is for several reasons behind NAT, only 443 port > is open. There is sslh balancer, which redirect external traffic to > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > installed in container behind nginx proxy and works well, except audio > and video. When I perform setup check after logged in (video camera > and microphone) I can see myself in camera and can also see increasing > and decreasing green line, which indicate microphone level, but I > can't save and replay the testing record. As far I understand the > problem is in NAT, so I had to use kurento server with TURN server. I > did that by adding the environment variables for kurento server in > docker container with the corresponding data for turn.anyfirewall.com: > > - KMS_STUN_IP=130.211.143.110 > - KMS_STUN_PORT=443 > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > and the same for openmeetings docker container: > > - TURN_USER=webrtc > - TURN_PASS=webrtc > - TURN_URL=130.211.143.110:443?transport=tcp > > After restarting it allowed me immediately to perform network test > (except ip ping), but not resolved the issue with camera and > microphone. > When I connect to OM server with help of vpn (so I and OM server are > in the same network) everything works as needed. I can save and replay > video, I can hear myself, two OM users connected by vpn to OM server > can talk to each other, etc. But it is not an option use vpn > connection... > I spent two days to find what I did wrong. I tried another TURN and > STUN servers, different type of configurations and so on, nothing > helped. > > Regards, > Yarema
Re: another question about clustering
Hello Peter, sorry for the late reply I'm using this config for my tests: https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/webapp/WEB-INF/classes/hazelcast.xml line 61: make instance-name UNIQUE (I'm using server-1, server-2 etc.) line 64: enable multicast line 69 uncomment, set-up ports interfaces This config for your server nodes Your clients will use UI On Fri, 13 Mar 2020 at 20:26, Peter Dähn wrote: > > Hi Maxim, > > do I need to do something like that > (https://docs.hazelcast.org/docs/3.0/manual/html/ch12s02.html#IPv6) > > > ... > > 5701 > > > FF02:0:0:0:0:0:0:1 > 54327 > > > [fe80::223:6cff:fe93:7c7e]:5701 > 192.168.1.0-7 > 192.168.1.* > fe80:0:0:0:45c5:47ee:fe15:493a > > > > 10.3.16.* > 10.3.10.4-18 > fe80:0:0:0:45c5:47ee:fe15:* > fe80::223:6cff:fe93:0- > > ... > > > to enable IPv6 support in addition? Clients usually have both addresses but > some of them just IPv4 or IPv6 only. > > Greetings Peter > > > -- WBR Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
Maybe you can set up KMS to use 8080? TURN requires more open port to handle "totally closed" networks ... On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > It seems to me that I found what is happening. Firewall blocks all non > http requests out to all ports except 443, 80, 8080 and 22. That is > why I don't have connection to outside turn ans stun servers. Is it > possible to connect to those server in such conditions? Tunnels? > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > Hello all, > > Could someone help me with configuration of my OM setup? Any help will > > be greatly appreciated. > > I have a server which is for several reasons behind NAT, only 443 port > > is open. There is sslh balancer, which redirect external traffic to > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > > installed in container behind nginx proxy and works well, except audio > > and video. When I perform setup check after logged in (video camera > > and microphone) I can see myself in camera and can also see increasing > > and decreasing green line, which indicate microphone level, but I > > can't save and replay the testing record. As far I understand the > > problem is in NAT, so I had to use kurento server with TURN server. I > > did that by adding the environment variables for kurento server in > > docker container with the corresponding data for turn.anyfirewall.com: > > > > - KMS_STUN_IP=130.211.143.110 > > - KMS_STUN_PORT=443 > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > and the same for openmeetings docker container: > > > > - TURN_USER=webrtc > > - TURN_PASS=webrtc > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > After restarting it allowed me immediately to perform network test > > (except ip ping), but not resolved the issue with camera and > > microphone. > > When I connect to OM server with help of vpn (so I and OM server are > > in the same network) everything works as needed. I can save and replay > > video, I can hear myself, two OM users connected by vpn to OM server > > can talk to each other, etc. But it is not an option use vpn > > connection... > > I spent two days to find what I did wrong. I tried another TURN and > > STUN servers, different type of configurations and so on, nothing > > helped. > > > > Regards, > > Yarema -- WBR Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
It nothing changes, only 443 is open to the world. On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik wrote: > > Maybe you can set up KMS to use 8080? > TURN requires more open port to handle "totally closed" networks ... > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > It seems to me that I found what is happening. Firewall blocks all non > > http requests out to all ports except 443, 80, 8080 and 22. That is > > why I don't have connection to outside turn ans stun servers. Is it > > possible to connect to those server in such conditions? Tunnels? > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > Hello all, > > > Could someone help me with configuration of my OM setup? Any help will > > > be greatly appreciated. > > > I have a server which is for several reasons behind NAT, only 443 port > > > is open. There is sslh balancer, which redirect external traffic to > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > > > installed in container behind nginx proxy and works well, except audio > > > and video. When I perform setup check after logged in (video camera > > > and microphone) I can see myself in camera and can also see increasing > > > and decreasing green line, which indicate microphone level, but I > > > can't save and replay the testing record. As far I understand the > > > problem is in NAT, so I had to use kurento server with TURN server. I > > > did that by adding the environment variables for kurento server in > > > docker container with the corresponding data for turn.anyfirewall.com: > > > > > > - KMS_STUN_IP=130.211.143.110 > > > - KMS_STUN_PORT=443 > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > and the same for openmeetings docker container: > > > > > > - TURN_USER=webrtc > > > - TURN_PASS=webrtc > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > After restarting it allowed me immediately to perform network test > > > (except ip ping), but not resolved the issue with camera and > > > microphone. > > > When I connect to OM server with help of vpn (so I and OM server are > > > in the same network) everything works as needed. I can save and replay > > > video, I can hear myself, two OM users connected by vpn to OM server > > > can talk to each other, etc. But it is not an option use vpn > > > connection... > > > I spent two days to find what I did wrong. I tried another TURN and > > > STUN servers, different type of configurations and so on, nothing > > > helped. > > > > > > Regards, > > > Yarema > > > > -- > WBR > Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
It seems I misread your previous email "all ports except 443, 80, 8080 and 22." I'm afraid you need more open ports ... I'm not sure but I would investigate if KMS/TURN URLs can be set up for context i.e. yourserver:4278/turn, yourserver:/kms in this case you can proxy them On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > It nothing changes, only 443 is open to the world. > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik wrote: > > > > Maybe you can set up KMS to use 8080? > > TURN requires more open port to handle "totally closed" networks ... > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > It seems to me that I found what is happening. Firewall blocks all non > > > http requests out to all ports except 443, 80, 8080 and 22. That is > > > why I don't have connection to outside turn ans stun servers. Is it > > > possible to connect to those server in such conditions? Tunnels? > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > Hello all, > > > > Could someone help me with configuration of my OM setup? Any help will > > > > be greatly appreciated. > > > > I have a server which is for several reasons behind NAT, only 443 port > > > > is open. There is sslh balancer, which redirect external traffic to > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > > > > installed in container behind nginx proxy and works well, except audio > > > > and video. When I perform setup check after logged in (video camera > > > > and microphone) I can see myself in camera and can also see increasing > > > > and decreasing green line, which indicate microphone level, but I > > > > can't save and replay the testing record. As far I understand the > > > > problem is in NAT, so I had to use kurento server with TURN server. I > > > > did that by adding the environment variables for kurento server in > > > > docker container with the corresponding data for turn.anyfirewall.com: > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > - KMS_STUN_PORT=443 > > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > and the same for openmeetings docker container: > > > > > > > > - TURN_USER=webrtc > > > > - TURN_PASS=webrtc > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > After restarting it allowed me immediately to perform network test > > > > (except ip ping), but not resolved the issue with camera and > > > > microphone. > > > > When I connect to OM server with help of vpn (so I and OM server are > > > > in the same network) everything works as needed. I can save and replay > > > > video, I can hear myself, two OM users connected by vpn to OM server > > > > can talk to each other, etc. But it is not an option use vpn > > > > connection... > > > > I spent two days to find what I did wrong. I tried another TURN and > > > > STUN servers, different type of configurations and so on, nothing > > > > helped. > > > > > > > > Regards, > > > > Yarema > > > > > > > > -- > > WBR > > Maxim aka solomax -- WBR Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
Can we just proxify kurento websocket? Something like this https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik wrote: > > It seems I misread your previous email "all ports except 443, 80, 8080 and > 22." > I'm afraid you need more open ports ... > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > for context i.e. > yourserver:4278/turn, yourserver:/kms in this case you can proxy them > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > It nothing changes, only 443 is open to the world. > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > wrote: > > > > > > Maybe you can set up KMS to use 8080? > > > TURN requires more open port to handle "totally closed" networks ... > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > It seems to me that I found what is happening. Firewall blocks all non > > > > http requests out to all ports except 443, 80, 8080 and 22. That is > > > > why I don't have connection to outside turn ans stun servers. Is it > > > > possible to connect to those server in such conditions? Tunnels? > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > > > Hello all, > > > > > Could someone help me with configuration of my OM setup? Any help will > > > > > be greatly appreciated. > > > > > I have a server which is for several reasons behind NAT, only 443 port > > > > > is open. There is sslh balancer, which redirect external traffic to > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 minimal > > > > > installed in container behind nginx proxy and works well, except audio > > > > > and video. When I perform setup check after logged in (video camera > > > > > and microphone) I can see myself in camera and can also see increasing > > > > > and decreasing green line, which indicate microphone level, but I > > > > > can't save and replay the testing record. As far I understand the > > > > > problem is in NAT, so I had to use kurento server with TURN server. I > > > > > did that by adding the environment variables for kurento server in > > > > > docker container with the corresponding data for turn.anyfirewall.com: > > > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > > - KMS_STUN_PORT=443 > > > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > > and the same for openmeetings docker container: > > > > > > > > > > - TURN_USER=webrtc > > > > > - TURN_PASS=webrtc > > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > > > After restarting it allowed me immediately to perform network test > > > > > (except ip ping), but not resolved the issue with camera and > > > > > microphone. > > > > > When I connect to OM server with help of vpn (so I and OM server are > > > > > in the same network) everything works as needed. I can save and replay > > > > > video, I can hear myself, two OM users connected by vpn to OM server > > > > > can talk to each other, etc. But it is not an option use vpn > > > > > connection... > > > > > I spent two days to find what I did wrong. I tried another TURN and > > > > > STUN servers, different type of configurations and so on, nothing > > > > > helped. > > > > > > > > > > Regards, > > > > > Yarema > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > -- > WBR > Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
Just to inform you, I made proxified kurento websocket in nginx and I can connect to it: $ wscat -n --connect https://external_server_ip_address/kurento (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version. Connected (press CTRL+C to quit) > I set - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento but got o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create Kurento client, will re-try in 1 ms On Sun, Mar 15, 2020 at 8:56 AM YUP wrote: > > Can we just proxify kurento websocket? Something like this > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik wrote: > > > > It seems I misread your previous email "all ports except 443, 80, 8080 and > > 22." > > I'm afraid you need more open ports ... > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > > for context i.e. > > yourserver:4278/turn, yourserver:/kms in this case you can proxy them > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > > > It nothing changes, only 443 is open to the world. > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > > wrote: > > > > > > > > Maybe you can set up KMS to use 8080? > > > > TURN requires more open port to handle "totally closed" networks ... > > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > > > It seems to me that I found what is happening. Firewall blocks all non > > > > > http requests out to all ports except 443, 80, 8080 and 22. That is > > > > > why I don't have connection to outside turn ans stun servers. Is it > > > > > possible to connect to those server in such conditions? Tunnels? > > > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > > > > > Hello all, > > > > > > Could someone help me with configuration of my OM setup? Any help > > > > > > will > > > > > > be greatly appreciated. > > > > > > I have a server which is for several reasons behind NAT, only 443 > > > > > > port > > > > > > is open. There is sslh balancer, which redirect external traffic to > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 > > > > > > minimal > > > > > > installed in container behind nginx proxy and works well, except > > > > > > audio > > > > > > and video. When I perform setup check after logged in (video camera > > > > > > and microphone) I can see myself in camera and can also see > > > > > > increasing > > > > > > and decreasing green line, which indicate microphone level, but I > > > > > > can't save and replay the testing record. As far I understand the > > > > > > problem is in NAT, so I had to use kurento server with TURN server. > > > > > > I > > > > > > did that by adding the environment variables for kurento server in > > > > > > docker container with the corresponding data for > > > > > > turn.anyfirewall.com: > > > > > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > > > - KMS_STUN_PORT=443 > > > > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > > > and the same for openmeetings docker container: > > > > > > > > > > > > - TURN_USER=webrtc > > > > > > - TURN_PASS=webrtc > > > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > > > > > After restarting it allowed me immediately to perform network test > > > > > > (except ip ping), but not resolved the issue with camera and > > > > > > microphone. > > > > > > When I connect to OM server with help of vpn (so I and OM server are > > > > > > in the same network) everything works as needed. I can save and > > > > > > replay > > > > > > video, I can hear myself, two OM users connected by vpn to OM server > > > > > > can talk to each other, etc. But it is not an option use vpn > > > > > > connection... > > > > > > I spent two days to find what I did wrong. I tried another TURN and > > > > > > STUN servers, different type of configurations and so on, nothing > > > > > > helped. > > > > > > > > > > > > Regards, > > > > > > Yarema > > > > > > > > > > > > > > > > -- > > > > WBR > > > > Maxim aka solomax > > > > > > > > -- > > WBR > > Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
Server has self-signed certificate, can it be a reason? On Sun, Mar 15, 2020 at 9:38 AM YUP wrote: > > Just to inform you, I made proxified kurento websocket in nginx and I > can connect to it: > $ wscat -n --connect https://external_server_ip_address/kurento > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName > to an IP address is not permitted by RFC 6066. This will be ignored in > a future version. > Connected (press CTRL+C to quit) > > > > I set > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento > but got > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create > Kurento client, will re-try in 1 ms > > > > On Sun, Mar 15, 2020 at 8:56 AM YUP wrote: > > > > Can we just proxify kurento websocket? Something like this > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik > > wrote: > > > > > > It seems I misread your previous email "all ports except 443, 80, 8080 > > > and 22." > > > I'm afraid you need more open ports ... > > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > > > for context i.e. > > > yourserver:4278/turn, yourserver:/kms in this case you can proxy them > > > > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > > > > > It nothing changes, only 443 is open to the world. > > > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > > > wrote: > > > > > > > > > > Maybe you can set up KMS to use 8080? > > > > > TURN requires more open port to handle "totally closed" networks ... > > > > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > > > > > It seems to me that I found what is happening. Firewall blocks all > > > > > > non > > > > > > http requests out to all ports except 443, 80, 8080 and 22. That is > > > > > > why I don't have connection to outside turn ans stun servers. Is it > > > > > > possible to connect to those server in such conditions? Tunnels? > > > > > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > > > > > > > Hello all, > > > > > > > Could someone help me with configuration of my OM setup? Any help > > > > > > > will > > > > > > > be greatly appreciated. > > > > > > > I have a server which is for several reasons behind NAT, only 443 > > > > > > > port > > > > > > > is open. There is sslh balancer, which redirect external traffic > > > > > > > to > > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 > > > > > > > minimal > > > > > > > installed in container behind nginx proxy and works well, except > > > > > > > audio > > > > > > > and video. When I perform setup check after logged in (video > > > > > > > camera > > > > > > > and microphone) I can see myself in camera and can also see > > > > > > > increasing > > > > > > > and decreasing green line, which indicate microphone level, but I > > > > > > > can't save and replay the testing record. As far I understand the > > > > > > > problem is in NAT, so I had to use kurento server with TURN > > > > > > > server. I > > > > > > > did that by adding the environment variables for kurento server in > > > > > > > docker container with the corresponding data for > > > > > > > turn.anyfirewall.com: > > > > > > > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > > > > - KMS_STUN_PORT=443 > > > > > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > > > > and the same for openmeetings docker container: > > > > > > > > > > > > > > - TURN_USER=webrtc > > > > > > > - TURN_PASS=webrtc > > > > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > > > > > > > After restarting it allowed me immediately to perform network test > > > > > > > (except ip ping), but not resolved the issue with camera and > > > > > > > microphone. > > > > > > > When I connect to OM server with help of vpn (so I and OM server > > > > > > > are > > > > > > > in the same network) everything works as needed. I can save and > > > > > > > replay > > > > > > > video, I can hear myself, two OM users connected by vpn to OM > > > > > > > server > > > > > > > can talk to each other, etc. But it is not an option use vpn > > > > > > > connection... > > > > > > > I spent two days to find what I did wrong. I tried another TURN > > > > > > > and > > > > > > > STUN servers, different type of configurations and so on, nothing > > > > > > > helped. > > > > > > > > > > > > > > Regards, > > > > > > > Yarema > > > > > > > > > > > > > > > > > > > > -- > > > > > WBR > > > > > Maxim aka solomax > > > > > > > > > > > > -- > > > WBR > > > Maxim aka solomax
Re: Openmeetings, kurento and TURN behind NAT
No, it is not a reason, checked. On Sun, Mar 15, 2020 at 10:10 AM YUP wrote: > > Server has self-signed certificate, can it be a reason? > > On Sun, Mar 15, 2020 at 9:38 AM YUP wrote: > > > > Just to inform you, I made proxified kurento websocket in nginx and I > > can connect to it: > > $ wscat -n --connect https://external_server_ip_address/kurento > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName > > to an IP address is not permitted by RFC 6066. This will be ignored in > > a future version. > > Connected (press CTRL+C to quit) > > > > > > > I set > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento > > but got > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create > > Kurento client, will re-try in 1 ms > > > > > > > > On Sun, Mar 15, 2020 at 8:56 AM YUP wrote: > > > > > > Can we just proxify kurento websocket? Something like this > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? > > > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik > > > wrote: > > > > > > > > It seems I misread your previous email "all ports except 443, 80, 8080 > > > > and 22." > > > > I'm afraid you need more open ports ... > > > > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > > > > for context i.e. > > > > yourserver:4278/turn, yourserver:/kms in this case you can proxy > > > > them > > > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > > > > > > > It nothing changes, only 443 is open to the world. > > > > > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > > > > wrote: > > > > > > > > > > > > Maybe you can set up KMS to use 8080? > > > > > > TURN requires more open port to handle "totally closed" networks ... > > > > > > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > > > > > > > It seems to me that I found what is happening. Firewall blocks > > > > > > > all non > > > > > > > http requests out to all ports except 443, 80, 8080 and 22. That > > > > > > > is > > > > > > > why I don't have connection to outside turn ans stun servers. Is > > > > > > > it > > > > > > > possible to connect to those server in such conditions? Tunnels? > > > > > > > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > > > > > > > > > Hello all, > > > > > > > > Could someone help me with configuration of my OM setup? Any > > > > > > > > help will > > > > > > > > be greatly appreciated. > > > > > > > > I have a server which is for several reasons behind NAT, only > > > > > > > > 443 port > > > > > > > > is open. There is sslh balancer, which redirect external > > > > > > > > traffic to > > > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 > > > > > > > > minimal > > > > > > > > installed in container behind nginx proxy and works well, > > > > > > > > except audio > > > > > > > > and video. When I perform setup check after logged in (video > > > > > > > > camera > > > > > > > > and microphone) I can see myself in camera and can also see > > > > > > > > increasing > > > > > > > > and decreasing green line, which indicate microphone level, but > > > > > > > > I > > > > > > > > can't save and replay the testing record. As far I understand > > > > > > > > the > > > > > > > > problem is in NAT, so I had to use kurento server with TURN > > > > > > > > server. I > > > > > > > > did that by adding the environment variables for kurento server > > > > > > > > in > > > > > > > > docker container with the corresponding data for > > > > > > > > turn.anyfirewall.com: > > > > > > > > > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > > > > > - KMS_STUN_PORT=443 > > > > > > > > - KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > > > > > and the same for openmeetings docker container: > > > > > > > > > > > > > > > > - TURN_USER=webrtc > > > > > > > > - TURN_PASS=webrtc > > > > > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > > > > > > > > > After restarting it allowed me immediately to perform network > > > > > > > > test > > > > > > > > (except ip ping), but not resolved the issue with camera and > > > > > > > > microphone. > > > > > > > > When I connect to OM server with help of vpn (so I and OM > > > > > > > > server are > > > > > > > > in the same network) everything works as needed. I can save and > > > > > > > > replay > > > > > > > > video, I can hear myself, two OM users connected by vpn to OM > > > > > > > > server > > > > > > > > can talk to each other, etc. But it is not an option use vpn > > > > > > > > connection... > > > > > > > > I spent two days to find what I did wrong. I tried another TURN > > > > > > > > and > > > > > > > > STUN servers, different type of configurations and so on, > > > > > > > > nothing > > > > > > > > helped. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Yarema > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > WBR >
Deploying Openmeeting 5 on Centos7
Hi, I'm deploying Openmeetings on a CentOS7 VM in proxmoxVE. I follow the "Installation OpenMeetings 5.0.0-M3 on Centos 7.pdf" document. I'm stalled at te step opening the browser on https://localhost:5443/openmeetings/ as the answer is "HTTP404 not found" I do not know tomcat at all, I've just changed the starting setup with export CATALINA_OPTS="-Djava.net.preferIPV4Stack=true" to make tomcat listening on IPV4 adresses and "netstat -a" show it is ok. Any help appreciated and advices to make openmeeting listening on port 80 or 443 to finalize the setup. Patrick
Cleanslide API call - meaning of slide
Hi Maxim,
Can you clarify what is meant by slide and how can identify
slide numbers ?
cleanSlide
@GET
@Path("/cleanslide/{roomid}/{wbid}/{slide}") publicServiceResult
cleanSlide(@QueryParam("sid")String
sid,
@PathParam("roomid") long roomId, @PathParam("wbid") long wbId,
@PathParam("slide") int slide)
This method will do the same as clean slide in the room (except for
there will be no UNDO)
Parameters:
|sid|- - The SID of the User. This SID must be marked as Loggedin
|roomId|- - id of the room to clean
|wbId|- - id of the white board to clean
*|slide|- - slide number (zero based)*
Returns:
- serviceResult object with the result
Thanks,
Dan
Re: Openmeetings, kurento and TURN behind NAT
I was able to connect to kurento websocket which is proxified by nginx, the solution was very simple, put wss instead of https, probably for some reasons openmeetings needs to have ws or wss in the input url: - OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento But it is not solved the issue with recording audio/video in test and different users. On Sun, Mar 15, 2020 at 10:16 AM YUP wrote: > > No, it is not a reason, checked. > > On Sun, Mar 15, 2020 at 10:10 AM YUP wrote: > > > > Server has self-signed certificate, can it be a reason? > > > > On Sun, Mar 15, 2020 at 9:38 AM YUP wrote: > > > > > > Just to inform you, I made proxified kurento websocket in nginx and I > > > can connect to it: > > > $ wscat -n --connect https://external_server_ip_address/kurento > > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName > > > to an IP address is not permitted by RFC 6066. This will be ignored in > > > a future version. > > > Connected (press CTRL+C to quit) > > > > > > > > > > I set > > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento > > > but got > > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create > > > Kurento client, will re-try in 1 ms > > > > > > > > > > > > On Sun, Mar 15, 2020 at 8:56 AM YUP wrote: > > > > > > > > Can we just proxify kurento websocket? Something like this > > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? > > > > > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik > > > > wrote: > > > > > > > > > > It seems I misread your previous email "all ports except 443, 80, > > > > > 8080 and 22." > > > > > I'm afraid you need more open ports ... > > > > > > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > > > > > for context i.e. > > > > > yourserver:4278/turn, yourserver:/kms in this case you can proxy > > > > > them > > > > > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > > > > > > > > > It nothing changes, only 443 is open to the world. > > > > > > > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > > > > > wrote: > > > > > > > > > > > > > > Maybe you can set up KMS to use 8080? > > > > > > > TURN requires more open port to handle "totally closed" networks > > > > > > > ... > > > > > > > > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > > > > > > > > > It seems to me that I found what is happening. Firewall blocks > > > > > > > > all non > > > > > > > > http requests out to all ports except 443, 80, 8080 and 22. > > > > > > > > That is > > > > > > > > why I don't have connection to outside turn ans stun servers. > > > > > > > > Is it > > > > > > > > possible to connect to those server in such conditions? Tunnels? > > > > > > > > > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP wrote: > > > > > > > > > > > > > > > > > > Hello all, > > > > > > > > > Could someone help me with configuration of my OM setup? Any > > > > > > > > > help will > > > > > > > > > be greatly appreciated. > > > > > > > > > I have a server which is for several reasons behind NAT, only > > > > > > > > > 443 port > > > > > > > > > is open. There is sslh balancer, which redirect external > > > > > > > > > traffic to > > > > > > > > > different targets: nginx, openvpn, etc. Openmeetings 5.0.0-M3 > > > > > > > > > minimal > > > > > > > > > installed in container behind nginx proxy and works well, > > > > > > > > > except audio > > > > > > > > > and video. When I perform setup check after logged in (video > > > > > > > > > camera > > > > > > > > > and microphone) I can see myself in camera and can also see > > > > > > > > > increasing > > > > > > > > > and decreasing green line, which indicate microphone level, > > > > > > > > > but I > > > > > > > > > can't save and replay the testing record. As far I understand > > > > > > > > > the > > > > > > > > > problem is in NAT, so I had to use kurento server with TURN > > > > > > > > > server. I > > > > > > > > > did that by adding the environment variables for kurento > > > > > > > > > server in > > > > > > > > > docker container with the corresponding data for > > > > > > > > > turn.anyfirewall.com: > > > > > > > > > > > > > > > > > > - KMS_STUN_IP=130.211.143.110 > > > > > > > > > - KMS_STUN_PORT=443 > > > > > > > > > - > > > > > > > > > KMS_TURN_URL=webrtc:webrtc@130.211.143.110:443?transport=tcp > > > > > > > > > and the same for openmeetings docker container: > > > > > > > > > > > > > > > > > > - TURN_USER=webrtc > > > > > > > > > - TURN_PASS=webrtc > > > > > > > > > - TURN_URL=130.211.143.110:443?transport=tcp > > > > > > > > > > > > > > > > > > After restarting it allowed me immediately to perform network > > > > > > > > > test > > > > > > > > > (except ip ping), but not resolved the issue with camera and > > > > > > > > > microphone. > > > > > > > > > When I connect to OM server with help of vpn (so I and OM > > > > > > > > > server are > > > > > > > > > i
Re: Cleanslide API call - meaning of slide
Hello Daniel,
This function is useful when multipaged document is loaded to wb
In this case you can clean each slide/page and not affect other work
Another difference from cleanWb: document on wb is not affected
On Mon, Mar 16, 2020, 00:36 Daniel Baker
wrote:
> Hi Maxim,
>
>
> Can you clarify what is meant by slide and how can identify slide
> numbers ?
>
>
>
> cleanSlide
>
> @GET
> @Path("/cleanslide/{roomid}/{wbid}/{slide}") public ServiceResult
>
> cleanSlide(@QueryParam("sid") String
>
> sid,
> @PathParam("roomid") long roomId, @PathParam("wbid") long wbId,
> @PathParam("slide") int slide)
>
> This method will do the same as clean slide in the room (except for there
> will be no UNDO)
> Parameters: sid - - The SID of the User. This SID must be marked as
> Loggedin roomId - - id of the room to clean wbId - - id of the white
> board to clean *slide* *- - slide number (zero based)* Returns: -
> serviceResult object with the result
>
>
> Thanks,
>
>
> Dan
>
Re: Openmeetings, kurento and TURN behind NAT
Maxim, I was also managed to install coturn on external server which listen on port 443. Kurento connects to this port (via TURN_URL, TURN_USER,TURN_PASS), I can see it in logs. I see in logs that openmeetings connects to kurento. But I don't understand why all my construction not working as needed? I still can't make settings test, record and play sample, two users can't see each other videos from cameras. Here I should to see to find the solution? On Sun, Mar 15, 2020 at 7:23 PM YUP wrote: > > I was able to connect to kurento websocket which is proxified by > nginx, the solution was very simple, put wss instead of https, > probably for some reasons openmeetings needs to have ws or wss in the > input url: > - OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento > But it is not solved the issue with recording audio/video in test and > different users. > > On Sun, Mar 15, 2020 at 10:16 AM YUP wrote: > > > > No, it is not a reason, checked. > > > > On Sun, Mar 15, 2020 at 10:10 AM YUP wrote: > > > > > > Server has self-signed certificate, can it be a reason? > > > > > > On Sun, Mar 15, 2020 at 9:38 AM YUP wrote: > > > > > > > > Just to inform you, I made proxified kurento websocket in nginx and I > > > > can connect to it: > > > > $ wscat -n --connect https://external_server_ip_address/kurento > > > > (node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName > > > > to an IP address is not permitted by RFC 6066. This will be ignored in > > > > a future version. > > > > Connected (press CTRL+C to quit) > > > > > > > > > > > > > I set > > > > - OM_KURENTO_WS_URL=https://external_server_ip_address/kurento > > > > but got > > > > o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create > > > > Kurento client, will re-try in 1 ms > > > > > > > > > > > > > > > > On Sun, Mar 15, 2020 at 8:56 AM YUP wrote: > > > > > > > > > > Can we just proxify kurento websocket? Something like this > > > > > https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ? > > > > > > > > > > On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik > > > > > wrote: > > > > > > > > > > > > It seems I misread your previous email "all ports except 443, 80, > > > > > > 8080 and 22." > > > > > > I'm afraid you need more open ports ... > > > > > > > > > > > > I'm not sure but I would investigate if KMS/TURN URLs can be set up > > > > > > for context i.e. > > > > > > yourserver:4278/turn, yourserver:/kms in this case you can > > > > > > proxy them > > > > > > > > > > > > On Sun, 15 Mar 2020 at 14:32, YUP wrote: > > > > > > > > > > > > > > It nothing changes, only 443 is open to the world. > > > > > > > > > > > > > > On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik > > > > > > > wrote: > > > > > > > > > > > > > > > > Maybe you can set up KMS to use 8080? > > > > > > > > TURN requires more open port to handle "totally closed" > > > > > > > > networks ... > > > > > > > > > > > > > > > > On Sun, 15 Mar 2020 at 14:18, YUP wrote: > > > > > > > > > > > > > > > > > > It seems to me that I found what is happening. Firewall > > > > > > > > > blocks all non > > > > > > > > > http requests out to all ports except 443, 80, 8080 and 22. > > > > > > > > > That is > > > > > > > > > why I don't have connection to outside turn ans stun servers. > > > > > > > > > Is it > > > > > > > > > possible to connect to those server in such conditions? > > > > > > > > > Tunnels? > > > > > > > > > > > > > > > > > > On Fri, Mar 13, 2020 at 1:09 AM YUP > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hello all, > > > > > > > > > > Could someone help me with configuration of my OM setup? > > > > > > > > > > Any help will > > > > > > > > > > be greatly appreciated. > > > > > > > > > > I have a server which is for several reasons behind NAT, > > > > > > > > > > only 443 port > > > > > > > > > > is open. There is sslh balancer, which redirect external > > > > > > > > > > traffic to > > > > > > > > > > different targets: nginx, openvpn, etc. Openmeetings > > > > > > > > > > 5.0.0-M3 minimal > > > > > > > > > > installed in container behind nginx proxy and works well, > > > > > > > > > > except audio > > > > > > > > > > and video. When I perform setup check after logged in > > > > > > > > > > (video camera > > > > > > > > > > and microphone) I can see myself in camera and can also see > > > > > > > > > > increasing > > > > > > > > > > and decreasing green line, which indicate microphone level, > > > > > > > > > > but I > > > > > > > > > > can't save and replay the testing record. As far I > > > > > > > > > > understand the > > > > > > > > > > problem is in NAT, so I had to use kurento server with TURN > > > > > > > > > > server. I > > > > > > > > > > did that by adding the environment variables for kurento > > > > > > > > > > server in > > > > > > > > > > docker container with the corresponding data for > > > > > > > > > > turn.anyfirewall.com: > > > > > > > > > > > > > > > > > > > > - KMS_STUN_IP=130.211
Re: Some noob question. dont trow me out yet please ;-)
Hello again :) sorry for the late reply, was busy on other tasks Admin UI will not let you to create users without login/password Your option is to sent invitation from the room using following format "John Doe" "Jane Doe" .. As a result special type of users `contacts` will be created These users will have no login/password and can enter the room only using invitation (First/Last name will be parsed at the moment of creation) On Fri, 13 Mar 2020 at 08:22, pete M wrote: > > > > On Thu, Mar 12, 2020, 04:43 pete M > wrote: > Hi every one. I am Pierre and I am from around Montreal QC, > Canada. > > Hello Pierre, > Welcome to our list :) > > Thanks for having me in > > Been looking at a solution to create some large web reunion > for my union group. > > I found a lot of high cost solution like webex and many more.. > > I need to invite people with specific links so that we can > see who is in the meeting and we dont want people to log in twice. > > Been playing with latest 5.0.0-M3 version on a vultr vps. > I've been trying a few things but did not found how to do that kind of stuff. > > Can openmeeting do that? > Should I use another version them 5 ?? > How many invite can I send for one webinar? > > Sure, > You have following options > 1) enter any room, choose Top menu - Activities - Invitation > Fill the form, press send :) > (You can enter more than one email) > > That been tested no problem. > > > In case you plan to invite same people multiple times it might worth > to create group > (And invite group) > > Yes group were created. > > > 2) or, you can generate link using #1 above and send it via your > usual channels > (All users in the room will have same email in this case ) > > That is a no go. really need to have only one login in the webinar by invited > people. no duplicate login dont want invited people to share links. > > If I create 20 user without a login/password but with the first name/last > name, email and assign them to a group. If I do an invite or appointement > will the system send a specific link to the user or will it send the same > link to all user? > > > 3) you can create appointment and add as many meeting members as > necessary > > There are no limits > > OK no limit on invite, thats good. > > I could have to invite 600 people but the max that will > connect will be about 20 to 25% is that even possible and what kind of > hardware I would need for this? Ido have a nice fiber > comming in the building 100MB in / 100 MB out so I hope bandwith wont be a > problem. > > This might be the problem > According to Kurento devs (media server we are using ATM) media > server is limited to ~200 connections > > 200, thats fine. If I have more then that number of user in one webinar I > would be extremly please to have to do more then one meeting. > > Since each user should get stream from all other users your only > chance to have 1 speaker in the room > > Union meetings, they will have only one stream going to the invited anyways. > They will only be able to use the chat to ask question. > > Again thanks for answering my message > > Pierre -- WBR Maxim aka solomax
