[jitsi-users] Confusion about the jabber server to use for jitsi


#1

Hi,

I wanted to use jitsi videobridge and meet together with an existing
ejabberd installation

On https://jitsi.org/Projects/JitsiVideobridge there's instructions to
install videobridgh for two jabber servers, ejabberd and openfire.

But when I install jitsi-meet through the jitsi ubuntu packages,
ejabberd wouldn't start since the ports are occupied by prosody, which
jitsi-meet automatically pulls in, although the network scheme in

https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

does not show a direct link between meet and a jabber server, but a
link between videobridge and prosody, although videobridge is intended
to be used with ejabberd or openfire.

The jitsi-meet package depends on jitsi-meet-prosody and
jitsi-videobridge, and jitsi-meet-prosody depends on prosody.

Does this effectively mean, that jitsi can be used with prosody only?
If so, what's the point in the installation instructions for ejabberd
and openfire?

thanks and regards
Hadmut


#2

Pasting my answer to the same questions with little update:

Hi,

The package you install jitsi-meet is a meta package and consist of
various components in order for users to install using a single
command and at the end have a working conference solution. These
dependencies consist of a web application, a way to serve it nginx,
apache2 or jetty from jvb, a video bridge, a controlling component
called jicofo and a XMPP server that connects them all which we chose
back in time and is prosody.
If you want to customize this solution you can install separate
packages and configure them one by one. You can use your web server
and your XMPP server and install just jitsi-meet-web,
jitsi-videobridge and jicofo.
A PR for configuring different XMPP servers in the system is welcome.

The instructions for ejabberd and videobridge are from the times when
jitsi-meet was not existing and jitsi-videobridge was used with jitsi
desktop client for conferences.

Regards
damencho

···

On Mon, Apr 10, 2017 at 9:20 AM, Hadmut Danisch <hadmut@danisch.de> wrote:

Hi,

I wanted to use jitsi videobridge and meet together with an existing
ejabberd installation

On https://jitsi.org/Projects/JitsiVideobridge there's instructions to
install videobridgh for two jabber servers, ejabberd and openfire.

But when I install jitsi-meet through the jitsi ubuntu packages,
ejabberd wouldn't start since the ports are occupied by prosody, which
jitsi-meet automatically pulls in, although the network scheme in

https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

does not show a direct link between meet and a jabber server, but a
link between videobridge and prosody, although videobridge is intended
to be used with ejabberd or openfire.

The jitsi-meet package depends on jitsi-meet-prosody and
jitsi-videobridge, and jitsi-meet-prosody depends on prosody.

Does this effectively mean, that jitsi can be used with prosody only?
If so, what's the point in the installation instructions for ejabberd
and openfire?

thanks and regards
Hadmut

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#3

Damian,

thanks for the hints.

One more question:

If you want to customize this solution you can install separate
packages and configure them one by one. You can use your web server
and your XMPP server and install just jitsi-meet-web,
jitsi-videobridge and jicofo.

This collides with the fact that the package jitsi-videobridge
occupies port 443 with a java server running
org.jitsi.videobridge.Main

Again, based on
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
the videobridge should not occupy port 443, and leave it for the web
server (nginx in this case).

Can you hint me again why the videobridge package ?

regards
Hadmut

···

On Mon, Apr 10, 2017 at 10:38:11AM -0500, Damian Minkov wrote:


#4

Hi,

Damian,

thanks for the hints.

One more question:

If you want to customize this solution you can install separate
packages and configure them one by one. You can use your web server
and your XMPP server and install just jitsi-meet-web,
jitsi-videobridge and jicofo.

This collides with the fact that the package jitsi-videobridge
occupies port 443 with a java server running
org.jitsi.videobridge.Main

This is a default behavior. If you are installing on a system that has
java8 and doesn't have apache2 or nginx installed, jitsi-videobridge
is configured to serve meet. This way jitsi-videobridge uses port 443
for both, serving content and also for tcp media connections. Using
443 for media is sometimes needed as a fallback for restricted
corporate networks.

There are a couple of options, like install jvb on a separate machine
and connect it to the XMPP server, or do not use that option and leave
jvb use the other default port for media over tcp, which is 4443. Use
the same machine but use two ip addresses there, one for content and
one for jvb.

Those configurations about configuring how to serve web content are
managed by package jitsi-meet-web-config, if you are installing
separate packages this will not be used.

Regards
damencho

···

On Tue, Apr 11, 2017 at 10:16 AM, Hadmut Danisch <hadmut@danisch.de> wrote:

On Mon, Apr 10, 2017 at 10:38:11AM -0500, Damian Minkov wrote:

Again, based on
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md
the videobridge should not occupy port 443, and leave it for the web
server (nginx in this case).

Can you hint me again why the videobridge package ?

regards
Hadmut


#5

Scary...really scary...

···

On Tue, Apr 11, 2017 at 10:30:36AM -0500, Damian Minkov wrote:

This is a default behavior. If you are installing on a system that has
java8 and doesn't have apache2 or nginx installed, jitsi-videobridge
is configured to serve meet.