What's new in version 32?

The new features and enhancements and changes in functionality included in version 32 of the Pexip Infinity platform and associated web apps, along with any planned changes, are described below.

For full information about the release, see the Pexip Infinity release notes and the Connect web app release notes.

For information about new features and changes to this and earlier versions of Pexip Infinity, see:

Pexip Infinity v32 new features and enhancements

Pexip Infinity platform

Feature Description More information
Teams Connector enhancements: improvements to the Teams-like layout* and support for Large Gallery view*

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

  • New layout features:

    • The Teams-like layout now supports multiscreen participant display and receiving the presentation stream as part of the layout mix. Note that this layout is still a technology preview feature, and is only recommended for use with Teams gateway calls.
    • Support for Microsoft's Large Gallery view: you can introduce a DTMF conference control command ("toggle_teams_large_gallery") into your themes that allows VTC participants to toggle between their current layout and Microsoft's Large Gallery view. Toggling to Large Gallery view is a technology preview feature in this release.
  • Changes to the installation/upgrade scripts are:

    • Microsoft Graph PowerShell is now used for creating the Teams Connector API app and for deploying the Teams Connector.
    • You must be using Az module version 9.0.1 or later (previously it required 7.0.0 - 8.3.0).
    • The strong API app password generation is now performed by Azure AD.

    Note that when upgrading to version 32 you can continue to use your existing Teams Connector API app that you have previously deployed.

  • Other administrative changes are:

    • The v32 Pexip Teams Connector uses the latest Microsoft Teams SDK for interoperability. This latest SDK addresses issues with the previous SDKs and also provides new features which will be used in future releases of the Teams Connector. However, there is a change in call capacity meaning that each Teams Connector instance can now handle approximately 10 calls (previously 15), although the exact capacity of each instance can vary depending on various factors such as call resolution, the number of presentation streams, and the number of participants in the Teams meetings. Microsoft are currently working on increasing the call capacity for a future release of their SDK.

      Users of scheduled scaling should review the number of instances that they need to add, and then adjust their scaling policies as appropriate.

    • The destination port ranges from Microsoft Teams (O365) to the Teams Connector load balancer are now 11000-11399 and 12000-12399 (previously they were 10000-10399 and 11000-11399). Note that these changes do not affect the Teams Connector Network Security Group (NSG) rules as they operate behind the load balancer.
    • Azure Storage key rotation is no longer performed as shared key authentication is now disabled. In addition, Teams Connector VMs now use managed identities instead of SAS tokens to access storage accounts.
New Microsoft Teams SIP Guest Join meeting type for One-Touch Join

When configuring One-Touch Join meeting processing rules, there is a new Microsoft Teams SIP Guest Join option for the meeting type. This replaces the need to use a custom rule when enabling the "SIP Guest Join" feature for Teams.

Note that the format of invitations to cloud-based or externally-managed meetings can often change. Using the latest versions of Pexip Infinity and the dedicated OTJ meeting types will ensure best future compatibility.

Enabling SIP Guest Join
Join instructions page hosted on Conferencing Nodes Conferencing Nodes can now generate a webpage where the full set of join instructions for a specific VMR is shown. These join instructions can optionally include a QR code, which when scanned by a device with a supported Connect app installed (such as Pexip Connect for RealWear or the Connect mobile app) will open the meeting directly in the app. Links to a join instructions page
Customizable display names for Epic telehealth appointments You can now customize the provider and patient display names for Epic telehealth appointments via the new Template for provider display names and Template for patient display names options when configuring an Epic telehealth profile. Configuring Pexip Infinity to integrate with Epic telehealth
Administrative improvements (site banner, search, configurable automatic backups)

This release contains the following administrative improvements:

  • You can now configure a site banner to appear across the top of every webpage of the Pexip Infinity Administrator interface. You can go to Platform > Global settings > Management web interface configuration and define the text to display, and choose the text and background colors.
Management web interface configuration
  • The Pexip Infinity Administrator interface now contains a search box (above the menu bar) that lets you search for configuration settings based on their associated menu, field name or field label text.
Using the Pexip Infinity Administrator interface
  • When enabling automatic backups, you can now configure the start hour per day and set it to run multiple times per day.
Enabling automatic backups

Connect web apps


Feature Description More information
New features
Show name labels Host participants now have the option to enable and disable name labels for all participant in the meeting. Show name labels
Alternative disconnect destination Administrators can now manually customize a destination to send participants upon disconnecting from a meeting (as an alternative to returning them to the home page). disconnectDestination
Additional background images

Administrators can now specify, via manual customization, multiple background images for users to select from.

Note that this replaces the bgImageUrl option — for more information, see Changes in functionality below.

