Pexip Secure Scheduler for Web release notes

This page provides a summary of the new features and fixed issues in each of the current and previous releases of Pexip Secure Scheduler for Web.

Version 5.2.0

Version 5.2.0 was released in October 2025.

Resolved issues

Ref # Resolved issue
GH886 Resolved an issue that may have affected upgrades from version 4.0/5.0 to 5.1 of Scheduler for Web. In some cases, the database may have become inconsistent, resulting in errors when scheduling new subsequent meetings. Fresh installations of v5.1.0 are generally not impacted, though we advise all customers — including those with new installations — to upgrade to version 5.2.0 at your convenience to ensure optimal stability.
GH880

When adding new languages to a system, all of the associated djangojs.po translation files are now generated as required.

If you are upgrading from version 4.0, 5.0 or 5.1 to 5.2, and you have previously added new languages to your system, then you must run the scripts described below at V5.1.0 known limitations on your existing (i.e. old) host before upgrading.

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

Ref # Resolved issue
GH876 An upstream security vulnerability (CVE-2025-59420) affecting OpenID Connect login and the use of OAuth2 in the Scheduler for Web REST API was identified, allowing potential exploitation during JWS deserialization. This issue was resolved by upgrading the python authlib dependency to version 1.6.4. Customers should update Scheduler for Web at their earliest convinience to ensure secure authentication.
GH864

An issue was identified that may affect customers upgrading from version 4.0.0 to 5.0.0. In some cases, the database may become inconsistent, resulting in errors when scheduling new subsequent meetings. Fresh installations of v5.0.0 are generally not impacted, though we advise all customers — including those with new installations — to upgrade to version 5.1.0 at your convenience to ensure optimal stability.

If you experience any related problems, please refer to the workaround in the v5.0.0 limitations section further below.

V5.1.0 known limitations

Ref # Limitation
GH886

If you have upgraded your deployment to v5.1.0 and use the breakout rooms feature then please run these commands on the VM (otherwise you may experience crashes when scheduling a meeting):

$ cd /courts-core

$ sudo /opt/courts-core/bin/python manage.py dbshell -- -c "SELECT setval(pg_get_serial_sequence('"scheduling_breakoutroom"','id'), coalesce(max("id"), 1), max("id") IS NOT null) FROM "scheduling_breakoutroom";"

GH880

When adding new languages to a system, the associated djangojs.po translation files were not generated as required. As a result, attempting to upgrade a system with incomplete translation data may lead to an error similar to:

httpx.HTTPStatusError: Server error '500 Internal Server Error' for url '/api/i18n/nl/djangojs_po/'

As the issue is caused by translation misconfiguration on the existing host, please use the following commands to update translations on the existing (i.e. old) host before upgrading.

  • Replace <language> with the appropriate language code (e.g. nl).
  • Replace <terminology> with the product relevant branding (e.g. courts or scheduling).
  • These steps should be repeated for every language except en.
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

When complete, you may proceed with the upgrade process on the target system.

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 meeting, 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 meeting settings from the default values or from the selected template. The Conference Name Prefix can now be optionally populated automatically based on the meeting title.
    • Breakout rooms: to set up breakout room for the meeting.
  • Support for right-to-left (RTL) languages: The Scheduler for Web 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 Scheduler for Web portal. See Using SCIM to synchronize participants for more information.
  • Automatically dialing out to a participant: You can now configure a meeting to automatically dial out to one or more participants, for example a SIP endpoint, when a Host participant joins the meeting. See Meeting participants for more information.
  • On the Meetings page, you can now change the list view between All, Upcoming and Past meetings.
  • If a user has the Can add meeting permission, they now see a Schedule meeting button on the Calendar page.
  • Scheduler for Web 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 meeting directly from the Calendar view.
  • Dynamic RTMP stream URLs are now supported. See RTMP streams for more information.

General improvements and resolved issues

