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 25

Pexip Infinity version 25 added the following features and enhancements:

Feature Description More information
Adaptive Composition layout

Adaptive Composition is a new layout option for Virtual Meeting Rooms:

  • Powered by AI and machine learning to give users a more natural, engaging, video-first meeting experience.
  • It continuously analyzes each video feed from all participants and uses automatic face detection and framing to create an optimized view of that participant, or group of participants where there are several people in that video feed.

  • Independent of where the participants are and which device they are using. No end-user action or configuration is required.

Adaptive Composition was available as "tech preview" in previous versions of Pexip Infinity.

Selecting the layout seen by participants
Epic telehealth integration with Pexip Infinity

Pexip's Epic telehealth integration enables healthcare organizations to hold video-based visits in Pexip Virtual Meeting Room (VMRs). The Pexip solution:

  • Provides secure, easy-to-join telehealth visits from any location.
  • Integrates seamlessly with Epic's standard video visit workflow.
  • Uses context-aware linking within an Epic appointment to enable providers and patients to meet together over video.
  • Allows providers (physicians/doctors) to directly launch their video visit from Hyperspace, Haiku, Canto or EpicCare.
  • Allows patients to launch the video visit directly from MyChart.
  • Supports clinic-to-clinic and teleconsult workflows (remote provider).
  • Requires no downloads or plugins.
  • Enables HIPAA compliance.

Epic Electronic Health Record (EHR) customers include hospitals, health systems, and physician practices.

Epic telehealth integration with Pexip Infinity
Pexip Smart Scale, hosted in the Pexip Private Cloud The Pexip Smart Scale (PSS) feature allows you to have Conferencing Nodes that are deployed by Pexip on your behalf within the secure Pexip Private Cloud, in the form of Pexip Smart Scale locations. You can add or remove these locations, and scale their capacity up or down, according to your own deployment's changing requirements. Enabling Pexip Smart Scale
One-Touch Join enhancements

The One-Touch Join feature now includes:

  • support for endpoints registered to Webex that are on a separate network to your Conferencing Nodes (such as those used in a home office)
  • the ability to disable alarms for all endpoints
  • the ability to customize the meeting subject for all meetings, or for private meetings only.
About One-Touch Join
VMR Scheduling for Exchange enhancements

The VMR Scheduling for Exchange feature now includes:

  • the ability to schedule meetings in users' personal VMRs
  • a change to the way in which the public key of the Microsoft Exchange Server Auth Certificate is obtained, meaning that you no longer need to provide all the FQDNs of all the Exchange servers in your deployment; instead, you only need provide a single URL for each certificate in use.

Scheduling Pexip Infinity meetings using Microsoft Exchange
Teams Connector enhancements

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

  • Enhanced Teams Connector instance status within Pexip Infinity, showing call capacity and media load (Status > Live View and Status > Microsoft Teams Connectors). After upgrading, enhanced status reporting has to be enabled within Pexip Infinity via Call control > Microsoft Teams Connectors. You must also ensure that your Pexip Infinity Management Node can communicate with the new Azure Event Hub component that is created as part of the Teams Connector upgrade.
  • Transcription indicators are displayed and messages are played to CVI participants when a Teams conference is being transcribed.
  • A recording indicator is now shown on VTC systems that are gatewayed into Teams live events.
  • Improved/more granular disconnection reasons for VTC systems leaving Teams meetings are shown in the Pexip Infinity Administrator interface and administrator logs.

Other changes and improvements to the Teams Connector include:

  • Version 25 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.
  • You must be using Az module version 4.7.0 or later.

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

Integrating Microsoft Teams with Pexip Infinity

Upgrading the Teams Connector to the latest software

Viewing Teams Connector instance, call and participant status

New theme elements for participants in a Microsoft Teams meeting

The following theme elements have been added to support the new Microsoft Teams integration features (as described above) for participants that are in a Teams meeting:

  • New icon_transcribing.svg graphic which is displayed when a conference is being transcribed (icon_transcribing.png in legacy version 1 themes).
  • New transcribing_indicator_text setting in the themeconfig.json file. This defaults to "Transcribing" and is temporarily displayed when a conference is being transcribed.
  • Two new audio files that are played when conference transcribing is used:

    • conf-transcribing_started_48kHz_mono.wav ("This call is being transcribed.")

    • conf-transcribing_stopped_48kHz_mono.wav ("Transcribing of this call has stopped.")

