What's new in version 23?

The new features and enhancements and changes in functionality included in Pexip Infinity version 23, 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
Support for "one-touch join" functionality on VTC endpoints

Pexip's One-Touch Join allows users to schedule a meeting in Microsoft Outlook or Google Calendar and include in the invitation a meeting room with a supported videoconferencing endpoint, so that the endpoint in the chosen meeting room displays a Join button just before the meeting is scheduled to begin. Participants can then simply walk into the room and select the button, and the endpoint will automatically dial in to the meeting.

One-Touch Join

Ability to control the maximum call quality for participants connecting to Pexip Infinity services

You can specify the maximum call quality for participants connecting to Pexip Infinity services to be either SD, HD or Full HD (1080p). You can set a global default and override it for each individual service (VMR, Call Routing Rule etc) if required. For example, you could use the default option of "HD" for most of your services, but enable Full HD on some specific services.

The default behavior for new and upgraded systems is HD, unless your system had already enabled the 1080p (Full HD) setting, in which case the default behavior will be Full HD. This new maximum call quality setting replaces the previous global setting to enable 1080p (Full HD).

Setting and limiting call quality
Ability to set bandwidth consumption ratio for presentations When sending main video and presentation to a standards-based endpoint, you can specify at the global platform level the maximum percentage of the call bandwidth to allocate to sending presentation content. The default is 75%, which reflects Pexip Infinity's previous automatic behavior. Managing and restricting call bandwidth
Full support for VP9 codec

The VP9 codec is now fully available for connections to Conferencing Nodes running the AVX2 or later instruction set. It is enabled by default for both new and upgraded deployments.

VP9 uses around one third less bandwidth for the same resolution when compared to VP8. Note however that VP9 calls consume around 1.5 times the CPU resource (ports) on the Conferencing Node.

(VP9 was previously available as technology preview in earlier versions.)

Codecs

Call types and resource requirements

Web proxy support

You can now specify one or more web proxies to use for outbound web requests from the Management Node, and from the Conferencing Nodes in each system location. Web proxies, when configured, are used to route all requests for analytics and incident reporting, and some requests for license activation. Support for other types of outbound web requests will be added in later releases.

Using a web proxy
Administrative improvements

This release contains the following administrative improvements:

  • Participant and backplane media stream statistics now include the framerate being sent and received by the Conferencing Node.

 

  • A new theme audio file, conf-test_call_audio_only_48kHz_mono.wav, that is played out to end-users making an audio-only call to the Test Call Service.
Configuring the Test Call Service
  • A new transform_layout management REST API command can be used to control the layout, overlay text and other in-conference indicators.
Management command API
  • A new boot_time field on the management REST API worker_vm status resource.
Management status API
  • The security wizard contains a new option to enable FIR support.
Deploying Pexip Infinity in a secure mode of operation
  • When using local or external policy, a new overflow_locations field is available when providing a response to a media location request. This optional field can be used to specify multiple overflow locations as an alternative to the primary and secondary overflow location fields that were already supported. This feature is available from version 23.2.
Using external and local policy to control Pexip Infinity behavior
Static NAT on Management Node You can now configure the Management Node with an IPv4 static NAT address. This allows IP-based access to a Management Node behind a NAT when it has an alternative FQDN configured.  
TCP media relay for WebRTC clients * A new global setting that enables media relay on TCP port 443 on all Conferencing Nodes. This is intended as a fallback mechanism for use by WebRTC clients that are behind strict firewalls that block RTP media to Pexip's standard ports. This setting should only be enabled when it is impossible to amend the firewall's rules to allow UDP media, as sending media over TCP can result in increased latency and jitter. Tech preview features
Adaptive Composition layout *

A new global setting that enables the Adaptive Composition layout as an option when selecting the conference Host and Guest view. This is an intelligent layout with real-time automatic face detection and framing.

If you have any feedback on Adaptive Composition, please send it us as described at https://www.pexip.com/ac-feedback.

Tech preview features

* Technology preview only

Pexip Infinity changes in functionality

Feature Description More information
Compatibility updates to the Teams Connector for Microsoft Teams

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

