Open Realtime.
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.
Open Realtime.
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.
Now that Firefox Beta has WebRTC enabled by default, it was time to upgrade the WebRTC audio/video demo to support Firefox. Even though changes were minimal and I could do Firefox<->Firefox as well as Chrome<->Firefox, there is still an outstanding issue that is a show stopper for me.
Firefox does not yet support trickle ICE candidates and consequently does not work with Jingle Relay Nodes. This means we cannot use Openfire to act as a media bridge and relay media when both WebRTC peers cannot connect directly with each other as we can do with Chrome.
I am hoping this will be fixed before formal release in June. In the meantime, you can test it at http://redfire.4ng.net/webrtc. Just make sure you have Firefox beta or latest Chrome browsers. As usual, source code is attached for those curious to see or reuse in their own applications.
The Ignite Realtime community is happy to announce the latest release of Smack (version 3.3). It is now available for download. There have been a large number of issues addressed for this release, including new functionality with support for several more protocol extensions (XEP's) and many improvements on existing features.
New Features
- [SMACK-331] - Add support for XEP-0184: Message Delivery Receipts
- [SMACK-345] - Inproved detection of last activity
- [SMACK-361] - Add support for XEP-0115 Entity Capabilities
- [SMACK-376] - Setting a custom trust manager to control certificates from outside
- [SMACK-388] - XEP-199 XMPP Ping support
In addition to these, there have been many bugs fixed and a variety of other tasks done, the complete listing can be viewed here.
A new version of the Jappix plugin for Openfire is available with support for WebRTC restored back. It only supports Chrome version 26+ and is compatible with the WebRTC plugin for Spark. It uses The Openfire JingleNodes plugin for media relaying via Openfire server when WebRTC peers can connect directly with each other.
Video Chat
Group Video Chat
How to use
Click on the webcam icon to share video in an active chat/groupchat.
With chats, the other party receives a prompt to share their audio/video.
Groupchat does not prompt and auto shares audio and video with all participants.
For those following the use of Openfire for audio and video communication, The Jitsi project released very recently, the . If you use Jitsi with Openfire, you find it very useful for creating both audio and video conferences with multiple people. I am hoping someone will try and make a Spark plugin for it 
In the meantime, I did a quick experiment to see if I could convert the Redfire plugin for Spark to use WebRTC instead of RTMP/RTMFP
Guess what!!. It worked 
It works the same way as the Redfire plugin for Spark. Click on the webrtc button to share audio and video with the person you are chatting with. On the other side, that person will receive a prompt to accept or reject the offer.
So here it is attached, if you want to play with it. It does not depend on any Openfire plugin, but will use the JingleNodes plugin if available to relay WebRTC audio/video media when a direct connection cannot be made between two Spark clients..
It needs Google Chrome version 26+ running on the client desktop as the default browser. It supports Google Chrome frame for Internet Explorer. The source code is in there as well. When Firexfox WebRTC support becomes stable, I will probably add support for that too.
*** UPDATE ***
I finally got multi-user video conferencing working in group chat like Redfire. Please note that there is no prompt. Each participant MUST click on the webrtc button to join the video conference and the plugin ensures a webrtc peer-connection is made between each and every participant. This should be done after everyone joins the groupchat.
If a new person enters the room and wishes to join the video-conference, each participant should close their browser windows and click on the webrtc button again.
Chrome version 26 stable and Firefox (Nightly build) now support full desktop screen sharing. In Chrome, you have to enable "Enable screen capture support in getUserMedia()" with the chrome://flags URL.
As the desktop screen is treated as a video device, you only have to make a change to the getUserMedia method for video and your existing application will work with no further changes. As an example, I only made the following change to my webrtc video example and now it allows two users to share their desktop screens
navigator.webkitGetUserMedia(
{video:{mandatory: {chromeMediaSource: 'screen'}}},
this.onUserMediaSuccess.bind(this),
this.onUserMediaError.bind(this)
);
To see it in action, just click on this URL https://webrtc.free-solutions.org:8443/webrtc/screen.html from two different PCs. Register with two different user names (no spaces or special characters).
It is hosted by the very good kind and generous folks at free-solutions.org
Recent Discussions
LambdaDriver in
"LDAP Connection pooling not working"
KPCA in
"
gerkoe in
"
workino in
"SIP Phone server port"
xmpprcl in
"Re: How to send custom response"