Features added in previous versions

This section summarizes the features and enhancements that were added in previous releases of Pexip Infinity software.

Features added in version 27

Pexip Infinity version 27 added the following features and enhancements:

Feature Description More information
SSO authentication for conference participants Access to VMRs and Virtual Auditoriums can now be controlled using SSO authentication, managed by one or more third-party Identity Providers which you enable for your deployment. About participant authentication
Teams Connector enhancements: scheduled scaling and layout controls

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

  • Scheduled scaling allows you to automatically scale up and down the capacity of your Teams Connector at different times of the day. This allows you, for example, to cater for increased demand during core working hours but just run a minimal capacity (and thus reduce running costs) at other times of the day.

  • VTC participants can now use DTMF/keypad controls to control the meeting layout during an ongoing conference.

Other changes and improvements to the Teams Connector include:

  • The Teams Connector deployment process has a new step to create an additional Azure app that is used to secure requests to the Teams Connector APIs. This new app is required for all new deployments and when upgrading existing deployments. Ensure that you follow the upgrade instructions as directed for this release.
  • The Teams Connector now uses the Azure Standard Load Balancer (previously Basic). One of the benefits of the Standard Load Balancer is that it enables the use of Azure Availability Zones, which are now used by default if they are available in your selected region. There is no user-facing impact to these changes but they do provide greater scaling capacity, plus improved resilience and monitoring capabilities.
  • You must be using Az module version 5.1.0 or later.
  • If the Teams Connector is deployed with RDP access disabled (no addresses were originally specified in the $PxMgmtSrcAddrPrefixes installation variable) then if you want to subsequently enable RDP access you now need to perform a full redeploy.
  • Version 27 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 27 as soon as practicable.

PSS Proxying Edge Node support

Pexip Smart Scale now supports Proxying Edge Nodes, in addition to Transcoding Conferencing Nodes.

As a result of this new feature, PSS locations have been renamed to PSS regions.

Enabling Pexip Smart Scale
New conference layouts, presentation modes, and in-conference DTMF control options

There is a range of new layout-related features:

  • A set of new conference layouts are available:

    • 9 main speakers (3 x 3 layout)
    • 16 main speakers (4 x 4 layout)
    • 25 main speakers (5 x 5 layout)
    • Small main speaker and up to 33 other participants (1 + 33 layout — this was a technical preview feature in v26)
    • Extended Adaptive Composition * (displays up to 23 video participants); this is a technical preview feature and it can only be enabled via the transforms functions in the Pexip client APIs
  • Host participants on video endpoints can change the layout currently being used by the conference by sending DTMF commands to the conference. The layouts that are available, and the DTMF keypad controls used to change the layout, are all customizable via themes.
  • When using Adaptive Composition, single-screen endpoints now receive any presentation content as part of the layout mix (replacing some of the other video participants). If required, they can use DTMF commands to switch to receiving the presentation as a separate stream.
  • There is a new theme customization file vendordata.json that contains information about videoconferencing endpoints from different manufacturers. It is used to determine whether a specific endpoint is a single-screen or two-screen device, and thus if presentation content could be sent as part of the layout mix.
  • The ability to show the name of the active speaker is now available in the following layouts: Adaptive Composition, 2 x 2, 3 x 3, 4 x 4, 5 x 5, and 1 + 33.

Conference layouts and speaker names

Controlling the layout during a conference

Using a DTMF keypad to control a conference

Rules and requirements for customized themes

transformLayout (PexRTC client API)

transform_layout (REST client API)

Installation wizard improvements

When using the installation wizard:

  • Default values are now also offered for the hostname, domain name, DNS and NTP servers, if they are provided by DHCP.
  • You can now use commas (as well as spaces) to separate the list of DNS and NTP servers.
 
Security enhancements

All TLS ciphersuites using SHA1 are now disabled (unless TLS 1.0/1.1 has been enabled via the security wizard).

