Pexip Infinity v36

Release Notes

Software Version 36

Document Version 36.a

November 2024
 Pexip Infinity v36 Release Notes

Contents

Introduction 3

Upgrading to version 36 4
Upgrading from version 35 to version 36 4
Upgrading from versions 31.4-34.2 to version 36 5
Upgrading from versions 27-31.3 to version 36 5
Upgrading from versions 22-26 to version 36 5

New features and improvements in this release 6

Pexip Infinity platform 6

Changes in functionality 9
Changes in this release 9
Planned changes in future releases 9

Issues fixed in version 36 10

Pexip Infinity 10
Connect web apps 10

Known limitations 11
Pexip Infinity 11
Pexip Teams Connector 12
Cisco 12
Poly/Polycom 12
Microsoft 12
Microsoft Skype for Business and Lync 12
VMR Scheduling for Exchange 13
One-Touch Join 13

© 2024 Pexip AS Version 36.a November 2024 Page 2 of 13

 Pexip Infinity v36 Release Notes Introduction

Introduction
This document contains the release notes for Pexip Infinity version 36.
Complete information about how to install and operate Pexip Infinity is available from the Pexip technical documentation website at
docs.pexip.com.
The website also contains comprehensive documentation on all aspects of deploying the Pexip Infinity platform. This includes how to
administer and use the Connect app client suite; how to configure Pexip Infinity features such as One-Touch Join, VMR Scheduling for
Exchange and Pexip Service; and how to integrate Pexip Infinity with other third-party systems and call control solutions including
Google Meet, Microsoft Teams, Microsoft Skype for Business and Lync, Cisco Unified Communications Manager, Cisco VCS and
Polycom DMA.
Management Node host server sizing information
l For typical deployments of up to 30 Conferencing Nodes, you must ensure that the Management Node host server has at least
4 vCPUs and 4 GB of RAM.
l For deployments with more than 30 Conferencing Nodes, you will need to increase the number of cores and the amount of RAM
on the Management Node. Please contact your Pexip authorized support representative or your Pexip Solution Architect for
guidance on Management Node sizing specific to your environment.

© 2024 Pexip AS Version 36.a November 2024 Page 3 of 13

 Pexip Infinity v36 Release Notes Upgrading to version 36

Upgrading to version 36
If you are running a software version between v31.4 and v34.2 inclusive, you must first upgrade to version 35, and then upgrade
again to version 36; see Upgrading from versions 31.4-34.2 to version 36.

Upgrading from version 35 to version 36

When the upgrade process starts, the Management Node is upgraded first. Then up to 10 Conferencing Nodes are selected and are
automatically placed into maintenance mode. When all calls have finished on a node that is in maintenance mode, that node is
upgraded and then put back into active service. Another Conferencing Node is then selected, placed into maintenance mode and
upgraded, and so on until all Conferencing Nodes have been upgraded.
If all of the calls on a Conferencing Node that is in maintenance mode have not cleared after 1 hour, the node is taken out of
maintenance mode and put at the back of the queue of nodes to be upgraded. A further attempt to upgrade that node will be made
after all other nodes have been upgraded (or had upgrade attempts made). Up to 10 Conferencing Nodes may simultaneously be in
maintenance mode or in the process of being upgraded at any one time.
Alternatively, to avoid unpredictable system behavior due to Conferencing Nodes running conflicting software versions, you may want
to manually put all of your Conferencing Nodes into maintenance mode before initiating the upgrade process. This will allow all
existing calls to finish, but will not admit any new calls. You should then actively monitor your Conferencing Nodes' status and
manually take each node out of maintenance mode after it has been upgraded to the new software version, so that the system can
start taking new calls again on those upgraded nodes.
If you are upgrading from versions prior to v32, you must remove any existing MD5/SHA1 certificates, except root certificates, and
replace them with new certificates before upgrading to v32 or later.
How to upgrade
When upgrading, please note that:
l A Management Node upgrade may take a long time, potentially up to 1 hour. Do not reboot the Management Node under any
circumstances. If you are concerned about the time the upgrade is taking, please contact your Pexip authorized support
representative.
l There is normally no need to reboot a Conferencing Node. If a Conferencing Node appears to be stuck for over 1 hour then contact
your Pexip authorized support representative — do not reboot the node.

