Ignite Realtime is the community site for the users and developers of Jive Software's open source Real Time Communications projects. Your involvement is helping to change the open RTC landscape.
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!!
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 getwhich 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
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).
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.
The Ignite Realtime community is happy to announce the latest release of Smack (version 3.3.1). It is now available for download. This is a minor release and there have been a few bug fixes, most importantly, the memory leak in the keep alive process and one new feature. This is a partial list of the more important items.
In addition to these, there have been many bugs fixed and a variety of other tasks done, the complete listing can be viewed here.
For anyone following my projects, you would be aware of me using jVoiceBridge as my audio conferencing and VOIP engine with Openfire. I stopping using Asterisk a while back and all my telephony is done with jVoiceBridge and the SIP plugin for Openfire. The combination of Openfire, jVoiceBridge and WebRTC provides a very compact unfied communications solution.
One of the many cool features of jVoiceBridge I was never able to exploit up until now was the spatial audio feature that creates a 3D audio immersion experience from a stereo mix.
What's so cool about this?
As a home worker, I have been dreaming of when I would get to hear the separation of conference participant voices across a stereo field. By adding matching visual sitting postions, speech detection and improved voice quality, we might just get audio-conference calls back in fashion.
What makes this now possible is the use of the OPUS codec in WebRTC. However for a while, it looked like it was going to remain a dream unless I could figure out a way to access WebRTC audio streams directly from an Openfire plugin.
I started out with the source code to the JingleNodes plugin for Openfire and got the WebRTC UDP packets wired into jVoiceBridge conferences. At first, I was limited to 8K mono audio from the PCMU (ulaw) codec, but thanks to the Jitsi project, I was able to add their OPUS decoder/encoder and finally got 48K stereo samples streaming into jVoiceBridge.
I have put together a demo web page of the plugin running on my server. To test, you have to access the same page from at least two PCs in order to test the 3D audio-conferencing effect. It only works with Google Chrome.
It will let you do the following things
The plugin will be an official Openfire plugin and the project will be hosted and supported from Igniterealtime. I am planning on exposing all the features of the plugin through the new Rayo XMPP Extension for remote call control. I hope to develop a Strophe plugin for Rayo to enable easy access from XMPP based web applications.
If you are interested in joining up with me to make this all happen sooner than later, send me an email or private message.
The Igniterealtime servers reside at Contegix ( http://www.contegix.com/ ) thanks to the generous support of Jive Software (http://www.jivesoftware.com ). Between 3-7 UTC on 21 July 2013, the servers will be offline to allow them to be physically moved to a new facility. The actual downtime may be shorter or longer than that period. Please comment on this post if you see degraded services after that period.