Maintaining your Teams Connector deployment
Teams Connector enhancements

When upgrading your Teams Connector to version 23, you must use the latest deployment scripts as contained within the v23 documentation. There are two significant changes to be aware of when upgrading to v23:

  • The v23 deployment scripts have switched from using AzureRM to Azure PowerShell module (Az).
  • The person performing the upgrade must have been granted Azure Owner permissions for the pre-existing static resource group in Azure.

Note that there are no additional variables required in the initialization script in v23, however the installation process now performs a case-sensitive check to ensure that the $PxTeamsConnFqdn variable matches the name in the Teams Connector's certificate. As with all upgrades, you can continue to use the Pexip CVI app from your existing deployment.

Full instructions are available at Upgrading the Teams Connector to the latest software.

Other changes and improvements to the Teams Connector include:

  • VMSS (virtual machine scale set) disk encryption is now always enabled. Hence, the $PxTeamsConnDiskEncryption variable in the variable initialization script is no longer used or required.
  • Access keys for the storage account that is used for logging are managed by Azure Key Vault and are regenerated every 90 days.
  • Improved quality of presentation streams from a VTC into a Teams meeting. Teams clients on poor networks can now request a presentation stream at a lower framerate without affecting the quality received by other clients on better networks that are connected to the same Teams meeting.
  • More informative error messages for deployment failures, including more extensive and up-front checking for certificate-related issues.
  • When viewing log messages and participant status in the Pexip Infinity Administrator interface, Teams clients in a meeting are now shown in the name@domain format (previously shown as an id).
Maintaining your Teams Connector deployment
Recording indicators when a Skype for Business / Lync client records a conference The recording indicator is now shown If a Skype for Business / Lync client records a conference (previously the streaming indicator was shown). Streaming and recording a conference
New address for outbound connections to Google Hangouts Meet Conferencing Nodes now connect out to Google Hangouts Meet at hangouts.clients6.google.com (previously clients6.google.com). This change applies as of version 23.2. Configuring Pexip Infinity as a Google Hangouts Meet gateway
Administrative modifications

This release contains the following administrative modifications:

  • Pexip Exchange Integrations (configured as part of the VMR Scheduling for Exchange feature) have been renamed VMR scheduling for Exchange integrations. This is to distinguish them from One-Touch Join Exchange integrations which are configured as part of the new One-Touch Join feature.
 
SSE4.x no longer supported

As of Pexip Infinity v12, the SSE4.x instruction set was only supported in deployments that had upgraded from a previous version — SSE4.x was not supported in new deployments using v12 or later.

As of 1 January 2020, deployments on SSE4.x hardware are not supported at all. You must ensure that all Conferencing Nodes in your deployment are relocated to hardware using the AVX or later instruction set.

To check the instruction set for each Conferencing Node, go to Status > Conferencing Nodes, select the Conferencing Node and scroll down to CPU instruction set.

 
vSphere ESXi 4.1 no longer supported As of 1 January 2020, deployments using vSphere ESXi 4.1 are no longer supported. This is a consequence of the removal of support for SSE4.x.  

Planned changes in future releases

Feature Description More information
Automatic deployments on ESXi no longer supported Automatic deployment of Conferencing Nodes in VMware environments is deprecated in Pexip Infinity v23 and will no longer be available from v25. 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 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 23:

Feature Description More information
Performance improvements

End users should experience lower CPU usage during calls, and improved performance in large meetings.

 
In-conference timeline is disabled by default

The timeline shown at the bottom of the screen during a conference is now disabled by default.

To enable it you can configure the new showTimeline customization option in the settings.json file in a web app branding package.

Advanced Infinity Connect customization
"You're muted" detection is disabled by default

The ability to display a message in selfview saying "You're muted" if the user's microphone detects sound while it is locally muted is now disabled by default.

To enable it you can configure the new micSampling customization option in the settings.json file in a web app branding package.

Advanced Infinity Connect customization
No support for Infinity Connect web app on Internet Explorer As of 1 January 2020, we no longer provide support for customers using the Infinity Connect web app with Microsoft Internet Explorer.