To upgrade Pexip Infinity software from v35.0 or later to v36:

1. Before upgrading an on-premises deployment, we recommend that you use your hypervisor's snapshot functionality to take a full
VMware/Hyper-V snapshot of the Management Node. We recommend that you do not take a snapshot of your Conferencing
Nodes — you can simply redeploy them from the Management Node (after it has been rolled back) in the unlikely event that this is
required.
Before upgrading a cloud-based deployment (Azure, AWS, GCP or Oracle), you should backup the Management Node via Pexip
Infinity's inbuilt mechanism (Utilities > Backup/Restore).
2. Download the Pexip Infinity upgrade package for v36 from the Pexip download page.
3. Before upgrading, ensure that all "always-on" Conferencing Nodes are powered on and are reachable (i.e. no Connectivity Loss
errors), and are all running the same version from which you are upgrading. You do not need to power on any cloud bursting
nodes.
4. From the Pexip Infinity Administrator interface, go to Utilities > Upgrade.
5. Select Choose File and browse to the location of the upgrade package.

6. Select Continue. There will be a short delay while the upgrade package is uploaded.

© 2024 Pexip AS Version 36.a November 2024 Page 4 of 13

 Pexip Infinity v36 Release Notes Upgrading to version 36

After the upgrade package has been uploaded, you are presented with a confirmation page showing details of the existing
software version and the upgrade version.
7. To proceed, select Start upgrade.
You are taken to the Upgrade Status page, showing the current upgrade status of the Management Node and all Conferencing
Nodes. This page automatically refreshes every 5 seconds.
8. When the upgrade completes, all nodes will show a status of No upgrade in progress and have the new Installed version.
If the upgrade process completes and there are some nodes that have failed to upgrade, you can restart the upgrade process by
uploading the upgrade package to the Management Node again via Utilities > Upgrade. This will skip over any nodes that have
already been upgraded.
9. If you have Pexip CVI for Microsoft Teams you must also upgrade your associated Teams Connector deployment in Azure to the
same version as your Pexip Infinity deployment (including minor/"dot" releases).
Full instructions are available at https://docs.pexip.com/admin/teams_managing.htm#upgrading.

If you are using VMware snapshots for backup purposes, we recommend that you delete those snapshots after approximately two
weeks, providing your upgraded system is operating as expected. This is because Virtual Machines, in general, should not run with
snapshots over time.
For full details on upgrading Pexip Infinity, see Upgrading the Pexip Infinity platform.

Upgrading from versions 31.4-34.2 to version 36

If you are running a software version between v31.4 and v34.2 inclusive, you must first upgrade to version 35, and then upgrade again
to version 36. To do this:

1. Before upgrading, ensure that all "always-on" Conferencing Nodes are powered on and are reachable (i.e. no Connectivity Loss
errors), and are all running the same version from which you are upgrading. You do not need to power on any cloud bursting
nodes.
2. Download the Pexip Infinity v35 upgrade file.
3. Follow the steps outlined in Upgrading from version 35 to version 36, but when asked to Choose File browse to the location of the
v35 upgrade file.
4. Verify that the upgrade has completed successfully.
5. Download the Pexip Infinity v36 upgrade file.
6. Follow the steps outlined in Upgrading from version 35 to version 36, and when asked to Choose File browse to the location of the
v36 upgrade file.

Upgrading from versions 27-31.3 to version 36

If you are running a software version between v27 and v31.3 inclusive, you must first upgrade to version 31.4, then upgrade again to
version 35, and then upgrade again to version 36.

Upgrading from versions 22-26 to version 36

If you are running a software version between v22 and v26 inclusive, you must first upgrade to version 27.4, and then upgrade again to
version 31.4, and then upgrade again to version 35, and then upgrade again to 36.

© 2024 Pexip AS Version 36.a November 2024 Page 5 of 13

 Pexip Infinity v36 Release Notes New features and improvements in this release

New features and improvements in this release

You can go to https://docs.pexip.com/admin/whats_new.htm and follow the relevant links for more information about all of these
features.
This topic covers the Pexip Infinity platform; for new features in the latest release of the Connect web app see the web app release
notes.

Pexip Infinity platform

Feature Description

Layout improvements There are several minor improvements to how some layout features are displayed:
l The text-based in-conference messages that are temporarily shown at the top of the layout (which
indicate states such as a locked conference, live captions, recording/streaming/transcribing/AI
enabled, raised hands, and audio-only participant names when speaking), have been restyled. By
default they are now shown in white text on various different background colors.

The text and background colors can be customized via a new indicator_color_config setting in the
theme configuration file.
l There is a new "AI" indicator, shown when Google Meet AI features are enabled.
l Any content classification messages are now shown in an overlay banner at the top of the layout.
If a banner message is also being displayed then they are combined into the same overlay.

Theme improvements: raise hand There are several improvements and updates to themes and splash screens:
DTMF command, new supported l There is a new dtmf_conference_control_command in the base theme: toggle_raise_hand, which
fonts, new AI files is assigned to *3 by default, and toggles the raised hand status of the participant.
l There are two new supported fonts for overlay text: "Inter" and "Inter Medium".
l In support of the new AI indicator for Google Meet, there are:
o New audio files: conf-ai_started_48kHz_mono.wav and conf-ai_stopped_48kHz_mono.wav.
o New fields in the themeconfig.json file: "disable_ai_indicator" and "ai_indicator_text".

© 2024 Pexip AS Version 36.a November 2024 Page 6 of 13

 Pexip Infinity v36 Release Notes New features and improvements in this release

Feature Description

Teams Connector enhancements: Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams has been enhanced:
improved Teams Rooms l Improved interoperability with Microsoft Teams Rooms:
interoperability, updated in-lobby o Connect app Hosts can now admit a Teams Room into a locked Pexip conference.
notification messages
o Dual-screen Teams Rooms are now automatically detected and will display conference
participants across both screens when joining a Pexip Infinity VMR, providing it uses the
Teams Room calendaring service* to join the conference. Local or external policy can also be
used to provide similar behavior (by modifying the dialed alias) when calling into a Zoom
meeting.
o Improved support for sending DTMF commands from a Teams Room into a Pexip conference.
This includes toggling receiving presentation content in the layout mix (*4), and toggling
multiscreen participant display (*9).
l Any in-lobby notification messages are now displayed at the top of the screen. Previously they
were displayed as slide out indicators. The displayed message is still generated from the
conference_locked_indicator_n_waiting_text theme configuration setting, but the conference_
locked_indicator_text and conference_unlocked_indicator_text settings are no longer used in
this context.
l Note that we now recommend assigning *2 to the DTMF command for toggle_teams_large_
gallery in any customized theme for Teams integration (previously *3 was recommended but this
is now assigned to toggle_raise_hand by default).
Note that version 36 of the Teams Connector contains updates that necessitate an upgrade to your
Pexip platform to ensure compatibility with the latest updates to the Microsoft Teams APIs and to the
Teams Connector's latest features. We strongly recommend that you upgrade your Pexip deployment
— both the Pexip Infinity platform and the Pexip Teams Connector — to version 36 as soon as
practicable.

Breakout rooms now a fully Breakout rooms, which are separate sessions that are split off from a main VMR or Virtual Auditorium
supported feature that allow smaller groups of people to meet together, is now a fully supported feature. Updates in this
release include:
l The ability to customize the length of time the transfer modal is shown to Webapp3 users being
moved to or from a breakout room.
l Updates to workflow and dialogs in the breakout rooms panel when managing rooms via the web
app.

