Hi Maxim,
thanks for the information.
Today in the morning I succeed to setup everything in connection with
the lms. I needed to add /proxyPort="443"/ to the connector definition
in server.xml.
Greetings Peter
Am 31.03.20 um 11:17 schrieb Maxim Solodovnik:
https://issues.apache.org/jira/browse/OPENMEETINGS-2209
to track progress
On Mon, 30 Mar 2020 at 20:24, Peter Dähn <[email protected]> wrote:
ok.. wait for that... ;-)
Am 30.03.20 um 14:15 schrieb Maxim Solodovnik:
I'll try to add "connection status handling" to the client
So user will be aware of connection-is-not-set state
will take some time
On Mon, 30 Mar 2020 at 19:11, Peter Dähn <[email protected]> wrote:
sorry for that.. :-(
1st user Linux Mint 18.3 Firefox 74.0 (64-Bit) -> was not be heard by
the others -> reload everything was fine
2nd user Firefox 74.0 macOS 10.15 -> could hear and was heard by all
others
3rd Ubuntu 18.04 - Firefox 72.0.2 ->could hear and was heard by all
others
4th FF 74 Linux Mint 19.3 -> was not be heard by the others -> reload
everything was fine
if it is possible with less participants need to be tested...
Am 30.03.20 um 12:58 schrieb Maxim Solodovnik:
This is the report I was always afraid of :((
What OSes/Browsers have you used?
Is the issue reproducible with less participants?
On Mon, 30 Mar 2020 at 17:14, Peter Dähn <[email protected]> wrote:
Hi Maxim,
we were right now at demo next and made a test, because we often here
that people have connection problems, when they enter the room. We can
not find any reason for that. The behaviour seems to be the same on
demo
next.
We were 4 persons in the room. The first and the last one could not be
heard by the others. They need to re-enter the room. Maybe you can
find
something in the logs. We met at 11:20 MEZ in room 4868.
I thought this could be caused by setup, but it seems to be
reproducible. This should be fixed.
Greetings Peter