Rules and requirements for customized themes
WebRTC and ICE connectivity improvements

All WebRTC and ICE clients connecting to Conferencing Nodes have:

  • Significantly improved initial connection times over WebRTC.
  • Improved resilience/reconnection when a WebRTC connection is interrupted, or there is a change in network.
 
Event sink improvements

There are a range of new event sink management features for administrators:

  • You can configure a set of options that control connectivity and failure retry limits (Platform > Global settings > Advanced event Sink Tuning).
  • There is an easier method to restart an event sink via a restart button (System > Event sinks and then select the event sink).
  • A new "Eventsink Reached Maximum Concurrent POSTs" alarm is raised if more than 1000 events are queued but have not been sent.
  • Within the API, all participant_connected, participant_updated and participant_disconnected participant events include a new related_uuids field which is a list of related participant events.
  • There is now a version 2 of the API, which is the default when creating a new event sink. In version 2:

    • There are new participant_media_stream_window and participant_media_streams_destroyed participant events.
    • The media_streams field is not included in participant_disconnected events.

Using event sinks to monitor conference and participant status

Event sink API

Administrative improvements

The v25.3 release contains the following administrative improvements:

  • In policy, there is a new "prefer_ipv6" field in service configuration responses. This determines whether to use IPv6 for SIP media when dialing out from Pexip Infinity.
Using external and local policy to control Pexip Infinity behavior
  • The security wizard contains a new Tolerate iPAddress SubjectAlternativeNames in SIP/TLS certificates option. The default is No. Setting it to Yes enables Pexip Infinity to accept IP Address-type Subject Alternative Name entries in certificates used for SIP/TLS.
Deploying Pexip Infinity in a secure mode of operation

Changes in functionality in version 25

Feature Description More information
Dialing out from an ongoing conference via Infinity Connect or the client API

There is a new Enable legacy dialout API setting (Platform > Global settings > Connectivity) that controls the system behavior when dialing out via an Infinity Connect client or the client API to a participant from an ongoing conference.

When selected (enabled), calls placed via the:

  • Infinity Connect client always use automatic routing and thus must match an appropriate Call Routing Rule.
  • Client API or the legacy (webapp1) client can either use automatic routing or they can specify a dial-out protocol without any need for a Call Routing Rule i.e. it allows end-users to perform arbitrary dial outs (and thus circumvent any administrator-set rules).

When not selected (disabled), calls that are placed via:

  • Any Infinity Connect client or via the client API always use automatic routing and thus must match an appropriate Call Routing Rule.

Note that dial out via the Administrator interface, management API or Automatically Dialed Participants (ADPs) is unaffected by this setting.

This new setting is disabled by default on upgrade and for new installations.

This means that when dialing out from an ongoing conference, any calls made via an Infinity Connect client (including RTMP calls to a streaming or recording service) now always use automatic routing and thus must match an appropriate Call Routing Rule for the call to be placed.

Manually dialing out to a participant from a conference
New recommended format for creating preconfigured links to launch conferences via the Infinity Connect web app

As of version 25, we recommend that the following URL structure is used when creating preconfigured links to launch a specific conference via the Infinity Connect web app:

https://<address>/webapp/#/?conference=<alias>&<any other parameters>

When using this format, the join parameters (conference alias and any other parameters such as the PIN), are automatically removed from the URL that is displayed in the browser's address bar.

