Skip navigation
All Places > Ignite Realtime Blog > 2013 > November
2013

The Jitsi project have just announced that Jitsi Videobridge is now compatible with WebRTC and can be used as a central relaying point for web video conferences (or web+Jitsi). You can check out shot of a first prototype here. A big thank you to Emil Ivov,  Philipp Hancke (estos.de) and Lyubomir Marinov (jitsi.org) for making this happen and sharing it with the rest of us

 

I was keen to see this in action with Openfire as Jitsi Videobridge works fine as an Openfire plugin and it will add the much needed and anticipated video streams forwarding/relaying feature to WebRTC applications as Red5 does to Flash Player. I copied all the required files to my Openfire server, made some minor adjustments for Openfire and as you can see below, it works!!

 

Image2.jpg

However it is early days. This is all leading edge code still in development. Jitsi Videobridge as an internal component from an Openfire plugin does not yet work because the bouncycastle library in Openfire needs an upgrade to the latest version that supports DTLS-SRTP. It only worked as an external component. I will try to get this fixed for Openfire 3.9.0 which is currently in alpha.

 

** UPDATE **

 

Jitsi Videobridge plugin for Openfire is now available here at igniterealtime.org with the webrtc-based video conferencing application embedded as a web service. A complete web muti-person video conference solution in one box. You will need Openfire 3.9.0 to try it out.

 

In the meantime, Claude Stabile has generously made a live version available for us to try at https://webrtc.free-solutions.org:8443/videobridge.html

 

** FURTHER UPDATE **

 

The first draft of the COnferences with LIght BRIdging (Colibri) XEP that is used to manage video conferences with Jitsi Videobridge is now out. You can find it here. All we need now is a volunteer to setp forward and add it to Smack/aSmack and Spark using the Java bells library

 

** YET MORE UPDATE***

 

The first version of the Jitsi jitmeet web conferencing application is now out and has replaced the demo web application in the Jitsi Videobridge plugin. It has MUC chat with some other needed features like mute audio/video. Expect some more before Openfire 3.9.0 is released. As usual, you can checkout the latest code in the ignite realtime VCS, build and try it out yourself.

 

To help those cannot build openfire 3.9.0 from source. Do the following

 

Grab Openfire 3.9.0 nightly build from here

Download jitsivideobridge.jar file from here

Image2.jpg

 

** LAST UPDATE **

 

There is now a dedicated ignite space for jitsi-videobridge plugin. Please post any issues, questions and contributions here. I have also posted a blog about the changes I have made to the plugin to support a server-side focus agent.

As many know, there has been a push in the community to move our VCS from subversion to git.  I agree with them that it is time to make that move, and I hope the other contributors and especially the project leads will get on board. I had reservations about making this move myself, not so much specific to git itself, but for the fact that I didn't think that it offered enough advantage over the cost of actually doing the move due to the limited resources available.  If we were all paid to do this kind of work, these issues simply wouldn't exist.  It isn't simply switching version control, but the interactions between that and the existing infrastructure (Jira and Bamboo) and the like and also implementing new software, build and release processes.

 

With regards to the software development process, this is where git, or more specifically, some of the available management tools for git really shine. They add more than enough value to the process that I think we should adopt them.

 

So, I am proposing that we get and set up Atlassian Stash (the enterprise version of BitBucket).  It has excellent integration with the existing development tools we are using and will provide a much better software development and management process then we currently have (which admittedly isn't that hard).

 

  • Branches can be linked to their Jira tickets.
  • Code review of a pull request will automatically update a Jira ticket to code review status.
  • Accepting a pull request will update the status to resolved.
  • Configure builds to automatically build any branch.
  • Force merge of pull request to require a successful build before allowing a merge.
  • Inline code reviews
  • Would allow private repos
  • Can be branded to Igniterealtime

 

From what I know, the feature set is very similar to Github, but I don't know where Github stands with respect to Jira and Bamboo integration. I am sure the build server has no issues either way with simply building the code base, but I have no idea if it offers any actual integration the other way around.

Filter Blog

By date: By tag: