Jitsi for Hackweek
a project by rsimai
Updated almost 3 years ago. 13 hacker ♥️. 5 followers.

Primarily to support Hackweek, but also to gain experience for a potential future corporate use, I like to run the open source Jitsi in a SUSE context and within a setup that is close to what SUSE IT is doing.

The service will be built in AWS/EKS within the SUSE E&I space and should be up and running on day 1, but will need love during the 5 Hackweek days to

The team meets in the channel #hackweek-jitsi. It's internally public, feel free to join.

Deployment related configs can be found in the internal GitLab

Everyone using the service should be aware it's a Hackweek project and not supported by IT but a group of volunteers. It is subject to be shut down after Hackweek.

Goals: gain experience and prepare technical details on how to run Jitsi in a SUSE IT compliant environment, to finally approach SUSE IT along with a business case to establish Jitsi as a open source and user friendly conference system alternative to MS Teams.

Join this project

Looking for hackers with the skills:

video audio conference teams jitsi

This project is part of:

Hack Week 20

Activity

  • over 3 years ago: tjyrinki_suse liked this project.
  • over 3 years ago: LKucharczyk liked this project.
  • over 3 years ago: cdywan liked this project.
  • over 3 years ago: okurz liked this project.
  • over 3 years ago: kwk liked this project.
  • over 3 years ago: rlambrecht liked this project.
  • over 3 years ago: jiriwiesner liked this project.
  • over 3 years ago: mkubecek liked this project.
  • over 3 years ago: pvorel liked this project.
  • over 3 years ago: bruclik liked this project.
  • over 3 years ago: rsimai liked this project.
  • over 3 years ago: LSchroeder joined this project.
  • over 3 years ago: SchoolGuy joined this project.
  • over 3 years ago: SchoolGuy liked this project.
  • over 3 years ago: mkoutny liked this project.
  • over 3 years ago: rsimai started this project.
  • over 3 years ago: rsimai added keyword "video" to this project.
  • over 3 years ago: rsimai added keyword "audio" to this project.
  • over 3 years ago: rsimai added keyword "conference" to this project.
  • over 3 years ago: rsimai added keyword "teams" to this project.
  • over 3 years ago: rsimai added keyword "jitsi" to this project.
  • over 3 years ago: rsimai originated this project.


    • Comments

    • rsimai
      over 3 years ago by rsimai | Reply

      Thanks to Enno, Leon and Dirk, the service is up and running in AWS, now with DNS and a letsencrypt certificate, as https://meet.suse.net

    • rsimai
      over 3 years ago by rsimai | Reply

      We're seeing a problem with the Rocket integration. The feature is turned on and Rocket now allows to start a "Call" from the top menu. This opens a browser to Jits for a new session and posts a "Clock to Join" link for other participants. In particular in team chats users see "Call Already Ended", it works better in direct chats.

    • rsimai
      over 3 years ago by rsimai | Reply

      Jitsi's timezone has been changed from CET to UTC to make it match with Rocket. Still there's only a 30 seconds time frame to join, after that Rocket will display "already ended" when people try to join. The issue seems known for a long time but not resolved.

    • rsimai
      over 3 years ago by rsimai | Reply

      We found a problem with the NUE dev network, and likely others. Users from there wouldn't see video or hear audio as there's UDP filtering in place. IT needs to create an exception and that's typically for a certain IP only. But with the AWS setup we can not guarantee the IP to be static. Cloud it is ...

    • mkubecek
      over 3 years ago by mkubecek | Reply

      Thanks a lot for this effort. What a pity it's not used for the official Hackweek activities and all of them are on MS Teams instead.

    • rsimai
      over 3 years ago by rsimai | Reply

      unfortunately we've been too late, and practically the service is still not fully configured (still firewall issues, no own STUN server, no TURN server, ...) so it probably makes more sense to go with a "reliable" solution cough cough

    • rsimai
      over 3 years ago by rsimai | Reply

      To conclude the project, we had to finally shutdown the AWS resources as announced, to not vaporize money into the cloud. We have achieved to have a ready-to-apply config, that's a success! The chat channel remains open for a while, feel free to join there. Thanks to everyone who tried the service and in particular to those who contributed!

    Similar Projects