Maxim, just to give some feedback. As we had some issues with 20.04 and docker kms. Ubuntu 18.04 , Open meetings nearly actual snapshot works fine now.
The hardware server has direct internet connection, IPV4. It might be related, that we disable IPV6, we do not use it. I guess a lot´s of people do use 20.04 server, probably without issues. We were not able to figure the reason out. If in the same network we had the same disconnects after view seconds, so I doubt it has to do with misconfigured coturn on the 20.04 However, coturn is installed on 18.04, connection from behind NAT are working fine too. We will try now the SIP stuff. Regards Gerald Von: Maxim Solodovnik [mailto:[email protected]] Gesendet: Sonntag, 8. November 2020 13:30 An: Openmeetings user-list <[email protected]> Betreff: Re: openMeeting 5.1 Media Server Disconnected On Sun, 8 Nov 2020 at 17:17, Rohrbach, Gerald <[email protected]<mailto:[email protected]>> wrote: Maxim, did this. No difference. I did a new installation, following the install instruction, to make sure I did not missed one line... Second time I did not used coturn and certifactes, for that I used chrome instead of firefox. Firefox does not allows the connection without certificates. Well, In your first try there were no TURN server, due to missing parameters No you have decided not to use it .... I would expect same results ... The same result, no improvement or change. If I go into a room, choosed camera etc. I get my video, after 10 > seconds this message, video disappeared > > Media Server connection failed, try to reconnect But it is not reconnecting. We have over the last weeks several time reinstalled , restarted, always the same issue. With the none docker kms version we had it working fine, older Version M4. you should use Ubuntu 18.04 to have "real" (not dockerized) KMS I´m pretty sure it has to do with our installation. The folder open 510 is nobody and nogroup. But log files are all root root. Is this correct? this most probably because you have started Tomcat as `root` We will install next week again and use only internal network, but I remember we did this, same behaviour. It`s standard Ubuntu 20.04 server, fresh install. Where is a good starting point for searching the problem? I don’t think its related with the new version 5.1. 5.01 we had the same issues. I have the feeling it has to do with the docker kms. so far I think the problem is caused by absence of TURN server Regards Gerald -----Ursprüngliche Nachricht----- Von: Maxim Solodovnik [mailto:[email protected]<mailto:[email protected]>] Gesendet: Sonntag, 8. November 2020 02:46 An: Openmeetings user-list <[email protected]<mailto:[email protected]>> Betreff: Re: openMeeting 5.1 Media Server Disconnected in upcoming 5.1.0 these changes need to be done in `openmeetings.properties` file just fill your previous values without quotes :) On Sun, 8 Nov 2020 at 01:30, Rohrbach, Gerald <[email protected]<mailto:[email protected]>> wrote: > > I’ve been using the 5.0.0-M5-SNAPSHOT version quite a while, with LDAP works > fine. > > That was the traditional setup with kurento local installed. > > > > As I got a new hardware server now I want to install an actual > snapshot > > apache-openmeetings-5.1.0-SNAPSHOT.tar.gz ( Ubuntu 20.04 server) > > > > So far I know the steps and used Alvaros documentation. Pretty perfect. > > The only issue comes with installing vlc. As I want only commandline version > vlc installs the desktop also. > > and some powersaving options make it difficult. So I do not install vlc. > Maybe a hint for documentation. > > > > However, the install works fine. > > The server is connected direct to internet, official IPV4 address. No Natting > at this point. > > > > I also followed the document installing coturn and letsencrypt certificates. > > > > sudo nano > /opt/open501/webapps/openmeetings/WEB-INF/classes/applicationContext.x > ml > > Well, in my applicationContext.xml there is no section. > > > > > > <!-- Kurento --> > > <bean id="kurentoHandler" > class="org.apache.openmeetings.core.remote.KurentoHandler" > > p:kurentoWsUrl="ws://127.0.0.1:8888/kurento<http://127.0.0.1:8888/kurento>" > > p:checkTimeout="10000" > > p:watchThreadCount="10" > > p:turnUrl=" > > Public IP of your server > > : > > 3478 > > " > > p:turnUser=" > > nobody > > : > > here the password you choose for kurento in step 6 > > " > > p:turnSecret=" > > 751c45cae60a2839711a94c8d6bf0089e78b2149ca602fdXXXXXXXXXXXXX > > " > > p:turnMode="rest" > > p:turnTtl="60" > > p:objCheckTimeout="200" > > p:flowoutTimeout="5" > > p:kuid="df992960-e7b0-11ea-9acd-337fb30dd93d" > > p:ignoredKuids="" > > /> > > > > > > That’s at the end the Problem: > > If I go into a room, choosed camera etc. I get my video, after 10 > seconds this message, video disappeared > > Media Server connection failed, try to reconnect. > > > > So probably it is related to the coturn config. > > > > Is the documentation wrong somehow, mistake between ears or some changes for > the newest version? > > > > I’m very interested in the SIP connection and would like to test this in > detail. > > > > > > Kind regards > > Gerald > > -- Best regards, Maxim -- Best regards, Maxim
