powered by Jive Software

Jitsi Videobridge Openfire Plugin

Hi all,

Jitsi Videobridge is an XMPP server component that allows for multiuser video communication. Unlike the expensive dedicated hardware videobridges, Jitsi Videobridge does not mix the video channels into a composite video stream, but only relays the received video channels to all call participants. More info can be found at https://jitsi.org/Projects/JitsiVideobridgehttp://jitsi.org/videobridge

Jitsi Videobridge can work either as a standalone component or and as an openfire plugin. The openfire plugin can be downloaded at:


The plugin uses libjitsi (http://jitsi.org/libjitsi) which, on the other hand, depends on some native libraries for implementing codecs for mixing the audio. Therefore, the plugin is bundled with native libs for each of the supported platforms. At the first run it checks whether those libs are present and, if missing, extracts them under plugin’s folder (/var/lib/openfire/plugins/jitsivideobridge/lib/native/;). Then at each subsequent run only java.library.path is modified.

Does this sound ok?

It would be good if someone could make an attempt to develop a Spark plugin for it.

Problem is that the COLIBRI XMPP extension protocol it uses is not yet published

It would be good if someone could make an attempt to develop a Spark plugin for it.

Oh yes that would be cool! This would mean that someone would first need to make sure Spark can handle video calls with multiple video streams (i.e. SSRCs) in an RTP session, but that would come for free if it uses libjitsi

Problem is that the COLIBRI XMPP extension protocol it uses is not yet published

Oh, you really shouldn’t consider this to be a problem. The COLIBRI protocol is extremely simple, kind of like Jingle Nodes, and you can see how it works by only looking at the logs.

Of course, reading a spec is always easier and we’ll definitely publish this at some point (the only constraint currently being time … or lack thereof) but If someone starts working on that let us know and we’ll make sure we have a neat XEP for you guys to read.

Hello Emil, I forgot you walk around these grounds

I did take a look at the openfire xmldebbuger logs to see if I could reverse-engineer the protocol after doing a video-bridge session between Jitsi on my mac and pc. It does look simple enough, but there was not enough information to develop something tangible in a short window of opportunity without the XEP. So if you have a draft version for us here at igniterealtime, it would help to get the project moving.

I did get started on replacing the phono media in the Spark Jitsi-Jingle plugin with libjitsi, but ran into an JMF issue that would require some changes from the core Spark team. I am not currently free to follow up on this and would love if someone else would like to follow through on making Jitsi-Jingle Spark plugin work with libjitsi and implement COLIBRI.

Please, please let us know as soon as libjitsi supports webrtc. I get more requests for audio/video with webrtc web applications rather than a Java desktop application like Spark.

Please, please let us know as soon as libjitsi supports webrtc

We definitely will! Shouldn’t be very long … hoping for the summer


If you get this error in the log files

java.lang.IllegalStateException: net.java.sip.communicator.SC_HOME_DIR_LOCATION

** at org.jitsi.impl.fileaccess.FileAccessServiceImpl.(FileAccessServiceImpl.ja va:53)**

** at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)**

** at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)**

** at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)**

** at java.lang.reflect.Constructor.newInstance(Unknown Source)**

Then these two lines in initializePlugin (PluginImpl.java) should fix that

System.setProperty(“net.java.sip.communicator.SC_HOME_DIR_LOCATION”, pluginDirectory.getPath());

System.setProperty(“net.java.sip.communicator.SC_HOME_DIR_NAME”, “.”);


Which way is better to contact with jitsi-videobridge openfire plugin developers?

Hi Dmitry, just send an email to dev@jitsi.org.

I’d sure love to be able to find a howto on installing this plugin… Currently, I’ve uploaded the v37 (also tried v32) via the plugins page, on Debian Wheezy with OF 3.8.2 / 1.7.0_25 Oracle Corporation – Java HotSpot™ Server VM, and all I get in the Server Settings is a new sub-menu called “plugin.title” with nothing underneath. There is NO documentation that I’ve been able to find on getting it fixed, and I do NOT get the error shown above in the logs, nor can I find the file to be edited…

Sure be nice to have a walk-thru or howto by someone who’s successfully gotten it installed and config’d…


the same happens to me even if I’m under Postgres 9.2 DB. I’m trying the bridge separately without the plugin as described here:




Damencho, I am trying to get Jitsi set up on my Openfire server.

Here are my settings for Server Settings, HTTP Bind:

  • HTTP Bind Settings is Enabled for port 7070 (7443 for SSL)

  • Script Syntax is Enabled

External Component Settings:

  • Port 5275
  • Default shared secret is 1a0c6e21

In Plugins, the Jitsi Video Bridge is installed (version 1.0).

However, nothing comes up in Sessions, Component Sessions .

Also, I do not see a ‘Jitsi Videobridge’ tab under Server settings (as indicated by the plugin’s info) to configure Jitsi.

What would I need to do to test Jitsi ? Do I need to reinstall the Jitsi Video Bridge plugin?

As others mentioned in this forum, I also have the plugin.title tab which is completely blank.

Thanks !

Giorgio, did you get yours working? If so, please point out what you did.


http://community.igniterealtime.org/blogs/ignite/2013/11/28/jitsi-videobridge-wi th-openfire-and-webrtc


i simply used the windows binary servicing it and connecting as external component. The plugin simply did not work at least when I tried it.

The plugin requires Openfire 3.9.0

Dele, I see that there are still some issues with Openfire 3.9.0:

http://issues.igniterealtime.org/browse/OF/fixforversion/12036#selectedTab=com.a tlassian.jira.plugin.system.project%3Aversion-issues-panel

Do you know when there are plans to release it?