New features and improvements in this release

The new features and enhancements included in Pexip Infinity version 33 are described below.

This topic covers the Pexip Infinity platform; for new features in the latest release of the Connect web app see the Connect web app release notes.

Pexip Infinity platform

Feature Description More information
Participant policy and
custom Identity Provider attributes

You can now use local and external policy to override a participant's role, alias and display name before they join a conference. This allows you, for example, to anonymize a participant's name or modify their role based on other properties of the call or their associated Identity Provider. This new Participant policy option is configured in the same way as the existing local and external policy types and is executed after any service configuration policy and before any media location policy.

To support participant policy, you can now also define custom attributes for your selected Identity Providers (Users & Devices > Identity Providers > Advanced options). The attributes you assign are made available to any local or external participant policy, where a Connect app or other WebRTC participant uses that provider for authentication. These attributes can then be used in the participant policy decision-making process (for example whether to accept or reject a call, or assign a specific role).

Using external and local policy to control Pexip Infinity behavior

About participant authentication

Custom layouts*

You can design your own layouts and use them in the same way as the standard adaptive composition and classic layouts that are included by default.

Custom layouts are specified through JSON configuration files that are uploaded via themes. The theme can then be assigned as the default theme or applied to specific VMRs and gateway rules as required, to control where your custom layouts may be used.

A new customlayouts license is required to upload your own custom layout files.

In addition, two new example custom layouts have been added to the base theme, as files custom_layout_one_main_twelve_around.json and custom_layout_two_mains_eight_around.json.

These custom layouts are available for use in all service types in the same way as the existing standard layouts:

  • 1+12 (Large main speaker and up to 12 other participants)

  • 2+8 (Two main speakers and up to 8 other participants)

(The numbers in the images indicate the order in which participants are displayed.)

Conference layouts and speaker names

Rules and requirements for customized themes

Portrait mode support for WebRTC devices in Adaptive Composition layouts *

Any WebRTC device with a portrait aspect ratio (such as 9:16) can now receive a layout specifically designed for a portrait display when in a conference that is using an Adaptive Composition layout.

This is a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Enable AC Portrait.

Enabling AC Portrait mode
Teams Connector enhancements: support for calling Microsoft Teams Room devices, blue-green deployments, private routing*, and certificate-based authentication for the CVI application

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

  • Users who have Microsoft Teams Room devices with Pro licensing can now make and receive 1:1 (also referred to as point-to-point) SIP/H.323 video calls with VTCs, and call into Pexip Infinity VMRs.
  • You can now enable private routing between your Pexip Infinity platform and your Teams Connector deployment. This enables traffic to go over a private/internal network instead of the public internet. This is a technology preview feature.
  • Changes to the installation process and upgrade scripts are:

    • There are some new variables in the variables script, and new parameters to create_vmss_deployment.ps1 in the installation and redeploy scripts to support Microsoft Teams Rooms SIP/H.323 calling, private routing and certificate-based authentication for the CVI app ID (see the upgrade steps for details).
    • We have documented a blue-green deployment/upgrade strategy to improve the upgrade process. This allows you to create separate environments where one environment (blue) is running the current application version and another environment (green) is running the new application version. Using a blue-green deployment strategy increases application availability and reduces deployment risk by simplifying the rollback process if a deployment fails.
    • From version 33 you can use certificate-based authentication (CBA) to authenticate the Teams Connector CVI application towards MS Graph. In version 33, CBA is optional and the previous password-based authentication method is still the default mechanism.

      The CBA method will be the default and recommended mechanism in version 34. Password-based authentication will still be supported in version 34 but we plan to deprecate it in a future release, thus we recommend migrating to CBA as soon as practicable.

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

  • VTC endpoints now see a splash screen if a Teams client starts PowerPoint Live sharing, or uses any other non-supported content share sources, such as Excel or Whiteboard:

  • Other administrative changes are:

    • The call capacity has been restored to approximately 15 calls per Teams Connector (it now uses an updated and improved Microsoft Teams SDK for interoperability).
    • Firewall changes to support calls between Microsoft Teams Rooms and VTC endpoints:

      • You need to open port 4277/TCP on your Conferencing Nodes to receive signaling from your Teams Connector instances.
      • Signaling is now sent from Microsoft Teams to port 10101/TCP on the Teams Connector's Azure load balancer.
    • The app password is now stored in the Azure Key Vault (instead of the Automation account).
    • Improvements in the Pexip Infinity Administrator interface (Status > Live View):

      • The private IP address of a Teams Connector instance is now shown when viewing its status in Live View.
      • Any overly long meeting names are now truncated when displayed in Live View.
    • The Teams-like layout and Microsoft's Large Gallery view are now fully supported features (they were technology preview features in previous releases).
    • The Teams Tenant ID is now provided in the call information (as teams_tenant_id) that is available to local and external policy.

Note that version 33 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 33 as soon as practicable.

ESXi 8.0 support The Pexip Infinity platform now supports VMware vSphere ESXi 6.5, 6.7, 7.0 and 8.0. Supported hypervisors
Breakout rooms *

Breakout rooms are now supported on VMRs. This lets you configure individual VMRs so that its participants can be moved into segregated breakout rooms.

This is a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Enable Breakout Rooms.

Breakout rooms
Improved One-Touch Join endpoint compatibility for Microsoft Teams SIP Guest Join The Microsoft Teams SIP Guest Join meeting type option for One-Touch Join has been updated to provide increased endpoint compatibility with Poly devices and for Cisco Unified Communications Manager (CUCM) integrations. Enabling SIP Guest Join
New custom jinja filters

This release includes two new custom jinja filters:

  • pex_url_decode: this can be used to decode previously URL-encoded links. For example, it can be used with OTJ custom rules to simplify the regular expressions required.
  • pex_urldefense_decode: this can be used to decode strings that have been encoded by Proofpoint's URL Defense.

Custom Pexip filters


Denoising is a server-side feature that removes the background noise from somebody who is speaking. (In comparison, Softmute softens the gain from a noisy, but non-speaking participant.)

This is a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Enable Denoise and can then be individually enabled or disabled at the VMR level.

Tech preview features

OTJ meeting type icons One-Touch Join endpoints now include an icon representing the meeting type (for Microsoft Teams, Google Meet, Webex and Zoom meetings) when displaying meeting information. This is automatically available on Cisco endpoints capable of supporting this feature.  
New theme content to support the latest features A new no_powerpoint_live.jpg file has been added to version 2 themes to support the new PowerPoint Live related splash screen used in the Microsoft Teams interop calls. Note that this is a static jpg image i.e. you can only customize it by supplying your own replacement jpg image. Rules and requirements for customized themes
Per-location syslog servers

You can now select, per system location, the syslog servers to be used by the Conferencing Nodes in that location.

On upgrade to v33, all existing syslog servers will be assigned to all existing locations. Any subsequently created locations must have their associated syslog servers assigned manually.

Using a syslog server
Administrative improvements

This release contains the following administrative improvements:

  • A "Google Meet Gateway Token expiring" alarm is raised when the Google Meet gateway token is due to expire within the next 30 days.
Configuring Pexip Infinity as a Google Meet gateway
  • When configuring event sinks there is a new advanced tuning setting — Time between metrics updates — that specifies the time between event sink metrics updates.
Using event sinks to monitor conference and participant status
  • There is a new User Group configuration page in the Administrator interface at https://<manageraddress>/admin/platform/usergroup/ which is used in conjunction with version 3 of the VMR portal to map users to Pexip Infinity resources.

Controlling web app path branding and VMR management via user groups

Extra configuration and maintenance tasks for the VMR self-service portal

* Technology preview only