Thanks for checking! not sure if i can make things better, have no more ideas right now :( will try to release 5.0.1 with these fixes asap :)
On Thu, 10 Sep 2020 at 04:29, kaffeesurrogat <[email protected]> wrote: > @maxim > > i just finished installing #34 and did some testing. You did some magic. > No more red pop up messages ;-) > > Even the moderator leaving a "wait for moderator" room works without any > problems .... > > sometimes I have a camera is busy message but this vanishes very quickly > .... > > i'm off to bed and many thanks, > > kaffeesurrogat > > On 09/09/2020 18:16, Maxim Solodovnik wrote: > > > > > > On Wed, 9 Sep 2020 at 23:12, kaffeesurrogat <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > > > On 09/09/2020 16:08, Maxim Solodovnik wrote: > > > please check the build #32+ from > > > here > https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/ > > > > will do so ;-) your building faster than i can install ;-) > > > > Thats the right one, isn't it ? > > > > > > > https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/lastSuccessfulBuild/ > > > > > > At least if the headline is > > > > > > Build #32 (Sep 9, 2020 2:27:05 PM) > > > > > > ? > > > > > > Yep, you can use this one :) > > or wait for #33, it should be green :) > > > > > > > > > > > > > > On Wed, 9 Sep 2020 at 20:47, Maxim Solodovnik > > <[email protected] <mailto:[email protected]> > > > <mailto:[email protected] <mailto:[email protected]>>> > wrote: > > > > > > > > > > > > On Wed, 9 Sep 2020 at 16:42, kaffeesurrogat > > > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>>> wrote: > > > > > > Dear Maxim, > > > > > > On 08/09/2020 17:02, Maxim Solodovnik wrote: > > > > Am I right thinking everything works as expected? > > > > The only issue is annoying red popups? > > > > > > right this is working .... many thanks for the fix ... is > > > there a way to > > > surpress all those messages ? > > > > > > > > > working on it > > > please be more patient .... ;) > > > > > > > > > > > > If the room is not set to "wait if the moderator is not > > there" > > > i have > > > almost none of the red popups .... ;-) > > > > > > > > > > According TURN > > > > > > > > This version can't affect your TURN server :) > > > > > > > > AFAIK > > > > you don't need to provide `user` > > > > Only `static-auth-secret` > > > > > > > > I have > > > > ``` > > > > fingerprint > > > > lt-cred-mech > > > > use-auth-secret > > > > static-auth-secret=bla-bla-bla > > > > realm=om.alteametasoft.com > > <http://om.alteametasoft.com> <http://om.alteametasoft.com> > > > <http://om.alteametasoft.com> > > > > stale-nonce=0 > > > > proc-user=nobody > > > > proc-group=nogroup > > > > ``` > > > > > > i changed my config, it is still working ;-) > > > > > > > > > many thanks, > > > > > > kaffeesurrogat > > > > > > > > > > > some of above options might conflict but so far they > works > > > on demo > > > > > > > > > > > > On Tue, 8 Sep 2020 at 21:11, kaffeesurrogat > > > <[email protected] > > <mailto:[email protected]> <mailto:[email protected] > > <mailto:[email protected]>> > > > > <mailto:[email protected] > > <mailto:[email protected]> > > > <mailto:[email protected] > > <mailto:[email protected]>>>> wrote: > > > > > > > > Dear Denis, dear Maxim, dear Alvaro > > > > > > > > @maxim: many thanks for the fix .... > > > > > > > > I did install the new snapshot: > > > > > > > > OpenMeetings > > > > 5.0.1-SNAPSHOT > > > > 5e724bf > > > > 2020-09-07T16:30:21Z > > > > > > > > The setup is still the same: > > > > > > > > user1 > > > > > > > > chrome 84.0.04147.135 (Official Build) 64 Bit gentoo > > > linux machine > > > > > > > > user 2 > > > > > > > > Firefox 79 (64 Bit) > > > > Windows 10 > > > > > > > > user 1 and user 2 both on the same network different > > > machines > > > > > > > > server > > > > > > > > ubuntu 18.04 LTS > > > > > > > > > > > > I followed the same way of clicking, entering the > > room, > > > ... as > > > > before the fix: > > > > > > > > > > > > 1) login user 1 (moderator) > > > > 2) user 1 entering private room > > > > 3) user 1 turns camera and mic on > > > > 4) login user 2 (not a moderator) > > > > 5) user 2 is entering private room > > > > 6) user 2 requests permissions to use camera and mic > > > > 7) user 1 grants permissions to use camera and mic > via > > > activities and > > > > actions > > > > 8) user 2 turns on camera and mic > > > > user 1 and user 2 see/hear each other > > > > 9) user 1 leaves the room > > > > user 2 sees "wait for moderator..." message > > > > 10) user 1 re-enters the room > > > > wait for moderator dissapears > > > > user 1/user 2 cameras/mics off > > > > 11) user 1 turns cam/mic back on > > > > => user 2 sees user 1 > > > > > > > > 12) user 2 turns cam/mic back on > > > > => user 1 does not see user 2 (question mark > > face ...) > > > > => several mic symbols displayed on user 2 - > > browser > > > for user > > > > 2.... > > > > > > > > STEP 12 DID CHANGE: > > > > > > > > I've got new error messages for user 2, see > > attached files, > > > > but both users can see and hear each other. > > > > THE MIC SYMBOL IS SHOWING UP ONLY ONCE > > > > > > > > > > > > I did some more testing: > > > > > > > > > > > > 1) login user 1 (moderator) > > > > 2) user 1 entering private room > > > > 3) user 1 turns camera and mic on > > > > 4) login user 2 (not a moderator) > > > > 5) user 2 is entering private room > > > > 6) user 2 requests permissions to use camera and mic > > > > 7) user 1 grants permissions to use camera and mic > via > > > activities and > > > > actions > > > > 8) user 2 turns on camera and mic > > > > user 1 and user 2 see/hear each other > > > > 9) user 1 DOES NOT leave the room > > > > user 2 turns camera and mic several times on > > and off > > > > > > > > The error message from step 12 picture_01 does > > appear > > > very seldom > > > > The error message from step 12 picture_02 does not > > > appear at all. > > > > The error message from step 12 picture_03 does not > > > appear at all. > > > > > > > > > > > > Hope this helps a bit .... > > > > > > > > > > > > What I noticed during setup of the new snapshot, > > that i > > > had some > > > > troubles with the coturn server. > > > > > > > > After following the Alvaro-Instructions SSL .... , i > > > was testing > > > > my coturn server using > > > > > > > > turnutils_uclient -v -u nobody -w a_new_password > > > my.server.org <http://my.server.org> <http://my.server.org > > > > > > <http://my.server.org> > > > > > > > > turnutils_uclient failed with "cannot complete > > Allocation" > > > > > > > > turnserver.log says > > > > > > > > 2375: check_stun_auth: Cannot find credentials of > user > > > <nobody> > > > > > > > > I've reread /etc/turnserver.conf: > > > > > > > > > > > > # 'Static' user accounts for long term credentials > > > mechanism, only. > > > > # This option cannot be used with TURN REST API > > > > # This option require a realm. > > > > # 'Static' user accounts are NOT dynamically > > checked by the > > > > turnserver process, > > > > # so that they can NOT be changed while the > turnserver > > > is running. > > > > # > > > > #user=username1:key1 > > > > #user=username2:key2 > > > > # OR: > > > > user=nobody:a_new_password > > > > > > > > > > > > Since it says that this option cannot be used with > > TURN > > > REST API > > > > i've disabled > > > > the lines > > > > > > > > #use-auth-secret > > > > > > > > > > > #static-auth-secret=c852f177eb61782daad0103a6141477dd90bf2714db1984daba09316dcd53a44 > > > > > > > > Now > > > > > > > > turnutils_uclient -v -u nobody -w a_new_password > > > my.server.og > > > > > > > > leaves > > > > > > > > session 002000000000000001: new, > > realm=<my.server.org <http://my.server.org> > > > <http://my.server.org> > > > > <http://my.server.org>>, username=<nobody>, > > lifetime=777 > > > > 3: session 002000000000000001: realm > > <my.server.org <http://my.server.org> > > > <http://my.server.org> > > > > <http://my.server.org>> user <nobody>: incoming > packet > > > ALLOCATE > > > > processed, success > > > > 3: session 002000000000000001: refreshed, > > > realm=<my.server.org <http://my.server.org> > > <http://my.server.org> > > > > <http://my.server.org>>, username=<nobody>, > > lifetime=777 > > > > 3: session 002000000000000001: realm > > <my.server.org <http://my.server.org> > > > <http://my.server.org> > > > > <http://my.server.org>> user <nobody>: incoming > packet > > > REFRESH > > > > processed, success > > > > 3: handle_udp_packet: New UDP endpoint: local addr > > > > MYIPCOTURNHOST:3478, remote addr > > MYIPCOTURNCLIENT:39612 > > > > > > > > in the turnserver log .... > > > > > > > > > > > > and turnutils_uclient talks about a lot of > > packages send > > > to my > > > > coturn server, but openmeetings is not running at all > > > with these > > > > settings :-) > > > > > > > > I guess i did not understand, how this > > > > cuturn,kurento-media-server,openmeetings > > combination is > > > working ;-( > > > > > > > > > > > > Again many thanks, sorry for making such a long > > post .... > > > > > > > > > > > > kaffeesurrogat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Maxim > > > > > > > > > > > > > > > -- > > > Best regards, > > > Maxim > > > > > > > > > > > > -- > > > Best regards, > > > Maxim > > > > > > > > > > -- > > Best regards, > > Maxim > > -- Best regards, Maxim
