Features added in previous versions

You can now optionally configure whether any audio-only or video-muted participants are represented as an avatar in the main video layout (excluding Adaptive Composition and Teams-like layouts) instead of those participants being counted in the "notch" indicators.

The avatar/image used to represent the participant can come from the following sources:

• User records
• External policy avatar lookup
• Exchange Online (Microsoft Teams conferences only)

If a participant image is not available then a substitute graphic is generated based on the initials of the participant's name.

This feature is disabled by default and can be enabled via the new enable_avatars_in_mix theme setting.

Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams has been enhanced to include a new speaker-focused layout:

• It displays one large main speaker and up to 7 other video participants as thumbnails to the side. It does not apply any face detection or zooming.
• Audio-only participants are shown across the bottom of the layout and are represented by their avatar from Exchange Online.
• It can be applied via local or external policy using the view name teams_focus.

Note that the layout does not currently support multiscreen participant display or receiving the presentation stream as part of the layout mix; these features will be added in a future release.

Users of the client API can now ascertain whether individual breakout rooms are enabled for chat capabilities or not, and thus provide the appropriate chat features within that breakout room. Previously, chat support for Hosts in each breakout room had to be based upon whether chat was enabled for the main room or not.

(Note that chat configuration for a breakout room, as well as any other specific breakout room settings such as its theme, can currently only be set via policy).

Breakout rooms

Using the Pexip client APIs

• When configuring administrator access to the Pexip Infinity Administrator interface, or setting up Identity Providers for participant or registration authentication, Pexip Infinity now supports OIDC Authorization Code Flow with Proof Key for Code Exchange (PKCE).
• When configuring an OIDC Identity Provider (Users & Devices > Identity Providers), the Display Name Claim Name field now supports custom attributes.

Managing administrator access via OIDC

OpenID Connect flow

This release contains the following administrative improvements:

• The platform information page (accessed via the About link at the top right of every page in the Administrator interface) now displays the platform's FIPS compliance mode status.
• FIPS compliance can now only be enabled via the security wizard if there are no Conferencing Nodes configured.

Using the Pexip Infinity Administrator interface

Deploying Pexip Infinity in a secure mode of operation

The Teams Connector has a new authentication model with Pexip Infinity due to the deprecation of TLS client certificates by public Certificate Authorities.

All customers using Teams Connectors must upgrade their Pexip deployment — both the Pexip Infinity platform and the Pexip Teams Connector — to version 39 before May 2026.

See Changes in functionality in version 39 for more information.

Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams also contains the following enhancements:

• Calls from your Zoom Rooms can now be treated as trusted/registered devices and allowed directly into the Teams meeting (i.e. bypassing the lobby). This requires a new zoomtrustedjoin license to be installed in Pexip Infinity, and configuration of your Zoom customer account number (Call control > Trusted join).

Microsoft Hyper-V 2025 is now supported. It must be deployed manually using the generic Management Node and Conferencing Node images.

From version 39 only Hyper-V 2025 is supported (i.e. Hyper-V 2019 is no longer supported).

The default minimum PIN length for VMRs has changed from 4 digits to 6 digits.

This applies to new installations of Pexip Infinity only. There is no impact to existing systems on upgrade.

PINs may still be between 4–20 digits long, subject to the new Minimum PIN length setting in Platform > Global settings > Service configuration.

You can set an in-conference timer or countdown clock that is displayed at the top of the screen to all conference participants. There are 3 types of timer that can be displayed:

• Elapsed time since the start of the conference
• Time remaining countdown
• Current time (UTC)

There are several updates to themes in support of the new external media collection indicators for Google Meet:

• New audio files: conf-external-media-processing-start_48kHz_mono.wav and conf-external-media-processing-stopped_48kHz_mono.wav.
• New fields in the themeconfig.json file: "disable_external_media_proc_indicator" and "external_media_proc_indicator_text".

Rules and requirements for customized themes

This release contains the following administrative improvements:

• The registration status and registration history pages now include vendor information for the registered device.
• All cosmetic references to Microsoft Lync have been removed from the Administrator interface, and thus all labels and messages now refer to only Microsoft Skype for Business / SfB.
• When uploading an upgrade package, Administrators are now presented with a progress bar.
• When configuring a service with multiple aliases, administrators can now change the order in which the list of aliases appears.

Server design recommendations

Viewing current and historic registrations

Using multiple aliases to access the same service

Public Certificate Authorities are stopping issuing certificates with client authentication EKU (Extended Key Usage) capabilities, due to a change in web browser trusted CA policy. By May 2026, it will be impossible to acquire new certificates with both client and server authentication EKUs from public CAs.

Prior to version 39, certificates with client authentication capabilities were required for communicating with the Teams Connector. This requirement has been removed in v39 (see below), and therefore, certificates with client authentication capabilities are now typically not required in most Pexip Infinity deployments. However, in advanced scenarios your Conferencing Nodes' certificates may require a client authentication EKU when responding to SIP/TLS client certificate challenges.

