I found all .webm files under the same data_dir path under docker:
/var/lib/docker/overlay2/.../diff/home/website_home/data_dir/streams/TEST_SETUP_694fad35-92ea-420f-99ff-f0203581460f.webm
Several .webm files are there
It seems that KMS created the full data_dir path from /home under docker
How did this happen? and how should it be corrected?
I defined this path during installation using the same command in installation
guide, but KMS instead of referring to the existing path it created its own!
بتاريخ الثلاثاء، 8 آب 2023 في 08:28:25 ص غرينتش+3، Maxim Solodovnik
<solomax...@gmail.com> كتب:
On Tue, 8 Aug 2023 at 05:22, Online Use <foronlineuseem...@yahoo.com> wrote:
>
> I used the hash?app=settings URL and I recorded a test recording, and was
> able to play it, but I didn't find where the recording file is saved in the
> data_dir path.
It is stored under "${DATA_DIR}/streams/TEST_SETUP_{RANDOM_UUID}.webm"
(the file is being recorded/played by KMS, OM is NOT affected)
can you see the file at OM filesystem?
If NO you definitely have issues with data_dir mapping :((
try to enter running KMS docker and search recordings using find command:
`find / -type f -name "TEST_SETUP_*.webm"`
what whould be result of such command at 2 systems?
>
> I think KMS recroding should be working correctly, but there is some issue
> from within the OM system itself.
>
>
> بتاريخ الاثنين، 7 آب 2023 في 06:31:39 ص غرينتش+3، Maxim Solodovnik
> <solomax...@gmail.com> كتب:
>
>
> KMS is being instructed by OM :)
> So OM sends command like "Start the recording and put the file into
> $DATA_DIR/streams/"
> and KMS stores recording at the path given BUT inside docker
> So correct mount should be set so OM can also see these files
>
> Can you check if test recording works for you:
> https://localhost:5443/openmeetings/hash?app=settings
> (use your IP/server name in the URL above :))
>
> On Sun, 6 Aug 2023 at 03:45, Online Use <foronlineuseem...@yahoo.com> wrote:
> >
> > If KMS is using its own work directory inside docker, where will the files
> > be so that I verify that?
> >
> >
> > بتاريخ الجمعة، 4 آب 2023 في 06:59:40 ص غرينتش+3، Maxim Solodovnik
> > <solomax...@gmail.com> كتب:
> >
> >
> > Hello,
> >
> > thanks for pinging! (too much day-time job :((( )
> >
> > let's get back to the topic :)
> >
> > On Fri, 4 Aug 2023 at 04:55, Online Use <foronlineuseem...@yahoo.com> wrote:
> > >
> > > Hello,
> > >
> > > I hope you have enough time to follow up with me regarding this issue.
> > > Can you tell me what you think?
> > >
> > > Thanks.
> > >
> > > بتاريخ الجمعة، 28 تموز 2023 في 06:52:17 ص غرينتش+3، Online Use
> > > <foronlineuseem...@yahoo.com> كتب:
> > >
> > >
> > > Yes the test files and folder 5 have been created successfully, and I
> > > already had folders for other room number with files. As I mentioned
> > > before I have empty video files inside room folder
> > > "rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav"
> >
> > I believe here might be misunderstanding
> >
> > Actually your configuration consist of two isolated Linuxes running at
> > the same phisycal machine
> > - first one is OM: it server web interface sending commands to KMS and
> > do process the recordings
> > - second one is KMS which handling multimedia part
> >
> > So the process of record in the room organized as follows:
> > - user press the button in UI
> > - OM send the command to KMS to start recording
> > - KMS start writing to
> > home/website_home/data_dir/streams/_ROOM_ID_/_LONG_UUID_.webm file and
> > sends ACK to OM
> > - OM displays "Recording has been started" to the user
> > - user stops recording in the UI (via button, room exit etc.)
> > - OM sends stop command to KMS
> > - KMS stops the recording, close the file and send ACK to the OM
> > - OM starts converting *.webm file
> > -- For all rooms except INTERVIEW --
> > * extracts audio from all webcam video OR create *.wav with silence
> > * join the audio with **SCREEN SHARING** video
> > -- For INTERVIEW rooms --
> > * join video from cameras of all participants into big "video carpet"
> >
> > So in case there is no *.webm file
> > - KMS might fail to write it (KMS logs need to be examined)
> > - **data_dir/streams** folder is mounted incorrectly and KMS writes
> > something inside it's Linux while OM can't see it
> > - permission issue
> > -
> > - something else
> >
> > we need to check all vectors ....
> >
> >
> > >
> > > The problem was in creating the temporary processing files in the
> > > hibernate folder, I think.
> > >
> > >
> > > بتاريخ الجمعة، 28 تموز 2023 في 05:53:24 ص غرينتش+3، Maxim Solodovnik
> > > <solomax...@gmail.com> كتب:
> > >
> > >
> > > On Fri, 28 Jul 2023 at 03:17, Online Use <foronlineuseem...@yahoo.com>
> > > wrote:
> > > >
> > > > I got the following output in both cases, from outside and inside
> > > > docker:
> > > >
> > > > total 16
> > > > drwxrwxrwx. 4 root root 4096 Apr 19 00:55
> > > > .
> > > > drwx--x--x. 8 cloud7843 cloud7843 4096 Jul 27 00:00 ..
> > > > drwxrwxrwx. 6 root root 4096 Apr 21 22:03
> > > > streams
> > > > drwxrwxrwx. 5 root root 4096 Apr 19 01:05
> > > > upload
> > > >
> > > > I frankly don't know what is this cloud7843 user?
> > >
> > > This is the owner of "/home/website_home" folder
> > >
> > > KMS writes to "/home/website_home/data_dir/streams" and
> > > "/home/website_home/data_dir/streams/ROOM_ID"
> > >
> > > could you run following commands inside KMS docker:
> > >
> > > cat "test1" > /home/website_home/data_dir/streams/test1
> > > mkdir /home/website_home/data_dir/streams/5
> > > cat "test2" > /home/website_home/data_dir/streams/5/test2
> > >
> > > room_id -> 5 === "Public Presentation Room"
> > >
> > > And check if files were successfully created and visible and readable
> > > on host machine?
> > >
> > > >
> > > > Do you think this line is the problem?
> > > >
> > > >
> > > >
> > > > بتاريخ الخميس، 27 تموز 2023 في 07:26:46 ص غرينتش+3، Maxim Solodovnik
> > > > <solomax...@gmail.com> كتب:
> > > >
> > > >
> > > > Hello All,
> > > >
> > > > sorry for being silent
> > > > answering this email was in my TODO list :)
> > > >
> > > > Recently I was able to set up our demo server [1]
> > > > The recordings works as expected (can be tested with [2])
> > > > It is Ubuntu 22.04 + Dockerized KMS
> > > >
> > > > So I believe there is nothing wrong with such configuration or
> > > > Dockerized KMS
> > > >
> > > > I would say something wrong with your
> > > > - folder mapping
> > > > and/or
> > > > - permissions
> > > >
> > > > BUT
> > > > since everything in your config is under `root` I don't think it can
> > > > be permission issue
> > > >
> > > > can you please check the following command
> > > >
> > > > `ls -la /home/website_home/data_dir`
> > > > ( and try some subfolders too)
> > > >
> > > > produces the same output
> > > > - from inside docker
> > > > - AND at your host machine (where OM process is working)
> > > > ?
> > > >
> > > > [1] https://demo-openmeetings.apache.org/openmeetings
> > > > [2] https://demo-openmeetings.apache.org/openmeetings/hash?app=settings
> > > >
> > > > On Thu, 27 Jul 2023 at 04:26, Online Use <foronlineuseem...@yahoo.com>
> > > > wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I haven't get response to this message. Would you please advise? the
> > > > > issue is still persistent.
> > > > >
> > > > > Did you find out any cause within this version of OM?
> > > > >
> > > > >
> > > > >
> > > > > بتاريخ السبت، 15 تموز 2023 في 10:21:56 ص غرينتش+3، Online Use
> > > > > <foronlineuseem...@yahoo.com> كتب:
> > > > >
> > > > >
> > > > > Thanks. I also now verified that KMS is started using root with uid 1.
> > > > >
> > > > > How can I check that OM is running using same user?
> > > > >
> > > > >
> > > > > بتاريخ السبت، 15 تموز 2023 في 07:48:37 ص غرينتش+3، Maxim Solodovnik
> > > > > <solomax...@gmail.com> كتب:
> > > > >
> > > > >
> > > > > On Fri, 14 Jul 2023 at 21:10, Online Use via user
> > > > > <user@openmeetings.apache.org> wrote:
> > > > > >
> > > > > > Can you tell me how to verify the user name who is running KMS? I
> > > > > > installed it from shell using root, just like all OM installation
> > > > > > steps.
> > > > >
> > > > > your KMS is running in docker
> > > > >
> > > > > so you have to do the following:
> > > > >
> > > > > run
> > > > > `docker ps`
> > > > >
> > > > > in terminal
> > > > > You will get output like
> > > > > ```
> > > > > docker ps
> > > > > CONTAINER ID IMAGE COMMAND
> > > > > CREATED STATUS PORTS NAMES
> > > > > 8d89d696012f kurento/kurento-media-server:7.0.0 "/entrypoint.sh
> > > > > bash" 6 seconds ago Up 5 seconds (health: starting)
> > > > > sad_gagarin
> > > > > ```
> > > > > now you have to copy "CONTAINER ID"
> > > > >
> > > > > and run following command
> > > > > `docker exec -it 8d89d696012f bash`
> > > > >
> > > > > in terminal (please use your own "CONTAINER ID")
> > > > > please NOTE "CONTAINER ID" is unique and generated on every new run
> > > > >
> > > > > now you are inside the docker
> > > > >
> > > > > you can use `ps -ef|grep kurento`
> > > > > for my machine the output is:
> > > > > ```
> > > > > root 1 0 0 04:38 pts/0 00:00:00
> > > > > /usr/bin/kurento-media-server bash
> > > > > root 61 52 0 04:39 pts/1 00:00:00 grep --color=auto
> > > > > kurento
> > > > > ```
> > > > >
> > > > > so the KMS is started as user with login `root` and uid `1`
> > > > >
> > > > > *.webm files on my machine are being created as
> > > > >
> > > > > ```
> > > > > -rw-r--r-- 1 root root 80134 Jul 15 11:45
> > > > > TEST_SETUP_4a7fa3f6-e284-4d42-be2c-94309b753a2d.webm
> > > > > ```
> > > > >
> > > > > BTW good option to test recordings would be test recording at
> > > > > following address:
> > > > > https://localhost:5443/openmeetings/hash?app=settings
> > > > >
> > > > > (please use your own server-name/IP+port :)))
> > > > >
> > > > > >
> > > > > >
> > > > > > بتاريخ الجمعة، 14 تموز 2023 في 01:55:43 م غرينتش+3، Maxim
> > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > from mobile (sorry for typos ;)
> > > > > >
> > > > > >
> > > > > > On Fri, Jul 14, 2023, 14:29 Online Use
> > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > >
> > > > > > I definitely did that during installation on KMS on docker. I used
> > > > > > my own data_dir, the change is not needed.
> > > > > >
> > > > > > Still I'm having the recording creation error mentioned before.
> > > > > >
> > > > > >
> > > > > > Maybe you can check with dockerized OM?
> > > > > > Does it works for you?
> > > > > >
> > > > > > Usually recordings works as expected if there are no permission
> > > > > > issues :(
> > > > > >
> > > > > > Additionally you can try to enter running KMS docker
> > > > > > And try to write to data dir using same user who started KMS
> > > > > > And check the result in real folder
> > > > > >
> > > > > >
> > > > > > Could it be a bug in this version of OM?
> > > > > >
> > > > > >
> > > > > > بتاريخ الجمعة، 14 تموز 2023 في 06:03:47 ص غرينتش+3، Maxim
> > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > >
> > > > > >
> > > > > > On Fri, 14 Jul 2023 at 02:54, Online Use
> > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > > >
> > > > > > > The hibernate folder path is:
> > > > > > >
> > > > > > > /home/website_home/data_dir/streams/hibernate/
> > > > > >
> > > > > > In such case docket should have parameter: `-v
> > > > > > /home/website_home/data_dir:/home/website_home/data_dir`
> > > > > > So both will write the same folder
> > > > > >
> > > > > > >
> > > > > > > My comment regarding the installation guide before wasn't related
> > > > > > > to syntax, but was related to your recommendation to move the
> > > > > > > data_dir under docker, because this was not mentioned in the
> > > > > > > installation guide althought they used docker to install KMS.
> > > > > > >
> > > > > >
> > > > > > @Alvaro maybe you can add data_dir mapping for the dockerized KMS to
> > > > > > user guide? :)
> > > > > >
> > > > > > >
> > > > > > > بتاريخ الثلاثاء، 11 تموز 2023 في 05:44:34 ص غرينتش+3، Maxim
> > > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > > >
> > > > > > >
> > > > > > > On Tue, 11 Jul 2023 at 02:23, Online Use
> > > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > > > >
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > You said that *.webm file is being written by KMS and being
> > > > > > > > used as source while creating recording file, but I see the
> > > > > > > > recording .wav files under the "streams/9/" folder are already
> > > > > > > > created,
> > > > > > >
> > > > > > > If I remember correctly *.wav files are generated using
> > > > > > > silence.wav in
> > > > > > > case of any problem ....
> > > > > > >
> > > > > > > Could you share full path for the hibernate folder please?
> > > > > > >
> > > > > > > > meaning that the .webm files have been there is the "hibernate"
> > > > > > > > folder and have been consumed to create the final recording
> > > > > > > > files and then deleted afterwards. So the problem is neither
> > > > > > > > with the data directory location nor with permissions, the
> > > > > > > > problem is with the recorded files themselves, recording error,
> > > > > > > > the .wav files are there with data, but only blan screen. May
> > > > > > > > be mal-formated?
> > > > > > > >
> > > > > > > > What do you think?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > بتاريخ الاثنين، 10 تموز 2023 في 05:25:34 م غرينتش+3، Maxim
> > > > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, 10 Jul 2023 at 19:33, Online Use
> > > > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > > > > >
> > > > > > > > > In the installation guide, Kurento is installed inside docker
> > > > > > > > > using this command:
> > > > > > > > >
> > > > > > > > > sudo docker run -d --name kms -p 8888:8888 --mount
> > > > > > > > > type=bind,source=/opt/om_data,target=/opt/om_data
> > > > > > > > > kurento/kurento-media-server
> > > > > > > > >
> > > > > > > >
> > > > > > > > I have to mention:
> > > > > > > >
> > > > > > > > 1)
> > > > > > > > `--mount type=bind,source=/opt/om_data,target=/opt/om_data`
> > > > > > > > and
> > > > > > > > `-v /opt/om_data:/opt/om_data`
> > > > > > > > are the same option :) (I'm just using shorter syntax :)))
> > > > > > > >
> > > > > > > > 2) I read the installation guide long time ago, but never
> > > > > > > > follow (The
> > > > > > > > guide is super clear and saves lots of time to many many users
> > > > > > > > :))
> > > > > > > > I'm developing OM for ~10 years so I don't need guide ;)
> > > > > > > >
> > > > > > > > (my command contains local DATA_DIR I'm using during
> > > > > > > > development)
> > > > > > > >
> > > > > > > > 3) In your original email you cut the real paths:
> > > > > > > >
> > > > > > > >streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav
> > > > > > > > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm
> > > > > > > > .....
> > > > > > > > So I can't guess what are your full paths :(
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > I just did the same during installation.
> > > > > > > > >
> > > > > > > > > It seems that you are trying to change the source and target
> > > > > > > > > directory values after installation using the command that
> > > > > > > > > you mentioned in your reply below, but I don't understand to
> > > > > > > > > where are the paths in your command referring? are these
> > > > > > > > > supposed to be the old om_data directory paths?
> > > > > > > > >
> > > > > > > >
> > > > > > > > By default OM uses DATA_DIR inside the folder it was extracted
> > > > > > > > to
> > > > > > > > it is good idea to use **external** DATA_DIR in production,
> > > > > > > > this way
> > > > > > > > you will NOT need to copy/paste lots of binary data during
> > > > > > > > upgrades :)
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > بتاريخ الاثنين، 10 تموز 2023 في 02:09:41 م غرينتش+3، Maxim
> > > > > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, 10 Jul 2023 at 18:06, Online Use
> > > > > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > > > > > >
> > > > > > > > > > I set the permission of the data directory recursively as
> > > > > > > > > > 777 so that it's writable by all users. I tested but got
> > > > > > > > > > same errors.
> > > > > > > > >
> > > > > > > > > Another point: DATA_DIR should be mapped inside docker
> > > > > > > > >
> > > > > > > > > Here is the example:
> > > > > > > > > ```
> > > > > > > > > docker run -it -v
> > > > > > > > > /home/solomax/work/openmeetings/kms/etc-kurento:/etc/kurento
> > > > > > > > > -v
> > > > > > > > > /home/solomax/work/openmeetings/data:/home/solomax/work/openmeetings/data
> > > > > > > > > --network host kurento/kurento-media-server:7.0.0 bash
> > > > > > > > > ```
> > > > > > > > >
> > > > > > > > > this way KMS will write to the correct folder :)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Different users affect anything other than directory access
> > > > > > > > > > permissions?
> > > > > > > > > >
> > > > > > > > > > How can I check and change the users? I installed
> > > > > > > > > > everything using root already.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > running as root not very wise from security perspective of
> > > > > > > > > view ....
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > بتاريخ الاثنين، 10 تموز 2023 في 01:58:11 م غرينتش+3، Maxim
> > > > > > > > > > Solodovnik <solomax...@gmail.com> كتب:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, 10 Jul 2023 at 17:17, Online Use
> > > > > > > > > > <foronlineuseem...@yahoo.com> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Thank you so much Maxim, it worked perfectly, I just
> > > > > > > > > > > needed to change the port number in Kurento conf file.
> > > > > > > > > > >
> > > > > > > > > > > Now I tested recording and it shows some error. The data
> > > > > > > > > > > directory path is correct, folders exist and their
> > > > > > > > > > > permission is 750. I found a recording file but blank
> > > > > > > > > > > screen, with size exceeding 3MB.
> > > > > > > > > > >
> > > > > > > > > > > I checeked the error trace, and I see the following
> > > > > > > > > > > notices:
> > > > > > > > > > >
> > > > > > > > > > > process: generate MP4
> > > > > > > > > > > - hibernate folder is empty
> > > > > > > > > > > - The recording file name is:
> > > > > > > > > > > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f_FINAL_WAVE.wav,
> > > > > > > > > > > but the error trace refers to file which doesn't exist:
> > > > > > > > > > > streams/9/rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm:
> > > > > > > > > > > No such file or directory
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I believe the issue is in
> > > > > > > > > > "rec_6_962a4647-ae73-4fc7-afda-3c5897b5925f.webm: No such
> > > > > > > > > > file or
> > > > > > > > > > directory"
> > > > > > > > > > This is most probably is caused by the fact KMS and OM are
> > > > > > > > > > started
> > > > > > > > > > using different users
> > > > > > > > > >
> > > > > > > > > > `*.webm` file is being written by KMS and being used as
> > > > > > > > > > source while
> > > > > > > > > > creating recording file
> > > > > > > > > > Both KMS and OM should be started by the same user (might
> > > > > > > > > > be tricky
> > > > > > > > > > with dockerized KMS)
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > process: generate preview PNG
> > > > > > > > > > > -
> > > > > > > > > > > streams/hibernate/79c499c1-ca69-4871-a82e-5f4229668698.mp4:
> > > > > > > > > > > No such file or directory
> > > > > > > > > > >
> > > > > > > > > > > I think the problem is something related to the hibernate
> > > > > > > > > > > folder, but it exists and with permission 750.
> > > > > > > > > > >
> > > > > > > > > > > What do you think?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > بتاريخ الاثنين، 10 تموز 2023 في 11:37:50 ص غرينتش+3،
> > > > > > > > > > > Maxim Solodovnik <solomax...@gmail.com> كتب:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hello,
> > > > > > > > > > >
> > > > > > > > > > > On Sun, 9 Jul 2023 at 15:55, Online Use via user
> > > > > > > > > > > <user@openmeetings.apache.org> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hello,
> > > > > > > > > > > >
> > > > > > > > > > > > I installed this version, and it opens correctly, the
> > > > > > > > > > > > KMS is installed and started correctly under docker,
> > > > > > > > > > > > but when I try to turn on the mic or webcam it shows an
> > > > > > > > > > > > error message "Multimedia server is inaccessible".
> > > > > > > > > > > >
> > > > > > > > > > > > What could be possible reasons for this error message?
> > > > > > > > > > >
> > > > > > > > > > > OM trying to connect to KMS using 127.0.0.1:8888
> > > > > > > > > > > Can you confirm both started at the same physical machine
> > > > > > > > > > > and KMS is
> > > > > > > > > > > listening at 127.0.0.1:8888 ?
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > بتاريخ الخميس، 11 أيار 2023 في 04:43:49 ص غرينتش+3،
> > > > > > > > > > > > Maxim Solodovnik <solo...@apache.org> كتب:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > The Apache OpenMeetings project is pleased to announce
> > > > > > > > > > > > the release of Apache OpenMeetings 7.1.0.
> > > > > > > > > > > > The release is available for download from
> > > > > > > > > > > > https://openmeetings.apache.org/downloads.html
> > > > > > > > > > > >
> > > > > > > > > > > > OpenMeetings provides video conferencing, instant
> > > > > > > > > > > > messaging,
> > > > > > > > > > > > white board, collaborative document editing and other
> > > > > > > > > > > > groupware tools.
> > > > > > > > > > > > It uses API functions of Kurento Media Server for
> > > > > > > > > > > > Remoting and Streaming.
> > > > > > > > > > > >
> > > > > > > > > > > > Release 7.1.0, provides following improvements:
> > > > > > > > > > > >
> > > > > > > > > > > > IMPORTANT: Java 17 and KMS 6.18.0+ are required
> > > > > > > > > > > >
> > > > > > > > > > > > Security:
> > > > > > > > > > > > * Invitation hash check made strict
> > > > > > > > > > > > * Set of user permissions is fixed
> > > > > > > > > > > > * Paths entered in Admin->Config are being verified
> > > > > > > > > > > > * All dependencies are updated with most recent versions
> > > > > > > > > > > >
> > > > > > > > > > > > Stability:
> > > > > > > > > > > > * TURN server config is passed to the client
> > > > > > > > > > > >
> > > > > > > > > > > > ***3 security vulnerabilities were addressed***
> > > > > > > > > > > >
> > > > > > > > > > > > Some other fixes and improvements, 12 issues were
> > > > > > > > > > > > addressed
> > > > > > > > > > > >
> > > > > > > > > > > > Readme:
> > > > > > > > > > > > https://github.com/apache/openmeetings/blob/7.1.0/README.md
> > > > > > > > > > > >
> > > > > > > > > > > > Changelog:
> > > > > > > > > > > > https://github.com/apache/openmeetings/blob/7.1.0/CHANGELOG.md
> > > > > > > > > > > >
> > > > > > > > > > > > List of fixed issues:
> > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312720&version=12352896
> > > > > > > > > > > >
> > > > > > > > > > > > For more information on Apache OpenMeetings please
> > > > > > > > > > > > visit project home
> > > > > > > > > > > > page: https://openmeetings.apache.org
> > > > > > > > > > > >
> > > > > > > > > > > > Apache OpenMeetings Team
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Best regards,
> > >
> > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Maxim
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Best regards,
> > > > > > > > > > Maxim
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best regards,
> > > > > > > > > Maxim
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best regards,
> > > > > > > > Maxim
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > > Maxim
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best regards,
> > > > > > Maxim
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Maxim
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Maxim
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
>
> --
> Best regards,
> Maxim
--
Best regards,
Maxim