Participant pinning now a fully Participant pinning, which allows you to place and lock specific participants in the most prominent
supported feature positions in a layout when a conference is in progress, is now a fully supported feature.

OIDC: ability to request additional When configuring participant authentication for VMRs using an Open ID Connect Identity Provider,
scopes administrators can now request additional information using scopes.

Codec selection when configuring When configuring Call Routing Rules you can now specify, per rule, which codecs to offer in
Call Routing Rules audio/video negotiation (SDPs).

Safe Links support Support for Safe Links URL rewriting:

l One-Touch Join now supports meeting invitations that include URLs rewritten by Safe Links in
Microsoft Defender for Office 365.
l There is a new custom jinja filter, pex_safelinks_decode, which can be used to decode strings that
have been encoded by Safe Links.

© 2024 Pexip AS Version 36.a November 2024 Page 7 of 13

 Pexip Infinity v36 Release Notes New features and improvements in this release

Feature Description

Policy enhancements: disable Local and external policy has the following additions:
overlay text in participant policy; l In participant policy you can control whether a participant's overlay text (display name) is disabled.
send DTMF in gateway calls; Teams l You can specify a DTMF sequence to send in a Infinity Gateway service type response.
Rooms OTJ call information; live
l When a Microsoft Teams Room joins a call via One-Touch Join the following fields are now
captions support; registration
included in service configuration requests (external policy) and call information (local policy):
requests support for SSO
o display_count: the number of screens signaled by the Teams Room.
o third_party_passcode: the passcode field provided by the Teams Rooms calendaring service*.
l You can specify the live captions source (audio) language and captions language.
l External policy registration alias requests include support for single sign-on (SSO). Requests now
include the remote_address field, plus a new policy request field of auth_type which can be either
"credentials" or "sso".

Pop-up-free authentication Administrators can now opt to remove the use of pop-up windows for Webapp3 participants when
authenticating using SSO in order to join a meeting. There are two new options in the Administrator
interface associated with this feature:
l Disable pop-up windows (Users & Devices > Identity Providers > Add Identity Provider) enables
and disables this feature.
l External Webapp Host address (Web App > External Web App Hosts) is required if you have
disabled pop-ups and you host the web app externally.

Administrative improvements: This release contains the following administrative improvements:

registration history, time-based
l You can now view a history of registered devices via History & Logs > Registration History.
media stream graphs, snapshot
generation, packet captures l In Status > Participants:
o A new field Is locally muted has been added which indicates whether the participant is muted
locally on the client side.
o The On Hold field has been removed (from the Administrator interface only — it is still
available via the Management Status API).
l When viewing current and historic media statistics for participants and backplanes, the media data
is now also shown as time-based graphs. This time series data is also included in diagnostic
snapshots.
l When generating a diagnostic snapshot you can now navigate away from the page while the file is
being generated and then download it later when the process has completed.
l When performing a packet capture you can now filter it on IP address / subnet and you have more
flexibility in selecting the type of traffic captured.

© 2024 Pexip AS Version 36.a November 2024 Page 8 of 13

 Pexip Infinity v36 Release Notes Changes in functionality

Changes in functionality
This topic covers the Pexip Infinity platform; for changes in the latest release of the Connect web app see the web app release notes.

Changes in this release

Feature Description

Scheduling: minimum suffix When configuring single-use VMRs as part of the VMR Scheduling for Exchange feature, the minimum suffix
length length is now 5 digits rather than 6. If you are using a short suffix you must ensure that this is appropriate to
the planned usage in your deployment, both for security purposes and to ensure you have a large enough
pool of aliases.

Planned changes in future releases

Feature Description More
information

Deprecation of Certificate-based authentication (CBA) is now the default method to authenticate the Teams
password-based Connector CVI application towards MS Graph. You can still use the previous password-based
authentication for authentication method, but we plan to deprecate it in a future release, thus we recommend using
the Teams CBA for new installations, or migrating to CBA as soon as practicable when upgrading existing
Connector CVI deployments.
application

