public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Technical Issues with yesterday's Video Conference
Date: Tue, 07 Dec 2021 15:32:13 +0000	[thread overview]
Message-ID: <2C9F2597-F159-483D-91D7-D5C5FE403874@ipfire.org> (raw)
In-Reply-To: <183ceb7f-b093-2863-4c56-cde5bd40c61f@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]

Hello,

I installed all updates that were available in the Jitsi repository and rebooted the server.

It might have been just that. Did all your clients have full access to the internet or have you been behind a proxy/firewall that was restricting access?

-Michael

> On 7 Dec 2021, at 12:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 07/12/2021 12:20, Michael Tremer wrote:
>> Hello,
>> 
>> I would like to apologise to the people who could not join the video call yesterday.
>> 
>> To make it short: I do not know why, but I think we seriously need to find out why this has happened.
>> 
>> We had a couple of people on the call who did not have any problems joining - even with multiple devices.
>> 
>> Then others could not see or hear a thing, which I would blame on the endpoint device, but Adolf tried multiple different ones and I do not believe that they are all suddenly broken at the same time.
>> 
>> Could you guys try to set up a video call with yourself and check if the problem persists?
> 
> I just gave it a try using my laptop and tablet, two of the three devices I tried yesterday. The video call worked fine. I had video and audio (quickly muted both ends with the feedback) but I had a perfectly working video connection where I could see both sides on both devices.
> 
> So not sure what happened yesterday but today it is working without problems.
> 
> Regards,
> 
> Adolf.
> 
>> You can just go to https://jitsi.ipfire.org and create a random room, then log in and hopefully you should at least see yourself. Joining from another browser tab or another device should work too.
>> 
>> If this fails, please let me know what you can find.
>> 
>> Best,
>> -Michael
> 
> -- 
> Sent from my laptop
> 


  reply	other threads:[~2021-12-07 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 11:20 Michael Tremer
2021-12-07 12:58 ` Adolf Belka
2021-12-07 15:32   ` Michael Tremer [this message]
2021-12-07 16:38     ` Adolf Belka
     [not found] <CAGGyJTrNoTpULH1g8vGNxHeJ2J4RC9atMUffVodCibn_tUgtdw@mail.gmail.com>
2021-12-07 12:08 ` Michael Tremer
2021-12-07 12:15   ` Michael Tremer
     [not found] <CAGGyJTq9T3cpRRogOQCnajrc-5pD3-nv7hnsBKTVUvfgVZvdUw@mail.gmail.com>
2021-12-07 12:26 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2C9F2597-F159-483D-91D7-D5C5FE403874@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox