What's new in version 24?

The new features and enhancements and changes in functionality included in Pexip Infinity version 24, along with any planned changes and the new features and changes in the Infinity Connect web app are described below.

For full information about this release, see the release notes.

For information about earlier versions of Pexip Infinity, see Features added in previous versions.

Pexip Infinity new features and enhancements

Feature Description More information
One-Touch Join enhancements

The One-Touch Join feature now includes:

About One-Touch Join
VMR Scheduling for Exchange enhancements

The VMR Scheduling for Exchange feature now includes:

Scheduling Pexip Infinity meetings using Microsoft Exchange
VMR self-service portal

The Pexip VMR self-service portal is a separately-installable component that allows end-users to manage their personal Virtual Meeting Room without having to send requests to their administrator to change the configuration of their VMR.

Pexip provides the VMR portal appliance via an OVA template suitable for deployment on VMware ESXi. The OVA template is provided "as-is" and provides a reference installation which is suitable for integrating with an existing Pexip Infinity deployment.

About the VMR self-service portal
Teams Connector lobby waiting screen, participant avatars and Teams compatibility updates

Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams now includes:

  • Updated splash screens when connecting to a Teams meeting:

    • A new "Call connecting" screen is initially displayed while the participant's status is being determined:

    • If the participant is held in the lobby a new "Welcome to the lobby" screen is displayed and a new "Welcome to the lobby. Please wait and your meeting host will admit you soon." audio message is played:

    These new screens and audio file can be customized via themes in the standard way.

  • The Teams Connector requests from Exchange Online an avatar for each participant in the conference. This avatar is used:

    • to represent any audio-only participant within the VTC's conference layout (replacing Pexip's standard audio indicator )
    • in the participant profile in the Infinity Connect roster.

    If the avatar request fails (the participant is not found in Exchange Online, or has no avatar) then a substitute graphic is generated based on the initials of the participant's name.

    This behavior is configurable via a new External participant avatar lookup option which you can set at the global level and override it for each individual Call Routing Rule if required.

Other changes and improvements to the Teams Connector include:

  • The OnlineMeetings.ReadWrite.All permission is no longer requested when providing consent for the Pexip CVI app to access Teams meetings.
  • Version 24 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.

We strongly recommend that you upgrade your Pexip deployment — both the Pexip Infinity platform and the Pexip Teams Connector — to version 24 as soon as practicable.

Integrating Microsoft Teams with Pexip Infinity
New theme elements for participants connecting to a Microsoft Teams meeting

The following theme elements (that apply to version 2 style themes only) have been added to support the new Microsoft Teams integration features (as described above) for participants that are connecting to a Teams meeting:

  • New inlobby_status_unknown splash screen which is shown when initially connecting to a Microsoft Teams meeting, while the participant's status is not yet known.
  • New inlobby splash screen which is shown while the participant is being held in the Microsoft Teams lobby when joining a Microsoft Teams meeting.
  • New icon_is_in_lobby.svg graphic which is displayed on the new inlobby splash screen.
  • New audio file conf-participant_is_in_lobby_48kHz_mono.wav ("Welcome to the lobby. Please wait and your meeting host will admit you soon.") that is played to the participant being held in the Microsoft Teams lobby.
Rules and requirements for customized themes
Additional web proxy functionality
  • If a web proxy is configured for the Management Node, it will now be used when the Management Node is communicating with the service used for cloud bursting (i.e. Azure, AWS or GCP), and for requests to One-Touch Join OAuth token endpoints (if OAuth is configured).
  • If a web proxy is configured for a system location that is used for One-Touch Join, the web proxy will now be used for outbound One-Touch Join-related requests to Cisco endpoints, Exchange, and G Suite.
Using a web proxy
Participant call tags

Every participant event associated with a conference can now include a call tag that is specific to that participant.

The tag can be specified in client API requests and then used by app developers to correlate other API requests. The participant call tag is present in policy requests, participant updates to other participants, event sinks and the status/history databases for management API requests. Note that the call tag is not displayed in the Administrator interface.

Tracking usage via service and participant call tags
Administrative improvements

This release contains the following administrative improvements:

  • When upgrading to version 24, and on any subsequent upgrades, up to 10 Conferencing Nodes can be upgraded simultaneously (previously 5 nodes).
Upgrading the Pexip Infinity platform
  • There is a new "Eventsink Reached Maximum Backoff" alarm that is raised when, after several retry failures, events cannot be delivered to an event sink.
About event sinks
  • There is a new optional theme setting, enable_solo_streaming_loopback, that can be added to your themeconfig.json file. This setting controls whether a loopback of the presentation stream is shown instead of the streaming_in_progress splash screen when there are no other participants in the conference other than a streaming participant.
Rules and requirements for customized themes

Pexip Infinity changes in functionality

Feature Description More information
Security enhancements for internode communications and connections between Pexip Infinity and endpoints