In addition, the security wizard contains the following new options:

  • Enable AES_CM_128_HMAC_SHA1_* SRTP ciphersuites: this allows you to disable SHA1 SRTP cryptosuites if required. It defaults to enabled, which is the existing/previous behavior.
  • Enable TLSv1.2 CBC-mode ciphersuites: this allows you to disable CBC for TLS 1.2 ciphersuites if required. It defaults to enabled, which is the existing/previous behavior.
  • Enable 2048-bit DH groups for H323: this allows you to enable 2048-bit Diffie-Hellmann groups for H.323 interoperability. It defaults to disabled, which is the existing/previous behavior.
Deploying Pexip Infinity in a secure mode of operation
Administrative improvements

This release contains the following administrative improvements:

 
  • There is a new watermark_footer_icon.png file in the Base theme. This new watermark graphic is used only in the 1 + 33 layout (it appears at the bottom of the layout).
Base theme and other preconfigured themes
  • The Conferencing Node status summary page (Status > Conferencing Nodes contains some extra fields: Number of vCPUs, System memory and Config sync status. The Deployment status field has been removed.
Viewing Conferencing Nodes
  • A Conferencing Node's static NAT address (if configured) is now included in the list view shown at Platform > Conference Nodes.
 
  • The Status > Registrations page now includes the device's remote IP address that is used for signaling.
Viewing registrations
  • You can now include the local_display_name field in the response to any local or external policy service configuration request i.e. for any service_type. Previously it was only supported in "gateway" service type responses.
Using external and local policy with Pexip Infinity

Changes in functionality in version 27

Feature Description More information
ESXi 7.0 is now supported

Support for ESXi 7.0 has been added, and support for 6.0 has been removed.

Version 27 now supports VMware vSphere ESXi 6.5, 6.7 and 7.0.

Configuring VMware for Pexip Infinity
Guests in a Virtual Auditorium now see a streaming indicator Guest participants in a Virtual Auditorium are now shown the streaming indicator when a conference is being streamed or recorded. About PINs, Hosts and Guests
Administrative modifications

This release contains the following administrative modifications:

  • When deploying a Conferencing Node you are now only asked to provide the number of virtual CPUs and amount of RAM to assign for VMware and Hyper-V deployment types.
 
  • When deploying a Conferencing Node to KVM or XEN, Pexip Infinity now generates a VMDK file instead of an OVA file.
 
  • Very quiet or very loud audio announcements are no longer adapted to a standardized level when played out in a conference. Customers with custom .wav files in a custom theme should check that the audio levels of those recordings are still appropriate when heard during a conference.
 
  • When configuring a Teams Connector the Enable enhanced status information field has been renamed to Enable Azure Event Hub.
 
  • The tech preview option Enable 1 + 33 layout has been removed (Platform > Global settings > Tech preview features). This layout is no longer tech preview and is now available by default.
 
  • The tech preview option Enable push notifications has been removed (Platform > Global settings > Tech preview features).
 
  • There is an improved indication of any default values when viewing the management API resource schema. For example it now shows "None" instead of "default" if a field is nullable but has no default.
  • Firewall connectivity to pexip.flexnetoperations.com is no longer required since 1 January 2022. (This is not a v27-specific change.)
 

Features added in version 26

Pexip Infinity version 26 added the following features and enhancements:

Feature Description More information
Adaptive Composition layout enhancements for inactive video participants and Virtual Auditoriums

The Adaptive Composition layout contains improvements to the process of removing and restoring inactive video participants in the video mix:

  • There is a new inactive video participants indicator . This shows the number of inactive video participants who are excluded from the video layout, including any Infinity Connect participants who have muted their video. Previously these participants were included in the count of audio-only participants.
  • Inactive participants are more quickly returned to the video layout when they are detected or become active again, removing the need for having to speak to be returned to the mix.

    • Web app participants: any activity in the web app, such as speaking or moving the mouse, instantly triggers a face-detection check.
    • Endpoint participants: now performs a face-detection check every 30 seconds, as well as when the participant speaks.

Other enhancements in this release:

  • The Adaptive Composition layout can now be used in Virtual Auditoriums (in addition to Virtual Meeting Rooms).
  • Support for Adaptive Composition in Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams (see below).
Conference layouts and speaker names
Removal of video-muted Infinity Connect participants from other layouts

Other (non-Adaptive Composition) layouts now also remove Infinity Connect participants from the layout mix if they mute their video:

  • These are shown with a separate indicator on the left-hand side of the screen, and works in the same manner as for existing audio-only participant indicators.
  • Up to 4 audio-only or muted-video indicators are displayed before they are collapsed into a single indicator.
Conference layouts and speaker names
Teams Connector enhancements: Teams lobby notifications, Azure resource tagging, and support for Adaptive Composition*

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

  • VTC systems that are gatewayed into a Teams meeting now see notification messages when an untrusted VTC or guest Teams client is waiting in the Teams lobby:

    • The messages are for information only — the VTC system cannot admit people into the meeting.
    • The notifications use Pexip Infinity's existing locked conference indicators, so the messages and indicators can be customized via themes in the usual way.

Other changes and improvements to the Teams Connector include:

  • The ability to optionally specify a set of tags (name-value pairs) to apply to the Azure resources that are created for the Teams Connector. This uses a new $tags variable in the PowerShell variables initialization script.
  • The redeploy/upgrade script now removes the dynamic Azure resource groups for you (those named <prefix>-TeamsConn-<region>-RG that contain the existing Teams Connector instances). This means you no longer have to perform this step manually via the Azure portal when upgrading or redeploying.

  • Support for Adaptive Composition layout (technology preview)

    When Adaptive Composition is used with a Teams conference:

    • Up to 9 video participants are shown in the Adaptive Composition layout seen by VTC participants.
    • Each participant's video that is received from Teams for display to VTC participants is cropped and framed as appropriate.
    • The VTC participant's video stream sent to Teams is cropped and framed as appropriate.
    • Audio participant avatars are not supported.

    The default layout for Teams meetings is still Pexip's standard 1+7 layout, but you can change this to Adaptive Composition via policy or via the transform layout management or client API commands.

  • Version 26 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 26 as soon as practicable.

Integrating Microsoft Teams with Pexip Infinity

Configuring the layout seen by VTC participants

Customizing the in-lobby notifications

Upgrading the Teams Connector to the latest software

WebRTC quality improvements

This release contains the following WebRTC enhancements:

  • Improved video and audio resilience in lossy networks.
  • Improved resilience and image quality for full-motion and still image presentation (now uses H.264).
 
Epic telehealth patients can join via email or SMS

Pexip's Epic telehealth integration contains the following new features:

  • Epic telehealth patients can now launch their video visit via a join link sent by email or SMS text message.
  • Pexip Infinity administrators can configure how the conference/appointment name is constructed via a new Service name template profile field.
  • Pexip Infinity administrators can configure the content of the error page shown to users if a telehealth call launch fails via a new Error page template for launch failures profile field.
Epic telehealth integration with Pexip Infinity
Polling for scheduled maintenance events in Microsoft Azure Pexip Infinity VMs that are deployed in Microsoft Azure now poll for scheduled maintenance events automatically. When certain events are detected, such as a Freeze event, the Conferencing Node running on that VM is automatically placed into maintenance mode, and an alarm is raised. Managing Azure instances
Additional One-Touch Join meeting rules
  • There is a new One-Touch Join rule available to support invitations to Microsoft Teams meetings sent from domains other than your own, where the meeting organizer is using a Cisco — Teams integration.
  • There is a new option for Zoom meetings to include the meeting password in the alias used to join the meeting, so that users do not need to enter the password themselves.
One-Touch Join meeting types and transforms
New 1 + 33 conference layout

*

A new 1 + 33 layout is available.

This layout is suitable for large conferences. It displays 1 small main speaker and up to 33 other participants. (It can be enabled for selection via Platform > Global settings > Tech preview features).

Conference layouts and speaker names
Administrative improvements

This release contains the following administrative improvements:

 
  • There is a new icon_video_muted.svg graphic (video_muted_indicator.png in legacy version 1 themes), which is used in non-Adaptive Composition layouts when a muted video participant is excluded from the video layout.
Rules and requirements for customized themes
  • In license management, if you select an existing license there is now an option to manually return the license (in addition to the existing online return option).
Pexip Infinity license installation and usage
  • Quicker reboot times when restarting a Conferencing Node on the same hardware due to faster sampling.
 

* Technology preview only

Changes in functionality in version 26

Feature Description More information
HTTP Content-Security-Policy headers on Conferencing Nodes are now enabled by default, and other new security wizard options

The use of HTTP Content-Security-Policy (CSP) headers on Conferencing Nodes has changed:

  • CSP headers are now enabled by default on new and upgraded deployments (previously disabled by default).
  • You can now enable or disable HTTP Content-Security-Policy headers, and modify the header contents, via the Administrator interface (Platform > Global settings > Security).
  • The option in the security wizard to enable/disable CSP headers has been removed.
  • The default CSP header content is unchanged from previous releases.
  • The security wizard also contains the following new options:

    • Enable Referrer-Policy: same-origin on HTTP responses (default = yes)
    • Enable X-Frame-Options: DENY (yes)
    • Enable preload in HSTS header (no)

About global settings

Deploying Pexip Infinity in a secure mode of operation

Break-in resistance settings: allow list and changes to the handling of X-Forwarded-For headers

Pexip Infinity version 26 behaves differently from prior versions in its handling of X-Forwarded-For headers in its break-in resistance checking.

Installations that use reverse proxies in conjunction with the break-in resistance options in Pexip Infinity need to take action after upgrading to v26:

  • A new option in version 26 lets you define "Allow list address" entries that are exempt from break-in resistance checks (Call control > Break-In attempt allow list).
  • You must create an allow list address with an Entry type of Proxy that contains the apparent IP address (from Pexip Infinity's perspective) for all trusted reverse proxies or HTTP(S) load balancers in use in your deployment. This allows Pexip Infinity to process the X-Forwarded-For header entries and, in turn, means that the break-in resistance features will work correctly to block malicious attackers who attempt to attack the Pexip Infinity deployment via the reverse proxy.
  • You may also choose to add trusted call control systems (such as H.323 gatekeepers and SIP proxies e.g. Cisco VCS systems) to the allow list to prevent those IP addresses from ever being temporarily blocked by Pexip Infinity.

If you have previously disabled the break-in resistance features due to the attacks being blocked too aggressively, you may find that you can now find a balanced configuration that allows you to enable the feature and maintain a good level of protection against SIP scanners etc. but, with judicious use of the new Allow List feature, a significantly reduced risk of accidentally blocking legitimate users from accessing Pexip Infinity.

Break-in resistance settings to mitigate rogue calls
New permission when configuring dynamic bursting to the Microsoft Azure cloud

When setting up the Active Directory (AD) application and permissions to be used by Pexip Infinity to start up and shut down the Conferencing Node overflow instances, we now recommend using the Virtual Machine Contributor built-in role (previously DevTest Labs User).

If you have created your own custom role you should add the Microsoft.Compute/virtualMachines/powerOff/action permission to it.

If the powerOff action permission is not assigned you may temporarily see a "Not authorized to perform this operation" alarm, but the virtual machine will still get successfully deallocated.

Configuring dynamic bursting to the Microsoft Azure cloud
Administrative modifications

This release contains the following administrative modifications:

  • You no longer have to select a Telehealth Profile when configuring a Call Routing Rule for Epic telehealth integrations (this field previously had no effect and was just for your own information). The rule's call target option has also been renamed from Epic Telehealth profile to Epic Telehealth meeting.

Configuring Pexip Infinity to integrate with Epic telehealth

Support for old versions of ESXi Support for ESXi 5.x was removed in Pexip Infinity v26. Version 28 of the Pexip Infinity platform supports VMware vSphere ESXi 6.5, 6.7 and 7.0.  
Automatic deployments on ESXi no longer supported Automatic deployment of Conferencing Nodes in VMware environments was deprecated in Pexip Infinity v23 and was removed in v26. From this version onwards, you must deploy your Conferencing Nodes manually, as with other hypervisor environments. As a consequence, VM managers are no longer required or supported.