Package Details: jitsi-videobridge-git r3063.a4bfc7f2-2

Git Clone URL: https://aur.archlinux.org/jitsi-videobridge-git.git (read-only, click to copy)
Package Base: jitsi-videobridge-git
Description: Videobridge for Jitsi Meet
Upstream URL: https://github.com/jitsi/jitsi-videobridge
Licenses: Apache
Conflicts: jitsi-videobridge
Provides: jitsi-videobridge
Submitter: fordprefect
Maintainer: fordprefect (C0rn3j)
Last Packager: C0rn3j
Votes: 1
Popularity: 0.135909
First Submitted: 2020-04-22 11:30
Last Updated: 2020-05-27 09:07

Dependencies (3)

Required by (4)

  • jigasi (requires jitsi-videobridge) (optional)
  • jigasi-git (requires jitsi-videobridge) (optional)
  • jitsi-meet (requires jitsi-videobridge) (optional)
  • jitsi-meet-git (requires jitsi-videobridge) (optional)

Sources (6)

Latest Comments

1 2 Next › Last »

archtom commented on 2020-04-26 14:08

Just sent you the email. Let me know if it worked ;)

And I did not get the link to the new config file path and options. Would be nice if you could include it in the email answer ;) Thanks

C0rn3j commented on 2020-04-26 10:23

If you'd mail me the migration steps(my mail is public here) that'd be great (and the install script if you will, extra info won't hurt), my current setup is based on the manual-install.md doc which is JVB1 based.

I'll PR to that doc when I get the changes running unless you've plans to do that yourself already.

where the file is located and where all names of the possible options are documented

The doc I just linked to has the JVB options and how to apply the file (though I haven't figured out a way to make jvb.sh use it cleanly)

archtom commented on 2020-04-26 06:45

Yes, I have it working after a lot of hiccups. Shall I describe you the changes that I made from jvb1 to jvb2 here or shall I send you an email? I have an install script with the current working configuration. But it's still work in progress.

The now recommended way is to switch the videobridge from component to muc (changes to prosody, videobridge and jicofo needed), disable xmpp api in in the videobridge config file and specify the path to the sip communicator file in the videobridge config file. After doing all that it's working.

I did not switch to the new config scheme yet (https://github.com/jitsi/jitsi-videobridge/blob/master/doc/muc.md). I'm still using the sip communicator file because I don't know how to specify all options (for behind nat usage) with the new scheme. If anyone knows how to switch to the new scheme (where the file is located and where all names of the possible options are documented) I would be happy to know ;))

I'm using a config with only one domain with auth only, no public or guest.

C0rn3j commented on 2020-04-26 01:27

Did anyone actually manage to make JVB2 work?

It seems that the manual-install doc is made for JVB1, and simply installing JVB2 with setup for JVB1 does not work (calls using 3+ participants instantly crash).

There seem to be some config changes - https://github.com/jitsi/jitsi-videobridge/blob/master/CONFIG.md#configuration-sources

JVB2 does not seem to bind on 443/4443 for me, which is probably why it crashes in my setup.

archtom commented on 2020-04-25 14:18

@fordprefect: o.k., thanks, until you get feedback from upstream I will build my own stable packages locally with my modified PKGBUILDs based on yours.

archtom commented on 2020-04-25 14:16

@C0rn3j and @fordprefect: Thanks for your feedbacks. "In-between" was misleading. According to multiple forum entries and the releases to their stable debian branch jvb2 is considered stable.

And as mention by C0rn3j the whole development and stable releases of jitsi-meet and jicofo rely on jvb2. All their configuration recommendations (using videobridge as muc, not as component) does only work on jvb2 for me.

And C0rn3j uses jvb2 for his stable jitsi-videobridge-bin release, too.

To follow their stable releases use the provided link https://download.jitsi.org/stable/.

As all the components seem to be under heavy development I would prefer to use "stable" jvb2 instead of git.

I think it is necessary to follow the stable releases of all components to keep them work together. That's why it's my suggestion to build the latest stable jvb2 from GitHub adding the stable commit. That what was what I meant with in-between, sorry for the confusion.

fordprefect commented on 2020-04-25 11:46

@archtom: in-between is not stable, at least not from my point of view. For the other packages, I saw your comments but will wait for upstream to communicate their stategy and only then change the packages.

C0rn3j commented on 2020-04-25 11:38

JVB packaging is kind of a mess right now, current JVB stable release doesn't even work against git jicofo.

You can follow this issue about it - https://github.com/jitsi/jitsi-videobridge/issues/1224, I'll bump up jitsi-videobridge the moment there's a new stable release (which I guess will be based on JVB2)

archtom commented on 2020-04-25 11:06

o.k., thanks for the feedback. So I meant something in-between. On their website https://download.jitsi.org/stable/ they consider certain jvb2 versions as stable and it would be nice to have a package for that.

It would be nice if you could also have a look at the comments for the jitsi-meet and jifoco packages, add the changes and revert to stable, too.

Thanks a lot. Have a great weekend ;)

fordprefect commented on 2020-04-25 10:22

The purpose of a git package is building from developement tip. Don't use a -git package if you want the latest stable version! As soon as there is a stable videobridge version 2.x, the stable package will reflect that. Until that, there is no "stable jvb2". EDIT: also, please note: for me it is still completely unclear what upstream considers "stable", thus there is a support request open and once we get a response, the packages will be changed to reflect that.