Deprecation of v1 We plan to deprecate legacy style "version 1" themes in a future release. If you still use v1 themes
legacy themes you should plan to move to using "version 2" themes instead, which have been available since
version 18 of Pexip Infinity.

Deprecation of We plan to remove the option to use Google OAuth 2.0 for device alias registrations in a future
Google OAuth release of the client API.
support

© 2024 Pexip AS Version 36.a November 2024 Page 9 of 13

 Pexip Infinity v36 Release Notes Issues fixed in version 36

Issues fixed in version 36

Pexip Infinity
Ref # Resolution

41093 Resolved an issue that caused packet captures to fail when the Management Node was configured to use a web proxy.

40517 Streaming participants now see the "You are the only participant in the conference" splash screen instead of the Welcome screen
when no other participants are sending video.

36428 OIDC JWT 'aud' claims can now be sent to Pexip Infinity in an array. Previously only strings were supported.

Connect web apps

Webapp3

Ref # Resolution

40796 Resolved an issue whereby a Webapp3 participant whose video or audio was administratively muted and who then experienced
connectivity issues would subsequently start sending video or audio.
GL5045

39138 Resolved an issue that affected direct media conferences joined via a webapp3 path with branding applied which included
shouldMaskConference, whereby if a third participant joined, none of the participants received media after it was escalated to a
GL4902
transcoded conference.

38808 When a Webapp3 participant joins a conference with their bandwidth set to `Auto`, change their bandwidth to a different
setting, and then change their bandwidth back to `Auto`, the correct bandwidth limitations are now applied.
GL4871

37887 There is now a differentiation between administrative muting and self-muting of participants, and these states are now
controlled separately.
GL4743

Webapp2
There were no significant user-facing fixes in this release.

© 2024 Pexip AS Version 36.a November 2024 Page 10 of 13

 Pexip Infinity v36 Release Notes Known limitations

Known limitations

Pexip Infinity
Ref # Limitation

40810 Portrait mode is not available in meetings with 1+0, 1+1 and 2x2 layouts.

35820 When a SIP or telephony device is attempting to join a locked conference that requires a PIN, while at the PIN entry screen the
device will appear in the Webapp3 participant list as "In this meeting" when it is not.
GL4422

30756 Under certain circumstances, when a Conferencing Node is handling WebRTC calls that include presentation, the observed
media load may exceed 100%.

27534 A Connect app that is paired to another video device (such as a SIP endpoint) cannot be used to connect to a Media Playback
Service.

24607 Changes to cloud bursting configuration may result in an administrator.configuration log message that GCP private key
configuration was changed even when it was not.

24424 Only 3 of the assigned DNS servers will be used by the Management Node or by a Conferencing Node (as configured in its
associated system location).

19176 Changing the IP address of the Management Node and then manually rebooting before completing the installation wizard may
result in failed connectivity to Conferencing Nodes. To work around this, you must ensure that you re-run and fully complete the
installation wizard after changing the Management Node configuration.

16232 The Call-id is not logged on an administrative event when a Guest joins a conference and all Guests are muted.

16119 "License limit reached" alarms are not lowered as expected, even though an appropriate "Alarm lowered" message is logged.

15943 "Connectivity lost between nodes" alarms are not recorded in the alarm history (History & Logs > Alarm History).

13305 The G.719 codec is not currently supported for SIP.

12218 In some call scenarios that take a long time for the call setup to complete (for example calls that involve ICE, a Conferencing
Node behind static NAT, and where the client is also behind a NAT) any audio prompts (such as requests to enter a PIN) may be
played too early and the client may not hear all of the message.

7906 If a caller dials into a Virtual Reception and enters the number of the conference they want to join, but there are insufficient
hardware resources available to join the caller to that conference, the caller is disconnected from the Virtual Reception.

6739 Any changes made to VMR configuration — such as updating the participant limit — while the conference is ongoing do not take
immediate effect, and may result in conference separation (i.e. new participants will join a separate VMR from those that are
currently connected). All participants must disconnect from the conference for the change to take effect.