The following changes to Pexip Infinity's encryption methodologies have been applied:

  • IPsec links between Pexip nodes now use 256-bit AES-GCM for encryption (previously 256-bit AES-CBC).
  • Encrypted connections between Pexip Infinity and endpoints may now use AES 256-bit encryption for media.
  • The fallback AES128-SHA ciphersuite is now disabled by default for inbound calls for new installations and after upgrading to version 24. However, it remains enabled for outbound SIP/TLS calls to maintain compatibility with endpoints running outdated firmware. This behavior can be changed via two new security wizard options as described below.
  • TLS1.0 and TLS1.1 are now disabled by default on all new deployments, and when upgrading to v24 on deployments on which the security wizard has never been run. Any existing deployments on which the security wizard has been run will now also disable TLS1.1 if TLS1.0 was disabled, otherwise both TLS1.0 and TLS1.1 will remain enabled after upgrading to v24.
  • Anonymous Diffie-Hellman for outbound SIP/TLS calls is now disabled by default on all new deployments, and when upgrading to v24 on deployments on which the security wizard has never been run. Any existing deployments on which the security wizard has been run will have unchanged behavior when upgrading to v24.

The associated changes to the security wizard are:

  • A new Enable AES128-SHA ciphersuite option, which is set to No by default. When this is set to No:

    • The AES128-SHA ciphersuite is disabled for inbound calls.
    • Outbound SIP/TLS calls may still use the ciphersuite depending on the value of the new Enable AES128-SHA ciphersuite for outbound SIP/TLS option, which is set to Yes by default.
  • The Enable TLS 1.0 option is now called Enable TLS <1.2 and is now set to No by default. When set to No, all versions of TLS <1.2 are disabled.
  • The Enable Anonymous DH for outbound SIP/TLS setting now defaults to No.

Encryption methodologies

Deploying Pexip Infinity in a secure mode of operation

RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP)

Audio improvements in Google Meet calls

There have been several improvements to audio quality in calls with Google Meet:

  • Audio from all participants in a Google Meet call is now normalized across all joining devices. Previously, when video endpoints joined a Google Meet call they were often at a lower volume than guests joining directly from their computer. This was noticeable in larger meetings with many Google Meet participants. The normalization means that all participants now join at a similar audio level without the need for manual adjustments.
  • Improved audio resilience between Google Meet and Pexip Infinity in situations where there is poor network quality.

Integrating Google Meet with Pexip Infinity

Improved VP8 and VP9 resource usage The VP8 codec now uses the same amount of CPU resources as the H.264 codec (previously it used around 20% more resources than H.264), and the VP9 codec now uses 25% more resources than H.264 (previously 50% more). Hardware resource allocation rules
Ability to set "treat as trusted" for calls to SIP destinations and registered SIP devices When configuring Call Routing Rules you can now set the Treat as trusted flag for calls placed to SIP destinations and registered SIP devices. This indicates that the target of the rule may treat the caller as part of the target organization for trust purposes. Configuring Call Routing Rules
Shorter entry and exit tones The entry and exit tones that are contained in the alternative preconfigured themes have a shorter duration and are less intrusive than those previously used. Base theme and other preconfigured themes
Administrative modifications

This release contains the following administrative modifications:

  • You cannot upgrade your platform to version 24 if any Conferencing Nodes are running on servers that do not use the AVX or later CPU instruction set (e.g. if it uses SSE4.2).
 
  • Administrators can now specify a Contact email address to be included in any incident reports.
Automatically reporting errors
  • When requesting a diagnostic snapshot via the Administrator interface you can now specify the start and end time for the period covered by the snapshot.
Downloading a diagnostic snapshot
  • A Conferencing Node is now automatically restarted if you change its role from a transcoding node to a proxying node or vice versa.
Deployment guidelines for Proxying Edge Nodes
  • When viewing the status of TLS certificates a new status of Over <n> days may be displayed. This supports recent changes to how browsers treat certificates: all browsers will not trust certificates that are valid for longer than 825 days, and Safari will also not trust certificates with a start date on or after 1st September 2020 and that are valid for longer than 398 days.
Managing TLS and trusted CA certificates
  • When deploying Virtual Machines in Google Cloud Platform (GCP), if you use project-wide SSH keys to manage your VMs, Pexip Infinity now looks for project metadata with a name of "ssh-keys" (previously it looked for "sshKeys").
Deploying Pexip Infinity on Google Cloud Platform (GCP) Virtual Machines
  • The maximum length of a local policy script has been increased from 12288 to 49152 characters.
Writing local policy scripts
  • References within the Administrator interface to "Google Hangouts Meet" have been changed to "Google Meet".
Integrating Google Meet with Pexip Infinity

Planned changes in future releases

Feature Description More information
Automatic deployments on ESXi no longer supported Automatic deployment of Conferencing Nodes in VMware environments was deprecated in Pexip Infinity v23 and will be removed in a future release. From that version onwards, you must deploy your Conferencing Nodes manually, as with other hypervisor environments. As a consequence, VM managers will no longer be required or supported when automatic deployment has been removed.  
RTVideo codec, Lync Server 2010 and Lync 2010 clients no longer supported Support for the RTVideo codec will be removed in Pexip Infinity v25. This means that Pexip Infinity will no longer enable interoperability with Lync Server 2010 and Lync 2010 clients from v25.  

Infinity Connect web app new features and changes

Following are the new features and changes in the Infinity Connect web app in Pexip Infinity version 24:

Feature Description More information
New features
  There are no significant new features in the Infinity Connect web app in Pexip Infinity version 24.  
Changes in functionality
Increased frame rate available when sharing presentation

The maximum frame rate available for sending presentation (set on the client via Settings > Advanced settings > Screen sharing quality) has increased to 30fps.

Note that the actual frame rate at which a presentation is sent will depend on the browser, computer, network quality, and nature of the presentation.

Screen sharing quality