Thanks Denis, much appreciated :) On Wed, 1 Apr 2020 at 11:52, Denis Noctor <denisnoc...@gmail.com> wrote:
> Hi there Maxim, > > Thank you so much for the offer of going through the log files. However, > after seeing the volume of emails you’ve been answering... and continue to > do so, I didn’t think it was fair to distract you further with my problem > and as a result decided to go through everything again and I have since > worked it out (after one or two surprises also). I have everything now > working on an AWS EC2 instance, using my own TURN server setup. > > I am going to write a separate email regarding how I set everything up on > AWS.... as the setup is slightly different and hope this will be of some > help to the group. > > I just want to take the opportunity now to say a “Big Thank You!” And > extend a virtual hug. I am not a real techie and as a result am amazed at > the level of patience and support that is given in this group ... and want > to say thank you to all those who have positively contributed to this forum > also. > > I will continue to look at the snapshots and give my input and feedback no > matter how small. > > Thanks again. > > Denis > > > Sent from my iPhone > > On Mar 26, 2020, at 7:30 PM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > > Can you share your openmeetings.log (can be shared privately) > Better if it will be log for one session (with exact times of camera drops) > > And couple of words about your client environment > OS/Browser > > Is the issue browser dependent? > > The only report like this so far was from user at Windows Terminal server > ... > > On Fri, 27 Mar 2020 at 06:17, Denis Noctor <denisnoc...@gmail.com> wrote: > >> Hi there Maxim, >> >> First of all, thanks for all your efforts to date. I have noticed via the >> forum you have been fighting fires answering lots of emails and queries and >> I salute you. >> >> I decided it best to take a few days before answering you email after >> upgrading everything to *OM 5 M3* (as per Alvaro’s instructions, which >> are great). >> Version 5.0.0-M3 >> Revision b739f87 >> Build date 2019-12-11T11:42:09Z >> Connect direct >> Using Chrome browser (as are my students) Version 80.0.3987.149 (Official >> Build) (64-bit) >> >> AWS E2 Instance >> Ubuntu 18.04.4 LTS(FULL SPECS AND PORTS OPEN AT THE BOTTOM OF EMAIL >> https:// with AWS Certificate >> >> I installed everything as per the instructions and setup up a “*Turn >> server*” account with *NUMB* (*http://numb.viagenie.ca/ >> <http://numb.viagenie.ca/>*) as recommended by as per Tajuddin Bennur’s >> >> >> https://mail-archives.apache.org/mod_mbox/openmeetings-user/201905.mbox/browser >> >> and made the following changes (*ONLY*) as per the recommendations in: >> /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini >> >> uncommenting and adding: >> >> >> *turnURL=USERNAME:PASSWORD@158.69.221.198:3478 >> <http://USERNAME:PASSWORD@158.69.221.198:3478> *In >> /opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml >> >> The only changes I made were similar to those above (though I tested >> everything before adding these changes are the following – but honestly, I >> haven’t really noticed any difference: >> >> <bean id="kurentoHandler" >> class="org.apache.openmeetings.core.remote.KurentoHandler" >> init-method="init" destroy-method="destroy" >> >> p:kurentoWsUrl="ws://127.0.0.1:8888/kurento" >> >> p:checkTimeout="10000" >> >> p:watchThreadCount="10" >> >> * p:turnUrl="158.69.221.198:3478 >> <http://158.69.221.198:3478>"* >> >> * p:turnUser="USERNAME"* >> >> * p:turnSecret="PASSWORD"* >> >> p:turnMode="rest" >> >> p:turnTtl="60" >> >> p:objCheckTimeout="200" >> >> /> >> >> >> >> >> The end result is: Whiteboard for my uses is working beautifully, >> conversion process is working beautifully, drag and drop of audio and video >> is working beautifully… though I tried to upload a 59 M file and everything >> seemed to hang for a while so I cancelled the upload… but appeared in my >> online files later on… probably more ram and CPU speed will deal with >> this.. no major problem as I re-uploaded a smaller vid file and it did the >> job. >> >> In all everything is working well except for the following: >> >> When enter a room, I can see and talk to a student ( and vice versa) very >> well. Audio quality is good and cam settings are as expected. This is >> something I couldn’t do in the past without the recommended Turn Server >> settings as mentioned about. >> >> *PROBLEM:* >> When I enter a conference room( first), and then when 2 students enter >> the room… after some time my cam box disappears from my screen. I am still >> in the room… I can still hear and see everyone else interacting with each >> other – but they can’t see or hear me. When I click on the cam and camera >> icon everything continues as normal until it happens again. Worth noting – >> I am the moderator. >> >> However, if I don’t turn on my camera and microphone again… after some >> time the same thing happens to the first user that entered the room after >> me… and so on. >> >> Apart from that everything is working really well. I remember some time >> back that a similar problem occurred with a user in the past but I can find >> anything in the user forums. >> >> Again important to note that I am using a TURN SERVER setup as mentioned >> above…. I have NOT implemented COTURN as I am under the impression TURN >> overrides COTURN.(?). >> >> Any suggestions / help as to what might be causing this? >> >> All the best, >> >> Denis >> >> Specs: >> >> AWS EC2 SERVER >> >> Instance type >> >> Memory (MiB) >> (Instance type) T3a.medium - t3a.medium 2(vCPUs) >> (Architecturex86_64) 4096 Memory (MiB) >> >> Ubuntu 18.04.01 >> >> LAMP setup >> >> PORTS OPEN: >> INBOUND >> Custom UDP UDP 3478 0.0.0.0/0 - >> >> Custom UDP UDP 3478 ::/0 - >> >> HTTP TCP 80 0.0.0.0/0 - >> >> HTTP TCP 80 ::/0 - >> >> Custom TCP TCP 8888 0.0.0.0/0 - >> >> Custom TCP TCP 8888 ::/0 - >> >> Custom TCP TCP 5080 0.0.0.0/0 - >> >> Custom TCP TCP 5080 ::/0 - >> >> SSH TCP 22 0.0.0.0/0 - >> >> Custom TCP TCP 5443 0.0.0.0/0 - >> >> Custom TCP TCP 5443 ::/0 - >> >> Custom TCP TCP 3478 0.0.0.0/0 - >> >> Custom TCP TCP 3478 ::/0 - >> >> All UDP UDP 0 - 65535 0.0.0.0/0 - >> >> All UDP UDP 0 - 65535 ::/0 - >> >> RDP TCP 3389 0.0.0.0/0 - >> >> RDP TCP 3389 ::/0 - >> >> HTTPS TCP 443 0.0.0.0/0 - >> >> HTTPS TCP 443 ::/0 - >> >> Custom ICMP - IPv4 Echo Request N/A 0.0.0.0/0 >> - >> >> Custom ICMP - IPv4 Echo Request N/A ::/0 - >> >> _____________________________ >> >> OUBOUND >> >> All traffic All All 0.0.0.0/0 >> - >> >> All traffic All All ::/0 >> >> On Fri, Mar 20, 2020 at 7:38 AM Maxim Solodovnik <solomax...@gmail.com> >> wrote: >> >>> Hello, >>> >>> I got reports like this before M3 has been released >>> Debugging shows camera/microphone stream just stops flow on client >>> (you can see NOT_FLOWING in the logs) >>> I was able to see this on Windows VM only, one of the cases was fixed >>> and was included into M3 >>> >>> I would appreciate if you can share details so I'll try to reproduce >>> the issue (impossible to fix without reproducing) >>> 1) Is the problem reproducible at demo-next? >>> https://om.alteametasoft.com:8443/next/ (It is M4, but still will be >>> good to know) >>> 2) Your client/server OS >>> 3) Client browser name/version >>> 4) Are you connecting directly or have front-end proxy (Apache/nginx) >>> 5) Do you have CPU high load during connection interruption? >>> 6) Anything else ... >>> >>> On Fri, 20 Mar 2020 at 16:06, Denis Noctor <denisnoc...@gmail.com> >>> wrote: >>> > >>> > Hi there Hosch, my gut reaction is that this is down to the turn >>> server setup I have... but I could be wrong. I am hoping that if there is >>> someone out there that has managed to setup a perfectly working model... >>> that they might share... and explain it in simple terms from A to Z... >>> after the initial installation prerequisites. It is 3am on this side, so I >>> will put my head down for a few hours... but hopefully will wake up to a >>> plethora of suggestions... look after yourself too. Talk soon... and thanks >>> for reaching out! All the best. Denis. >>> > >>> > Sent from my iPhone >>> > >>> > On Mar 20, 2020, at 2:45 AM, Stefan Kühl <ste...@quatrekuehl.eu> >>> wrote: >>> > >>> > Morning! >>> > >>> > Denis, could please explain how you are going to connect to OM? Is it >>> possible that these problems are caused by network issues? >>> > I've got this by myself yesterday evening in a class with 7 other >>> students. Couldn't find anything in kurento or om logs. I suggested that I >>> just run in little disconnections in private network or provider >>> connections?! >>> > >>> > Greetings and stay healthy everyone! >>> > >>> > >>> > Hosch >>> > >>> > >>> > >>> > >>> > Am 20.03.2020 09:15, schrieb Denis Noctor: >>> > >>> > @Tajuddin and anybody else that can help. >>> > >>> > Tajuddin, I have been "off grid" for some time and apologies to those >>> I have not been able to be in contact with recently. >>> > >>> > Hopefully you might be able to provide me with some help. And please >>> forgive me if I haven't seen a previous, solution or comment that might >>> help me with this problem. >>> > >>> > I am adding to a thread that was created by in May of last year >>> (2019)... and given the whole Coronavirus issue, I have been forced to look >>> into a working version of OpenMeetings, on an AWS instance... before things >>> turn to s#it on my side... and when I say "s#it"... it is breaking my heart. >>> > >>> > I set up OM some time back and everything seem to run beautifully.... >>> a few glitches with uploading ( I understand there have been some >>> improvements).... but after increasing ram and cpu speed things got to an >>> acceptable level (running OM 5 - M2). As you can appreciate, due to recent >>> events, I have needed to revisit the whole online approach of things and >>> have ran into the following problem: >>> > >>> > (Tested with me and a few others students on a "one to one" basis) >>> > >>> > When I am initially in a room... everything works as expected, I am >>> able to move from whiteboard to whiteboard and demonstrate a great class, >>> with audio, video, pdfs and so on.... but suddenly my audio and video is >>> disconnected... I can still see and hear the other participant... but they >>> can't see or hear me.... I refresh the page... and everything continues as >>> normal for a few mins... and my audio and video is disconnected again. This >>> "seems" to be Kurento related only (I assume) as I can still interact with >>> everyone via whiteboard etc. >>> > >>> > Based on previous messages that you may see below with Tajuddin, this >>> is probably related to having a AWS EC2 virtual server... using a "NUMB" >>> "turn server" (details below in a previous message). >>> > >>> > Is there anyone out there that can explain in simple terms... "apples >>> and bananas"... what I should be doing in order to get things running to at >>> least a minimal acceptable level? >>> > >>> > For reference, I have the following setup (I know that some >>> recommendations will be to upgrade to OM 5.03... but I am still curious as >>> to the "why" regarding my current setup and situation). >>> > >>> > OM >>> > Version 5.0.0-M2-SNAPSHOT >>> > Revision 85daa3b >>> > Build date 2019-05-13T16:53:23Z >>> > >>> > Kurento 6.10.0 bionic kms6 >>> > >>> > Ubuntu 18.04 >>> > >>> > Once again, if if hasn't been clear... in this email or others... I am >>> a simple teacher that thought by opening up a AWS EC2 instance, I could >>> make a difference... and now even more, given the state of affairs... I am >>> bumbling over my owns steps trying to get something working... I think I >>> have even knotted myself up in confusion. >>> > >>> > I would appreciate any help on this... @Tajuddin @Maxim and at >>> anybody else. >>> > >>> > If you can.... please... get back in touch with constructive comments >>> or suggestions... I know you all have a lot going on during this time and I >>> wish you all the best and good health... >>> > >>> > I am more than happy to make myself a personal ambassador of OM after >>> all of this! >>> > >>> > All the best. >>> > >>> > Denis >>> > >>> > >>> > >>> > On Tue, May 28, 2019 at 4:04 AM Denis Noctor <denisnoc...@gmail.com> >>> wrote: >>> >> >>> >> Good man Tajuddin. Much appreciated - will check this out in the >>> morning. All the best, Denis. >>> >> >>> >> Sent from my iPhone >>> >> >>> >> On May 28, 2019, at 2:49 AM, Tajuddin Bennur <tajben...@gmail.com> >>> wrote: >>> >> >>> >> Hi Denis, >>> >> >>> >> Apologies for the late reply. >>> >> >>> >> To answer your question, and the steps which I followed are as >>> follows, which are most similar to the steps which you shared in your email. >>> >> >>> >> As per instructions are given in the " >>> https://doc-kurento.readthedocs.io/en/6.10.0/user/installation.html#installation-stun-turn"; >>> document, >>> >> >>> >> 1. I opened all the UDP ports in my security group. >>> >> 2. Then I registered to the NUMB server to get the username and >>> password. >>> >> 3. To configure a TURN server in KMS, uncommented the following lines >>> in the WebRtcEndpoint configuration file, located at >>> /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini >>> >> >>> >> turnURL=<user>:<password>@<serverIp>:<serverPort> >>> >> >>> >> Following details are used in the server >>> >> >>> >> turnURL=<myusername>:<mypassword>@158.69.221.198:3478 >>> >> >>> >> 4. And restarted the Kurento server. >>> >> >>> >> >>> >> >>> >> Thus my Mic and Audio issue resolved. >>> >> >>> >> >>> >> >>> >> On Thu, May 23, 2019 at 1:51 PM Denis Noctor <denisnoc...@gmail.com> >>> wrote: >>> >>> >>> >>> Hi there Tajuddin (and everyone else), >>> >>> >>> >>> Would you be kind enough to go through step by step the process you >>> went through to solve your problem. >>> >>> >>> >>> I have gone through all the installation processes of installing >>> everything on an AWS EC2 instance (with Ubuntu 18.04.2 LTS). At first >>> glance everything seemed to be working fine until I realized that when 2 >>> users were logged on in a room, they could see their own camera but could >>> not see the other participants screen (this applies to audio also). >>> >>> >>> >>> At first I thought this might be down to how I installed everything >>> but having read most (if not all the treads), I came across the following >>> query which suggests a Turn Server is required... ( >>> https://issues.apache.org/jira/browse/OPENMEETINGS-2066
 ) >>> According to the Kurento documentation ( >>> https://doc-kurento.readthedocs.io/en/6.10.0/user/installation.html >>> ) 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. I tried the suggest TURN settings using >>> NUMB (after registering a user name and password), but with no joy, still >>> have the same problem. >>> >>> >>> >>> Finally on a separate matter I noticed there are 9 versions of >>> Alvaro's instructions for setting up openmeetings on Ubuntu 18.04 LTS - >>> versions 1 to 7 make reference to DOCKER.... 8 and 9 don't. Excuse my >>> ignorance but does that mean it is no longer require. All versions contain >>> the same date (25-3-2019). >>> >>> >>> >>> Any help would be appreciate. >>> >>> >>> >>> All the best. >>> >>> >>> >>> Denis >>> >> >>> >> >>> >> >>> >> -- >>> >> Thanks & Regards, >>> >> Tajuddin Bennur >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> > > -- > WBR > Maxim aka solomax > > -- WBR Maxim aka solomax