5601 When changing the certificates in a chain, a reboot of the associated Conferencing Nodes may be required if the changes do not
produce the desired effect.

© 2024 Pexip AS Version 36.a November 2024 Page 11 of 13

 Pexip Infinity v36 Release Notes Known limitations

Pexip Teams Connector

Ref # Limitation

35285 Participants connected via Azure Communication Services (ACS) will not see video from participants joining via CVI as "trusted".
We are working with Microsoft to address the issue that these participants are filtered out. A temporary workaround is to
configure your system so that CVI participants connect as normal/untrusted guests, and ensure that someone admits them from
the lobby. Please contact your Pexip authorized support representative for assistance and refer to issue #35285.

34367 A Microsoft Teams Room that joins a VMR as a Guest is not treated as a Guest. For example, it will not be muted if "mute all
Guests" is triggered.

27854 In a large Teams meeting you may see a discrepancy in the participant count on Pexip versus that which is reported on the Teams
side. We are working with Microsoft to resolve this.

Cisco
Ref # Limitation

4142 If the presentation channel already active from an MXP is taken by another connected participant, the MXP may not properly
receive presentation content.

Poly/Polycom
Ref # Limitation

13541 When a Polycom Trio is registered to Skype for Business, and has dialed in to Pexip Infinity, it will receive presentation as main
video from Pexip Infinity. However, when the same endpoint is dialed out to from Pexip Infinity, it will receive presentation as
RDP.

Microsoft

Microsoft Skype for Business and Lync

Ref # Limitation

17210 RDP presentation content from a Skype for Business meeting may sometimes take several seconds to render on VTC devices that
are gatewayed into that meeting. One workaround is to use Video-based Screen Sharing (VbSS) instead of RDP for content
sharing. If you must use RDP then you can configure your system to adjust the bandwidth used for RDP presentation which will
reduce the delay in rendering the RDP content for the VTC device — contact your Pexip authorized support representative for
configuration details.

13201 When a Skype for Business client is presenting PowerPoint slides in a Skype for Business meeting, sometimes only the first slide is
sent to standards-based endpoints that are gatewayed into that meeting.

5100 If a Conferencing Node being used as a gateway into a SfB/Lync meeting is near processor capacity and another endpoint in the
SfB/Lync meeting starts sending content, a participant may be inadvertently disconnected from the conference. To resolve this,
the endpoint can dial back into the conference.

4926 Participants calling into Skype for Business / Lync through the Infinity Gateway may experience inconsistent call rejection
messages if a Conferencing Node is placed into maintenance mode.

© 2024 Pexip AS Version 36.a November 2024 Page 12 of 13

 Pexip Infinity v36 Release Notes Known limitations

Ref # Limitation

4812 In some instances, one of two messages sent to a VMR from two SfB/Lync clients not previously connected may not be properly
retained by the VMR. To resolve, re-send the message.

4195 Participants connected via the Infinity Gateway into a SfB/Lync meeting may not receive presentation content from SfB/Lync
participants. This occurs if the SfB/Lync user has a screen resolution where the width is an odd number of pixels, such as a
resolution of 1437x758. If this occurs, one workaround is for the user to share an application rather than their full desktop.

VMR Scheduling for Exchange

Ref # Limitation

19530 When using Microsoft's OWA with Office 365 account, join instructions that use the <style> element will not be added, even
though the "Success" message is displayed to the user.

16602 In some circumstances, users are not able to obtain a VMR for a meeting if an existing meeting invitation is being edited and has
previously had a VMR assigned. This may happen if a user has previously activated the add-in when editing an invitation but then
discarded their changes, or if the user has removed the information added to the invitation when the add-in was previously
activated. By default, users will see a message "VMR already assigned".

One-Touch Join
Ref # Limitation

32706 Poly Trio endpoints running software version 7.x do not display meeting reminders or join notifications.

© 2024 Pexip AS Version 36.a November 2024 Page 13 of 13