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.
Latest Blog Entries
Dele Olajide
0

Openfire Meetings Desktop/Screen Sharing using Pd

Screen sharing with Openfire Meetings is a bit tricky no thanks to Google's WebRTC security policy to use Chrome extensions for trust. This means you have to develop a personalised chrome extension to white-list your domain as trusted. I don't use Firefox and consequently have no idea of the user experience.

With Pd version 0.1.13, I have tried to improve the experience as follows:

  • If you use ofmeet from Pd exclusively, then you can screen/desk share from any domain. No extra work involved.

  • If you still use the ofmeet 0.3.x version, then you can use Pd to provide screen/desk-share from any domain as well. You should check "Desktop Share mode only" in the options screen

  • If you are using the ofmeet latest 0.9.x version, then you have to white-list your domain in order for Pd to support it. To do this, you can either raise a PR on the Pd repository at GitHub or raise an issue and I will add it manually. When the next Pd release is made, your domain should be supported.

Please note that your domain name will be exposed. This should not be a problem for a private network, but could expose your server if your domain is on the Internet. In that case, write your own chrome extension for Openfire Meetings or pay someone to do it or simply use Pd :slight_smile:

Tags: 0
daryl herzmann
0

Openfire 4.2.1 Release

The Ignite Realtime Community is thrilled to announce the availability of Openfire 4.2.1. But wait, you may wonder why Openfire 4.2.0 was not announced nor blogged about. The answer is that after a soft release of Openfire 4.2.0, we noticed a number of folks hitting a database schema issue that would cause logins to fail. We decided to turn around a fix for that issue and now fully announce the new release.

So what has changed with Openfire 4.2? A lot! Some highlights:

  • XEP-0237 Roster Versioning
  • Server to Server (s2s) is more robust
  • The websocket functionality, previously in a plugin, was merged into core
  • The Admin Console now has a Pub-Sub administration interface
  • You can now manually test a Server to Server connection on the Admin Console
  • XEP-0198 Client Resumption is now available
  • A lot of polish and new handy functionality was added to the Admin Console
  • Openfire plugin loading is much more robust

The changelog denotes the full listing of Jira issues addressed in this release and 4.2.0.

Here is a listing of sha1sum values for the release binaries, which can be found on our download page.

a038d417784f6d623014ba88013407f3d36792ac  openfire-4.2.1-1.i686.rpm
6c8886834b9b7d2ce6144d7ce23d3e47bbff91bd  openfire-4.2.1-1.noarch.rpm
34bb23661c77b27a37572532fa23a0f8c6459015  openfire-4.2.1-1.x86_64.rpm
8a66b230323a9231dc2aca6ae7288186e56d5315  openfire_4.2.1_all.deb
bcf543c65c1bf22da8c05413646230f30a60b378  openfire_4_2_1_bundledJRE.exe
947ef8ee8c08c527d1c3932bec7ea580b3c08956  openfire_4_2_1_bundledJRE_x64.exe
a4ec386f9eb6cf4078b505ec57d007c799853034  openfire_4_2_1.dmg
922bb44ed7b72b75d781f1091978cb4759575112  openfire_4_2_1.exe
750524d79a18e8c6c38702f980dec961fa102f82  openfire_4_2_1.tar.gz
6d04e462bc7a5b39701d7dd1538c5508bdeff339  openfire_4_2_1_x64.exe
00b6a27057bac2b26ba6084b6606ca1ee449fc18  openfire_4_2_1.zip
e918dfbfcd91d6f0562d20aa0600266db5f855e7  openfire_src_4_2_1.tar.gz
7e82909a7e9a55ed71483b054e61d0ec95b0cccf  openfire_src_4_2_1.zip

Please let us know of any troubles you find by either visiting our webchat or creating posts in our Discourse Openfire Dev Forum. Thanks for using Openfire!

Tags: release, openfire, planetjabber 0
Florian Schmaus
0

Smack 4.2.2 released

Smack 4.2.2 was tagged and released recently to Maven Central.

We like to thank everyone who contributed to this release. This not only includes the various contributors shown below, but also everyone who reported an issue or suggested an improvement.

$ git shortlog -sn 4.2.1..4.2.2                                                                                                                                           >> ~/data/code/smack
    39  Florian Schmaus
     5  Ingo Bauersachs
     2  Dmitry Deshevoy
     2  damencho
     2  vanitasvitae
     1  iachimoe

The list of fixed bugs can be found in the Smack 4.2.2 changelog. Or have a look at the github comparison of the 4.2.1..4.2.2 tags.

Tags: planetjabber 0
Dele Olajide
8

Introducing Project Pd- Openfire Meetings

Pd is the Yoruba word for "Meet" and is also the name of a new project here at Ignite. Pd (the "p" is pronounced explosively) is the renamed Openfire Meetings Chrome Extension.

