Skip to content

Releases: igniterealtime/openfire-pade-plugin

Jitsi-Meet, JVB and JiCofo stable ver 2.0.5390

Openfire Meetings becomes Pàdé

Version 1.2.2

20 Dec 13:30
b1c0b40
Compare
Choose a tag to compare

A big thank you to @naive924 for the investigation and PR that made this release possible. Dominant Speaker switching now working for Windows users

1.2.2 -- December 20, 2020

Version 1.2.1

13 Dec 11:48
Compare
Choose a tag to compare

Pade Meetings showing a conference with 4 participants

  1. A regular home telephone
  2. Jitsi mobile app
  3. Firefox web browser
  4. Chrome web browser

Changelog

1.2.1 -- December 13, 2020

ofmeet is single plugin

Version 1.1.3- Sip Gateway

06 Dec 23:16
Compare
Choose a tag to compare

This release adds back the SIP gateway Jigasi and provides visual indicators for confirming that the JVMs for JVB, Jicofo and Jigasi services are all active. Only incoming telephone calls to the default siptest room has been tested.

image

Changelog

1.1.3 -- December 6, 2020

image

Version 1.1.2

Version 1.1.1 - Openfire Meetings now works with Firefox and Chrome 87

24 Nov 21:26
Compare
Choose a tag to compare

This version is the first release with support for Jitsi Videobridge 2.x
For more details, see the notes form the pre-release version

With this version, the new summary admin page shows call statistics from JVB2 as well as all active calls
image

Special cases

By default, ofmeet should run out of the box with Openfire default settings. However, if ldap or any other custom user provider is being used, user accounts must be created manually for jvb and focus as the plugin cannot do this automatically.

JVB2 now prefers websockets for the data channel to Jitsi Meet. Ports 8080/8443 will be used by default in Openfire. A websocket proxy has been implemented in ofmeet to proxy from the configured Openfire websocket TLS port (7443) to 8080. This removes the need to open port 8443 externally and allows JVB2 to reuse the Openfire domain certificate for TLS on port 7443.

If ports 8080/8443 are in use elsewhere and this needs to be changed, use the Network web page to do so.
image

Jitsi Videobridge 2.x

22 Nov 21:04
Compare
Choose a tag to compare
Jitsi Videobridge 2.x Pre-release
Pre-release

This is my first rushed attempt at upgrading Openfire Meetings to JVB2. Expect some bugs as the ofmeet and offocus plugins have changed a bit. I have only tested on my Windows dev pc. Feedback is most welcome especially with Linux.

image

It should run out of the box as expected, but there are some changes to be aware of.

  1. JVB (ofmeet plugin) does not exposed an xmpp component anymore. Instead, it uses an XMPP user called jvb that will join a global conference called ofmeet

image

Make sure this user is online and has joined the ofmeet chat room. Confirm focus user is also onlie and has joined the ofmeet room as well.

image

  1. Jicofo (offocus plugin) is still has as an xmpp component even though I suspect it is not being used. It connects to Openfire now as an external component

image

  1. Thats it. ofmeet and offocus will talk to each other in the ofmeet chat room and everything on the client side (Jitsi Meet) should work as usual.

  2. The summary web page is disabled and will return later looking very much different. A few networks settings have no effect because both offocus and ofmeet are running as external processes. You would have to restart the plugins to see the effect of any any server-side changes.

Version 1.0.2 - Shared Screen Cursors

01 Nov 11:52
Compare
Choose a tag to compare

This release has a new feature that enables Jitsi Meet participants to share their screen cursor positions and mouse clicks. See this feature request for more details.

image

Jitsi Meet is updated to build 4383 and this may be the last upgrade with Jitsi JVB1. Openfire Meetings (ofmeet plugin) cannot proceed to JVB2 until this issue is fixed. Consequently, this issue will remain outstanding, causing Jitsi Meet mobile to stop working with Openfire Meetings.

Changelog