Ref # Improvement / Resolved issue
GH760 Fixes an issue in the user interface that caused a window to appear off screen when adding an access group to a meeting in the portal.
GH756 Failed API authentication attempts are now logged in the support log and administrator log, and forwarded to remote log servers.
GH753 When using OAuth2 for authentication, the OAuth2 client could not always access /api/alias/. This has now been fixed.
GH728 Fixes an issue that could cause the portal to close unexpectedly when two breakout rooms with the same role were created.
GH726 Aliases are now regenerated when the meeting participant is changed.
GH725, GH489 Fixes for missing translations.
GH488 Improvement to the user interface of the portal to prevent the Global settings and Meeting settings menus from overlapping.
GH486 Resolves an issue that caused cyclical errors when using the Windows Azure Linux Agent to run a Linux VM instance of Scheduler for Web in an Azure deployment.
GH439 Previously, when the requests module was used without an explicit certificate store entry for verify=, certifi was used for verification instead of the system certificate store. This meant internal certificates could never verify. Now, when requests is used, the system certificate store is used for validation by default, if there nothing is specified for verify=.

V5.0.0 known limitations

Ref # Limitation
GH864

If you have upgraded your deployment to v5.0.0 you must run these commands on the VM (otherwise you will experience crashes when scheduling a meeting):

$ cd /courts-core

$ sudo /opt/courts-core/bin/python manage.py dbshell -- -c "SELECT setval(pg_get_serial_sequence('"scheduling_encounterparticipant"','id'), coalesce(max("id"), 1), max("id") IS NOT null) FROM "scheduling_encounterparticipant";"

GH806

The Add participant dialog in Webapp3 exposes the current participant's join link, as the send an invite link option, to share to ad hoc participants, meaning that private participant links could be unintentionally shared.

To work around this issue you could hide the Add participant link through customization of Webapp3 (via user-menu-add-participant in the hiddenFunctionality settings).

GH250 Pexip Secure Scheduler for Web currently ignores the Pexip Infinity > Platform > Global Settings > Connectivity > Media Encryption: Required policy when setting RTMP streaming URLs. As a result, RTMP streams may be allowed even when RTMPS is required.
GH347 When creating a new meeting and entering a name, it is currently possible to discover other meeting names that are in use, as meeting names must be unique. An authenticated user could potentially identify existing names through trial and error. We therefore recommend that meeting names do not contain sensitive information.

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 Scheduler for Web portal has a new Calendar page where you can view, in calendar format, any scheduled meetings that you (your signed-in portal user) has been assigned to as a participant. The Meetings page shows only the meetings that you have access to view and/or edit based on permissions set by Access groups or administrator status.
  • Recurring meetings: When creating or editing a meeting, there is a new option Make recurring on the Start-End Time page. Select Make recurring to view and edit the recurrence preferences.
  • Meeting templates: There is a new option Meetings > Create From Template which allows you to create a meeting based on previously designed templates that contain preconfigured settings. You must first add one or more templates in Meeting settings > meeting template. You can also create a template when editing an existing meeting, or when creating a new meeting 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 meetings, 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 Meeting ID or video address from a Pexip Secure Scheduler for Web 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 Scheduler for Web 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 Scheduler for Web 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 meeting, there is a new button to Save and send email invitations.
  • Meetings 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 meeting > 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 meeting as you must delete or edit the meeting first. Now, when you attempt to delete this participant you will be able to see what meetings they are currently still assigned to so that you can manage those meetings 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 Scheduler for Web. 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 Scheduler for Web application, admins can now configure:

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

Known Limitations

Ref # Limitation
250 Pexip Secure Scheduler for Web currently ignores the Pexip Infinity > Platform > Global Settings > Connectivity > Media Encryption: Required policy when setting RTMP streaming URLs. As a result, RTMP streams may be allowed even when RTMPS is required.
347 When creating a new meeting and entering a name, it is currently possible to discover other meeting names that are in use, as meeting names must be unique. An authenticated user could potentially identify existing names through trial and error. Therefore we recommend that meeting names do not contain sensitive information.

Version 3.0.0

Version 3.0.0 was the initial release of Pexip Secure Scheduler for Web in October 2024.

Known Limitations

Ref # Limitation
320

Unattended automatic OS security updates are unintentionally enabled by default in this release. In the unlikely event of an issue with automatic updates, this could potentially cause system stability issues. To disable unattended updates, run sudo apt remove unattended-upgrades followed by sudo reboot to reboot. When applying system updates, ensure that you follow the manual process documented here.