Pexip Secure Meetings for Justice release notes

Version 5.2.0

Version 5.2.0 was released in October 2025.

Resolved issues

Version 5.1.0

Version 5.1.0 was released in September 2025 and includes a resolution to an upgrade issue introduced in v5.0.0.

Resolved issues

V5.1.0 known limitations

pexip@courts-core:~$ cd /courts-core/
pexip@courts-core:/courts-core$ sudo /opt/courts-core/bin/python3 manage.py makeportalmessages -l <language> --add-location file --domain djangojs
pexip@courts-core:/courts-core$ sudo /opt/courts-core/bin/python3 manage.py compilemessages
pexip@courts-core:/courts-core$ sudo chown gunicorn -R "locales/<terminology>/<language>/LC_MESSAGES/"
pexip@courts-core:/courts-core$ sudo systemctl restart courts-core.service

Version 5.0.0

Version 5.0.0 was released in September 2025 and includes the following new features, improvements and resolved issues.

Do not upgrade any existing deployments to v5.0.0. Please upgrade to v5.2.0 instead. You can upgrade directly from v4 to v5.2.0. Any existing installations of v5.0.0 should also upgrade to v5.2.0.

Prerequisite

Pexip Infinity version 35 or later.

New features

• Improved scheduling user interface: When creating a hearing, the settings are now spread over three tabs on the user interface:

  • Meeting details: for the time, date and participants.
  • Additional settings: to apply any changes to hearing settings from the default values or from the selected template. The Conference Name Prefix can now be optionally populated automatically based on the hearing title.
  • Breakout rooms: to set up breakout room for the hearing.
• Support for right-to-left (RTL) languages: The Pexip Justice portal interface now supports languages that are written from right to left such as Arabic and Hebrew.
• You can use SCIM to synchronize corporate user accounts to the participants list in the Pexip Justice portal. See Using SCIM to synchronize participants for more information.
• Automatically dialing out to a participant: You can now configure a hearing to automatically dial out to one or more participants, for example a SIP endpoint, when a Host participant joins the hearing. See Hearing participants for more information.
• On the Hearings page, you can now change the list view between All, Upcoming and Past hearings.
• If a user has the Can add hearing permission, they now see a Schedule hearing button on the Calendar page.
• Pexip Justice now requires a system license that permits basic operation of the platform. See Licenses for more information.
• In Global settings > General you can now specify the default URL of the webapp. This is used to generate links to the webapp on the calendar page and in email notifications, and can be referenced via the new {{ default_webapp_url }} variable in your email templates.
• Users can now join a hearing directly from the Calendar view.
• Dynamic RTMP stream URLs are now supported. See RTMP streams for more information.

General improvements and resolved issues

V5.0.0 known limitations

Version 4.0.0

Version 4.0.0 was released in April 2025 and includes the following new features, improvements and resolved issues.

Prerequisite

Pexip Infinity version 35 or later.

New features

• Calendar view: The Pexip Secure Meetings for Justice portal has a new Calendar page where you can view, in calendar format, any scheduled hearings that you (your signed-in portal user) has been assigned to as a participant. The Hearings page shows only the hearings that you have access to view and/or edit based on permissions set by Access groups or administrator status.
• Recurring hearings: When creating or editing a hearing, there is a new option Make recurring on the Start-End Time page. Select Make recurring to view and edit the recurrence preferences.
• Hearing templates: There is a new option Hearings > Create From Template which allows you to create a hearing based on previously designed templates that contain preconfigured settings. You must first add one or more templates in Hearing settings > hearing template. You can also create a template when editing an existing hearing, or when creating a new hearing by selecting Save as Template.
• Send test email: When editing the SMTP server settings in the scheduling portal, you can now send a test email to the provided email address to ensure that the configuration is correct.
• Send cancellation emails: When deleting hearings, you now have the option to send emails notifying participants of the cancellation. Participants can then choose to remove the event from their calendar.
• Generate alias: When you invite an ad hoc participant, if you do not want to manually add an alias, there is a new Generate alias button which generates a random alias for that participant.

• Default response type: In Global settings > General > Default response type, you can set the default action that occurs when someone dials an unknown alias, or enters an unknown Hearing ID or video address from a Pexip Secure Meetings for Justice joining link.

  If you set this to continue and someone dials an unknown alias, Pexip Infinity looks for the alias in its internal database. If a matching VMR is located, the call is allowed to continue. If you set this to reject and someone dials an unknown alias, the call is not allowed to continue, even if there is a VMR matching that alias in your Pexip Infinity deployment.

General improvements and resolved issues