Guests shown PIN entry keypad Guest participants who join a meeting without a Host are offered a DTMF keypad, so that they can enter the Host PIN. Enter the Host PIN
Send DTMF tones to external devices / conferences Participants in a gateway call can now send DTMF tones to the meeting or device they are connected to. Send DTMF tones to an external conference or device
Send DTMF tones to participants Host participants in a Virtual Meeting Room or Virtual Auditorium can now send DTMF tones to a selected participant. Send DTMF tones to a participant
Application tab title Administrators can now manually customize the title that appears on the web app browser tab. appTitle
Local mute state propagated to server When a user mutes or unmutes themselves, their mute state will be updated on Pexip Infinity.  
App and plugin API versions shown The app version and plugin API version are now available from within the app's User menu.  
Changes in functionality
Default background images The new "bgImageAssets" option replaces the single default background replacement image specified using the "bgImageUrl" value within the defaultUserConfig section of the manifest file. To ensure backwards compatibility this option is still supported, but we recommend for new customizations that you use the "bgImageAssets" option instead. If both "bgImageAssets" and "bgImageUrl" are specified, the former will be used and the latter ignored. Participant background replacement images


There are no significant new features in Connect Webapp2 in Pexip Infinity version 32.

Pexip Infinity v32 changes in functionality

Feature Description More information
TLS certificates with legacy signature algorithms Pexip Infinity v32 and later require TLS certificates with SHA256 or later signature algorithms. Certificates using legacy algorithms such as SHA1 and MD5 must be removed from the system before upgrade.  

TLSv1.3 is now enabled on all services

TLSv1.3 is now enabled on all services by default (and cannot be disabled).

Deployments running in FIPS compliance mode

Pexip Infinity v32 and later running with FIPS cryptography enabled now has FIPS 140-3 compliance and requires RSA private keys that comply with SP800-56b. Any keys generated by earlier Pexip Infinity versions running with FIPS cryptography enabled are already compliant. The upgrade process will endeavor to fix any non-compliant keys installed on the system, but there is a small subset of possible keys that cannot be fixed (the Certificates > TLS Certificates page on the Administrator interface will display a status of "Private key is unusable" for any such key, and those keys will then need to be replaced). Administrators uploading their own keying material must ensure compliance with SP800-56b (any non-compliant keys will be rejected).

Deploying Pexip Infinity in a secure mode of operation
Security wizard removal of X-Frame-Options setting, and an additional default CSP frame-ancestors directive

The X-Frame-Options setting has been removed from the security wizard. The CSP frame-ancestors directive supersedes the X-Frame-Options setting and the system now calculates the X-Frame-Options value based on the configured CSP (Global Settings > Security > HTTP Content Security Policy Header).

The default CSP for new installations now includes frame-ancestors 'self'.

On upgrade to version 32, frame-ancestors 'self' will be automatically added to the existing CSP unless there is an existing frame-ancestors directive.

About global settings
Install wizard new email address option

When running the installation wizard, if Enable incident reporting is selected, administrators are now required to provide a contact email address. (This address can be changed at any point after installation via Platform > Global settings > Reporting > Contact email address.)

The address will be used by Pexip Support when following up on any incident reports received from your deployment.

Re-running the installation wizard
Voice Focus performance improvements

Voice Focus (a voice activity feature that distinguishes between actual speech and background noise) has improved accuracy and better performance. When enabled it now uses the equivalent of an extra 4 audio connections per participant (previously an extra 6).

Voice activity features
Concurrent call licenses statistics no longer split by location The usage statistics showing the maximum number of concurrent call licenses used per day is now a single daily total, and is no longer split by location. Viewing usage statistics
Hardware resource usage for presentations in Teams calls To improve the accuracy of the platform's resource management, extra hardware resources are now accounted for in a gateway call to a Microsoft Teams meeting. If a VTC participant presents content, additional resources are allocated on the Teams backplane while the presentation is in progress. Hardware resource allocation rules

Infinity Connect legacy webapp

The original "legacy" version of the infinity Connect web app, "Webapp1", is no longer actively developed or maintained and has been removed from the default installation of Pexip Infinity.

If you still require access to this version, please contact your Pexip authorized support representative.

About Connect web app versions

Planned changes in future releases

Feature Description More information
Pexip Smart Scale

Pexip Smart Scale is being deprecated from Pexip Infinity version 32. Customers currently using this feature should contact your Pexip authorized support representative for information about a replacement offering.

Enabling Pexip Smart Scale
Remove support for ESXi 6.5 Support for ESXi 6.5 will be removed in a future release. When this occurs, Pexip will support VMware installation on ESXi 6.7 and 7.0 only. Configuring VMware for Pexip Infinity
Remove support for Xen Support for Xen hypervisors will be removed in version 33 of Pexip Infinity.  
Management API rate limiting In version 33 the rate limit of requests to the management API will be reduced from the current (version 32) limit of 10,000 requests every 60 seconds to 1000 requests every 60 seconds.