Therefore if your environment requires your Conferencing Node certificates to have client (and server) EKU then you will need to manage this in the future through your own private Certificate Authority.

Version 39 of Pexip Infinity contains the following related changes:

• When configuring a Conferencing Node there is a new optional Client TLS certificate setting that may be assigned. This is the TLS certificate to use on this node when responding to SIP/TLS client certificate challenges.

  If your deployment receives SIP/TLS client certificate challenges then you must assign an appropriate Client TLS certificate to your Conferencing Nodes after upgrading to version 39.

• When generating a CSR (Certificate Signing Request), only server authentication EKU is now requested by default. You can optionally also request client authentication EKU. Previously all CSRs requested server and client EKU.

Teams Connector integrations

Customers who use Pexip's Teams Connector will be affected by this change to EKU:

• In version 38 and earlier, a Teams Connector deployment used TLS certificates with both server and client capabilities for validating device identities (Pexip Infinity nodes and Teams Connectors), known as mutual TLS.
• Version 39 and later uses a new authentication model that does not use mutual TLS. This means that the TLS certificates on Pexip Infinity nodes and Teams Connectors are no longer required to have client capabilities.

All customers using Teams Connectors must upgrade to v39 before May 2026.

From version 39 onwards, only the following key types are supported in the certificate that is installed on Conferencing Nodes that are used to communicate with a Teams Connector:

• RSA
• ECDSA with the following NIST curves:
  • P-256
  • P-384
  • P-521

Note that the certificate installed on your Teams Connectors must use RSA keys only.

Skype for Business deployments

Integrations with Microsoft Skype for Business require the use of client certificates, and therefore you must assign an appropriate Client TLS certificate to your Conferencing Nodes after upgrading to version 39.

Managing TLS and trusted CA certificates

Network and certificate requirements (Teams Connector)

Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams has been enhanced:

• Watermarked Teams meetings are now supported (no action is required in Pexip Infinity to enable support).

Ensuring your CVI app ID is assigned

You must ensure that your CVI app ID is specified in your Cloud Video Interop connection information. This is normally done as part of the initial deployment of your Teams Connector when defining the CVI app behavior and granting interoperability.

If your CVI app ID is not assigned then your CVI calls will fail with Teams Connector version 38 or later. Your CVI app ID is also required to receive PowerPoint Live content.

Full details of how to check and (if necessary) assign your CVI app ID via the Get-CsVideoInteropServiceProvider and Set-CsVideoInteropServiceProvider commands are contained in the Teams Connector upgrade instructions.

Local and external policy has the following enhancements:

• The call information now contains a previous_service_name field which can be used to identify the name of the previous service prior to a call transfer.

• Participant policy includes new options:

  • rx_presentation_policy: controls whether the participant can receive presentation content.
  • can_receive_personal_mix: controls whether the participant can receive a personal layout.
• The response for Infinity Gateway calls can now specify via a new transcoding_enabled field if the video and presentation streams of SIP-to-SIP calls are transcoded or not.
• The response for VMR and Virtual Auditorium service types can now specify denoise_enabled and softmute_enabled settings (when the denoise and softmute technology preview features are enabled).

Call information variables

Participant configuration responses

Infinity Gateway service type response fields

Virtual Meeting Room / Virtual Auditorium service types response fields

Administrators configuring Secure Scheduler for Exchange Integrations can now use a jinja template to generate a description of the aliases used for single-use VMRs. These alias descriptions may be displayed to users of registered Pexip apps who are performing a directory search.

By default the organizer's email address is included in the description, but this can be changed via the template.

Registering devices via an SSO Identity Provider has the following improvements:

• Device alias validation against Identity Provider attributes is now case-insensitive, allowing for a smoother experience when users who are registering their device via SSO enter an alias with a different case to that configured in the Identity Provider.
• The LDAP synchronization template, used for bulk creation and updating of device aliases, now includes fields for Enable registration using IdP SSO and Identity Provider group so you no longer need to manually set these fields after a bulk import/update.

Authenticating app registrations using Identity Providers

LDAP synchronization template

There are two new administrator permissions which provide edit and view access to OTJ Endpoints only:

• May modify OTJ Endpoints
• May view OTJ Endpoints.

The Google Meet SIP Guest Join meeting processing rule now includes a Pexip Service Customer ID field, allowing you to track these calls within Pexip Control Center.

After upgrade, you must update this rule to include your customer ID to ensure that these calls will continue to work in the future.

This release contains the following administrative improvements:

• Warning-level alarms on the Management Node can now be acknowledged by the administrator and thus hidden from Live View.
• When logging out of the Administrator interface you now have the option to log out of all active sessions.

Viewing alarms

Using the Pexip Infinity Administrator interface