• The URL for downloading the latest version of Pexip Secure Meetings for Justice has changed from https://dl.pexip.com/courtscore/ to https://dl.pexip.com/scheduling-core/
• At https://dl.pexip.com/scheduling-core/, you can now download the recording, interpreter, and courts-control plugins that are used with the Pexip Secure Meetings for Justice application. The courts-control plugin provides a start hearing button that when selected moves participants from their breakout rooms into the main room. Selecting the button again (pause hearing) returns participants to their respective breakout rooms.
• In the scheduling portal, a newly added participant now receives a random PIN code if PIN code is selected as the authentication method. You can edit the random PIN code if you need to. Previously, the PIN code field remained empty until you manually added a PIN.
• For participants who have PIN code as their authentication method, the PIN itself is now hidden by default in the PIN field in the scheduling portal.
• When editing a hearing, there is a new button to Save and send email invitations.

• Hearings can now use a different theme for breakout rooms instead of them using the same theme as the main room. You can configure this in Edit hearing > VMR settings > Breakout room theme. If no breakout room theme is selected, the breakout room will inherit the same theme as the main room.

• You cannot delete a participant that is still assigned to a scheduled hearing as you must delete or edit the hearing first. Now, when you attempt to delete this participant you will be able to see what hearings they are currently still assigned to so that you can manage those hearings first.
• Table contents in the scheduling portal are now sorted alphabetically regardless of upper or lower case.
• In previous upgrades, you had to manually move any translation files over to the new version of Pexip Secure Meetings for Justice. Now, the translation files are automatically carried over as part of the upgrade.
• In a previous version, unattended automatic OS security updates were unintentionally enabled by default. This has now been fixed and unattended automatic OS security updates are disabled.

• During the installation wizard of the Pexip Secure Meetings for Justice application, admins can now configure:

  • a session duration timeout
  • a log retention period
  • an external syslog server
• Accessibility improvements.

Known Limitations

Version 3.0.0

Version 3.0.0 was released in October 2024 and includes the following prerequisites and new features:

Prerequisite

Pexip Infinity version 35 or later.

New features

• New Pexip Justice portal permissions:

  • Feature groups: Allows you to restricts a user's editing and viewing capabilities of everything in the portal. For example, you can create a feature group so that users in this group can view participants, but cannot create new participants or edit existing participants.

    When configuring feature group permissions (Global settings > Feature groups > Edit feature group), administrators should be aware that by granting someone the Can add feature group and/or Can add user permissions, that person inherently has permission to edit users’ feature groups, potentially resulting in full access to the administrator privileges of the portal. The Can add feature group and Can add user permissions should therefore, be assigned with caution and only to admins who definitely require them.

  • Access groups: Restrict which hearings are visible for users in particular groups. In hearings > [hearingname] > Edit hearing > Permissions, you can configure which access groups have permission to view and edit that specific hearing.
• When you add a non-host participant to a hearing in the portal, a breakout room is now automatically populated for this role in Edit hearing > Breakout rooms.
• Hearings can now be scheduled without requiring breakout rooms. In the portal, there is a Breakout rooms mode field in Hearing > VMR settings which can be set to Automatic, Manual, or Off.
• New Guests can present and Mute all guests toggle options in Hearing > VMR settings.
• Adds OAuth2 support to the API. In Global settings, you can now create an OAuth2 Client which gives you a Client ID and a private key for use instead of a username/password in the API.
• Allows dialing out to multiple (up to five) RTMP streams. An update to the call routing rules is required to allow this. The destination regex for the Plugin-initiated streaming/recording rule must now be rtmps://courts-core.stream/[0-4] (previously rtmps://courts-core.stream).
• When using Interpretation: support for pinning the non-native/interpreter video pane when the hearing is in progress.
• Email invitations to hearings now contain an .ical file, allowing invitees to store calendaring information.

• Adds the encounter_participants variable to the email template.

  • This is a list of all participants in the hearing, each with the same variables as the current participant. e.g. '{% for participant in encounter_participants %}{{ participant.display_name }} is a {{ participant.role }}!{% endfor%}'

General improvements and resolved issues

• During the installation process, there is a new step in the portal configuration for choosing a suitable industry terminology.
• The upgrade script now asks for a username and password interactively instead of requiring them in command line arguments.
• Users will now be logged out after 8 hours of inactivity.
• Fixes a bug that prevented saving a hearing when there were duplicate pinning configurations across themes.
• Fixes overlapping participant display names when a hearing is in progress.
• Fixes an issue where emails did not send to users when the hearing name contained non-ascii characters.
• Accessibility improvements.

Known Limitations