To install, visit the Google Chrome Store

You will need at least the following four openfire plugins to use it.

  • ofmeet
  • offocus
  • bookmarks
  • websocket (not needed if using OF 4.2)

Pd will fetch the logged in user's contact roster as well as all the bookmarks configured for the user. To see, the contacts, conference rooms and web page urls, right click on the Openfire icon.

A normal left click on the Openfire icon causes Pd to open into a Jitsi Meet video-conference with the currently selected contact or multi-chat room.

If the meeting is with a contact, then the meeting url is sent to the contact as a standard chat message. When Pd receives such a message, it displays a notification to the user.

Accepting the invitation opens the Jitsi Meet video-conference window.

Tags: 8
daryl herzmann
11

Openfire 4.2.0 Beta Release

The Ignite Realtime Community is thrilled to announce the availability of a beta quality release of Openfire 4.2.0. Downloads of release artifacts can be found on our beta release website and a changelog denoting 60 some Jira issues resolved is available as well.

So what has changed with Openfire 4.2? A lot! Some highlights:

  • XEP-0237 Roster Versioning
  • Server to Server (s2s) is more robust
  • The websocket functionality, previously in a plugin, was merged into core
  • The Admin Console now has a Pub-Sub administration interface
  • You can now manually test a Server to Server connection on the Admin Console
  • XEP-0198 Client Resumption is now available
  • A lot of polish and new handy functionality was added to the Admin Console
  • Openfire plugin loading is much more robust

Here is a listing of sha1sum values for the release binaries

f6b69035c848c7555d2710b26efbb6a927e86175  openfire-4.2.0-0.2.beta.i686.rpm
4142b5baf024b603949b64f3896964ed4dcab196  openfire-4.2.0-0.2.beta.noarch.rpm
eb6e993e2ea185da235a9039b227a676d96210a0  openfire-4.2.0-0.2.beta.x86_64.rpm
ffcf842fd9a64741140bfdde560c952a34db08a9  openfire_4.2.0.beta_all.deb
5077b1283d91e23880148fc9891a18af02fb5c68  openfire_4_2_0_beta_bundledJRE.exe
c6108509b29fb8339f444e0b766d212818560465  openfire_4_2_0_beta_bundledJRE_x64.exe
8c68a07c1933754af2042bc5cd76e2545a2bcdd6  openfire_4_2_0_beta.dmg
551015e80cf4a001a6f97deda869cbdde8f7151f  openfire_4_2_0_beta.exe
aff23069cac31aad0ee902077fd8cd4f85ea3c1f  openfire_4_2_0_beta.tar.gz
b8255d7d7cd06a35f3bf12cc38d3473aa34669a5  openfire_4_2_0_beta_x64.exe
ed53cb92966f8e21e373afcca491dd3e1b70bb7e  openfire_4_2_0_beta.zip
b380d386c2f3b4007dc9755648c579b984b52389  openfire_src_4_2_0_beta.tar.gz
f814b17f00084ef904959b3241044cf63981ece4  openfire_src_4_2_0_beta.zip

Our current intention is for a quick turnaround of this beta into a full release, so please do test it and let us know of troubles you find by either visiting our webchat or creating posts in our Discourse Openfire Dev Forum.

A big thanks goes out to our current developers for doing a lot of work to make this beta release happen. These include @dwd, @guus, @gdt, and others now submitting pull requests to our Github Repository. A special thanks goes to folks at Surevine who have been actively supporting Openfire development.

For those interested in development, here are some current talking points of where development stands.

  • A large whitespace pull request was made against the master-branch, which is now the 4.2.0 beta. The intention of this was to not frustrate all of you that maintain forks of Openfire :), but to make future Openfire contributions easier. The code base should now follow the Editor Config guidelines and so your IDE should be able to focus better on actual code changes and not fixing whitespace issues.
  • At this point, there is not much appetite for an additional 4.1 branch release, but that could of course change. We'd like to get 4.2.0 out the door, then branch master into a 4.2 branch and then focus on moving forward with 4.3 development and stabilizing 4.2 branch with a 4.2.1 release.
  • master branch continues to support building with ant and maven, with Install4j artifacts built from the ant side. We like to consolidate on maven, but work needs to be done in this area. Please consider contributing if you have maven/install4j expertise!

And in closing, please consider helping out with development. The needs are many, but some particular areas of interest are:

  • improving Openfire's LDAP implementation
  • Bringing core functionality like Multi User Chat (MUC) up to current specifications
  • Vastly improving Openfire's automated testing

We are an easy going bunch and I personally love chipping in to help out. We all hang out within the groupchat each day, so stop by! If your organization relies on Openfire, please consider helping out!

Hopefully everybody enjoys the beta release and we can turn around a full release shortly, thanks for reading and your support of Ignite Realtime!

Tags: planetjabber 11