Note that:

  • This URL structure will not work on version 24 or earlier of Pexip Infinity, but any URLs using the previously recommended structure (https://<address>/webapp/conference/<alias>?<parameters>) will still work on v25 and later, and the join parameters (but not the alias) will be removed from the browser's address bar.

  • This structure is now used in the default VMR join instructions template when adding a new VMR Scheduling for Exchange integration.
Creating preconfigured links to launch conferences via Infinity Connect
NTP configuration Due to improvements in v25, it is critical that NTP is correctly configured across the platform (i.e. on the Management Node and all Conferencing Nodes) and that there are no "NTP Not Synchronized" alarms present.  
Administrative modifications

This release contains the following administrative modifications:

  • When deploying a Conferencing Node on an ESXi host you can now choose either Manual (ESXi 6.7 and above), Manual (ESXi 6.0 and 6.5) or Manual (ESXi 5.x) as appropriate. Note that:
    • AVX2 instruction set requires ESXi 6.0+ and VM hardware version 11+
    • AVX512 instruction set requires ESXi 6.7+ and VM hardware version 14+

 

Deploying a Conferencing Node on an ESXi host

Upgrading VM hardware versions

  • In a 2 + 21 layout, up to 3 HD streams may now be sent between any 2 nodes (up to 2 current speakers and potentially 1 previous speaker). This means that a main speaker will now always see the other main speakers at high resolution.
 
  • When taking packet captures (Utilities > Packet capture), WebRTC encryption keys may also be captured.
Performing a network packet capture
  • Backup files produced by Pexip Infinity's inbuilt backup and restore mechanism now have a .pexbak extension, rather than .gpg.
Backing up and restoring configuration

Features added in version 24

Pexip Infinity version 24 added the following 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 is now used when the Management Node communicates 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 is now used for outbound One-Touch Join-related requests to Cisco endpoints, Exchange, and Google Workspace.
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.
Using event sinks to monitor conference and participant status
  • 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

Changes in functionality in version 24

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

Features added in version 23

Pexip Infinity version 23 added the following features and enhancements:

Feature Description More information
Support for "one-touch join" functionality on VTC endpoints

Pexip's One-Touch Join (OTJ) allows users to schedule a meeting in Microsoft Outlook or Google Calendar and include in the invitation a meeting room with a supported Cisco or Poly 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.25 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, Epic telehealth requests, some requests for license activation, requests from the Management Node to cloud service providers, and One-Touch Join requests. 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 frame rate 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

Changes in functionality in version 23

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 frame rate 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 Meet Conferencing Nodes now connect out to Google Meet at hangouts.clients6.google.com (previously clients6.google.com). This change applies as of version 23.2. Configuring Pexip Infinity as a Google 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.  

Features added in version 22

Pexip Infinity version 22 added the following features and enhancements:

Feature Description More information
Far-End Camera Control (FECC) support Endpoints that support FECC can now be controlled by a Host participant using an Infinity Connect client. FECC support is configurable at the global platform level, and is enabled by default.

About global settings

Control another participant's camera

Improved WebRTC resilience in poor networks There is improved resilience to poor or constrained network conditions for the video sent from WebRTC clients to a Pexip Infinity Conferencing Node. A WebRTC client that supports Google Congestion Control, such as the Infinity Connect clients, can now adapt more quickly to deteriorating network conditions and downspeed the video it sends to Pexip Infinity, while preserving the bandwidth allocated for audio packets.  
Ability to enforce encrypted-only calls

You can control the media encryption requirements on calls placed via Pexip Infinity. You can specify at the global platform level whether calls placed into a Pexip service (such as a Virtual Meeting Room or via a Call Routing Rule must be encrypted, use encryption when available i.e. "best effort", or whether encryption is not required. You can then override the standard behavior for each individual service if required.

The default behavior for new and upgraded systems is "best effort" (which is how all calls were treated in previous versions).

About global settings

About Pexip Infinity conferences

Google Meet integration improvements

The following improvements have been made when integrating Google Meet with Pexip Infinity:

  • Full support for duo video between VTC participants and native clients: when a VTC participant presents content, the other participants in the conference will see both the presentation stream and the video from that participant (duo video was already supported to VTC participants when a native Google Meet client presented content).
Integrating Google Meet with Pexip Infinity
Improved control of content sent to a streaming service

The client API transform_layout conference control option has a new streaming parameter which allows you to control the content sent to a streaming participant (such as a YouTube broadcast).

This allows you, for example, to send a different layout to the stream from that seen by standard participants, or to temporarily send a new "holding" splash screen while you are waiting for people in the conference to get ready to start.

You can invoke this functionality either by implementing your own calls directly to the client REST API, or by using the transformConferenceLayout Infinity Connect plugin function.

Pexip client REST API

Creating and deploying Infinity Connect plugins

New theme elements for streaming participants and for Google Meet public streaming

The following elements (that apply to version 2 style themes only) have been added to support streaming participants:

  • New icon_streaming_screen.svg graphic which is displayed on the 2 new splash screens described below.
  • New stream_waiting splash screen which is used in conjunction with the client API transform_layout conference control.
  • New streaming_in_progress splash screen which is shown if there are no other participants in the conference other than a streaming participant.

The following theme elements have also been added to provide support in the future for public streaming from a Google Meet conference:

  • New audio files for streaming started/stopped messages:

    • conf-public_streaming_started_48kHz_mono.wav
    • conf-public_streaming_stopped_48kHz_mono.wav
  • New setting in the themeconfig.json file for the public streaming indicator text:

    • public_streaming_indicator_text
  • New graphics file for the public streaming indicator icon (applies to version 2 style themes only):

    • icon_public_streaming.svg
Rules and requirements for customized themes
Administrative improvements

This release contains the following administrative improvements:

  • Several new administrator alarms have been added to indicate:

    • LDAP sync provisioning failures
    • PIN brute force resistance detections
    • VOIP scanner resistance detections

Viewing alarms

 

  • Live View updates:
    • Live view and conference graphs can be filtered by participant or conference name.
    • The timeline now indicates historical call quality issues for participants and backplanes.

Viewing live and historical platform status

Changes in functionality in version 22

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

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

Maintaining your Teams Connector deployment
Single Teams Connector CVI app and new installation/upgrade scripts

In version 20 and 21 of the Teams Connector, Pexip used a trusted app and a guest app to connect participants to Teams meetings. In version 22 and later, only the trusted app is required, which now performs both the trusted and guest joining workflows, and is now referred to as just the Pexip CVI app.

Maintaining your Teams Connector deployment
Updated default Pexip logo and avatar

The default Pexip logo has changed from    to    and the avatar image has changed to .

This affects the following end-user facing features:

  • Themes: the in-conference video watermark watermark_icon.png file and the conference avatar presence_avatar_image.jpg file. If your services (VMRs etc) use the base Pexip theme then the new watermark and avatar logo files will take effect automatically. They will also take effect automatically if you use a customized theme, unless you have explicitly included an alternative watermark_icon.png or presence_avatar_image.jpg file in your theme. Note that the change to the avatar may take some time to appear in SfB/Lync users' contact lists due to caching.
  • Infinity Connect web app: the Pexip watermark shown in the selfview prior to joining a conference. If you use the default web app branding then the new watermark will take effect automatically. It will also take effect automatically if you have customized your web app, unless you have explicitly included an alternative watermark_icon.png file in your branding package.
  • VMR Scheduling for Exchange: the default Add-in image icon, which appears on the add-in button in Outlook clients. If you have uploaded your own icon, this will remain in use on upgrade to v22. If you have not uploaded an icon, the icon will change to the new default. Note that Outlook clients may cache the add-in icon, so it may be some time after upgrade that the new icon appears.

Customizing the Pexip Infinity user experience

 

Adding a VMR scheduling for Exchange integration to Pexip Infinity

Streaming/recording participants are not included in stage layout When a conference participant is flagged as a streaming/recording participant, that participant is now treated as a receive-only participant and it is no longer included in the video stage layout seen by other participants. Streaming and recording a conference
Administrative modifications

This release contains the following administrative modifications:

  • Any leading and trailing whitespace is now stripped from content entered into text boxes in the Administrator interface.
 
  • Previously when using the client REST API transform_layout conference control option, if you made multiple requests for the same conference you had to keep track of the state and respecify all of the relevant parameters in each request. In version 22, if you make multiple requests for the same conference, the changes are applied cumulatively (with the most recent settings taking precedence).

Pexip client REST API

  • In the Administrator interface, Microsoft Azure tenants are now referred to as Microsoft Teams tenants.
Configuring Pexip Infinity as a Microsoft Teams gateway
  • The setting to Enable support for Pexip Infinity Connect and Mobile App has been renamed to Enable support for Pexip Infinity Connect clients and Client API. If an administrator disables this option, they will get a warning that it will also disable WebRTC and RTMP calls.
Enable support for Pexip Infinity Connect clients and Client API
Service tag added to participant events When participant events are logged, they now include the service tag of the associated conference. Tracking usage via service and participant call tags