Features added in previous versions

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

This topic covers the Pexip Infinity platform; for features added in previous versions of the Connect web app see the Connect web app release notes.

Features added in version 33

Pexip Infinity version 33 added the following features and enhancements:

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.

    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.
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*

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

Changes in functionality in version 33

Feature Description More information
Pexip Smart Scale

Pexip Smart Scale has been removed from Pexip Infinity.

 
Management API schema The Management API schema has moved from /api/admin/schema/ to /admin/platform/schema/. Using the management API
Management API rate limiting The rate limit of requests to the management API has been reduced from 10,000 requests every 60 seconds to 1000 requests every 60 seconds.  
Removed support for Xen Support for Xen hypervisors has been removed.  
OTJ: Automatic URL Defense decoding

One-Touch Join now automatically decodes any URLs within a meeting invitation that have been encoded by Proofpoint's URL Defense, thus improving the ability of the default meeting processing rules to extract the correct meeting alias.

 
Resource usage for voice activity features Voice Focus and Softmute now use the equivalent of an extra 6 audio connections per participant (previously an extra 4). Voice activity features

Features added in version 32

Pexip Infinity version 32 added the following features and enhancements:

Feature Description More information
Teams Connector enhancements: improvements to the Teams-like layout* and support for Large Gallery view*

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

  • New layout features:

    • The Teams-like layout now supports multiscreen participant display and receiving the presentation stream as part of the layout mix. Note that this layout is still a technology preview feature, and is only recommended for use with Teams gateway calls.
    • Support for Microsoft's Large Gallery view: you can introduce a DTMF conference control command ("toggle_teams_large_gallery") into your themes that allows VTC participants to toggle between their current layout and Microsoft's Large Gallery view. Toggling to Large Gallery view is a technology preview feature in this release.
  • Changes to the installation/upgrade scripts are:

    • Microsoft Graph PowerShell is now used for creating the Teams Connector API app and for deploying the Teams Connector.
    • You must be using Az module version 9.0.1 or later (previously it required 7.0.0 - 8.3.0).
    • The strong API app password generation is now performed by Microsoft Entra ID.

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

  • Other administrative changes are:

    • The v32 Pexip Teams Connector uses the latest Microsoft Teams SDK for interoperability. This latest SDK addresses issues with the previous SDKs and also provides new features which will be used in future releases of the Teams Connector. However, there is a change in call capacity meaning that each Teams Connector instance can now handle approximately 10 calls (previously 15), although the exact capacity of each instance can vary depending on various factors such as call resolution, the number of presentation streams, and the number of participants in the Teams meetings. Microsoft are currently working on increasing the call capacity for a future release of their SDK.

      Users of scheduled scaling should review the number of instances that they need to add, and then adjust their scaling policies as appropriate.

    • The destination port ranges from Microsoft Teams (O365) to the Teams Connector load balancer are now 11000-11399 and 12000-12399 (previously they were 10000-10399 and 11000-11399). Note that these changes do not affect the Teams Connector Network Security Group (NSG) rules as they operate behind the load balancer.
    • Azure Storage key rotation is no longer performed as shared key authentication is now disabled. In addition, Teams Connector VMs now use managed identities instead of SAS tokens to access storage accounts.
New Microsoft Teams SIP Guest Join meeting type for One-Touch Join

When configuring One-Touch Join meeting processing rules, there is a new Microsoft Teams SIP Guest Join option for the meeting type. This replaces the need to use a custom rule when enabling the "SIP Guest Join" feature for Teams.

Note that the format of invitations to cloud-based or externally-managed meetings can often change. Using the latest versions of Pexip Infinity and the dedicated OTJ meeting types will ensure best future compatibility.

Enabling SIP Guest Join
Join instructions page hosted on Conferencing Nodes Conferencing Nodes can now generate a webpage where the full set of join instructions for a specific VMR is shown. These join instructions can optionally include a QR code, which when scanned by a device with a supported Connect app installed (such as the Connect mobile app) will open the meeting directly in the app. Links to a join instructions page
Customizable display names for Epic telehealth appointments You can now customize the provider and patient display names for Epic telehealth appointments via the new Template for provider display names and Template for patient display names options when configuring an Epic telehealth profile. Configuring Pexip Infinity to integrate with Epic telehealth
Administrative improvements (site banner, search, configurable automatic backups)

This release contains the following administrative improvements:

 
  • You can now configure a site banner to appear across the top of every webpage of the Pexip Infinity Administrator interface. You can go to Platform > Global settings > Management web interface configuration and define the text to display, and choose the text and background colors.
Management web interface configuration
  • The Pexip Infinity Administrator interface now contains a search box (above the menu bar) that lets you search for configuration settings based on their associated menu, field name or field label text.
Using the Pexip Infinity Administrator interface
  • When enabling automatic backups, you can now configure the start hour per day and set it to run multiple times per day.
Enabling automatic backups

Changes in functionality in version 32

Feature Description More information
TLS certificates with legacy signature algorithms Pexip Infinity v32 and later require TLS certificates with SHA256 or later signature algorithms. Certificates using legacy algorithms such as SHA1 and MD5 must be removed from the system before upgrade.  

TLSv1.3 is now enabled on all services

In addition to TLSv1.2, TLSv1.3 is now enabled on all services by default (and cannot be disabled).

Deployments running in FIPS compliance mode

Pexip Infinity v32 and later running with FIPS cryptography enabled now has FIPS 140-3 compliance and requires RSA private keys that comply with SP800-56b. Any keys generated by earlier Pexip Infinity versions running with FIPS cryptography enabled are already compliant. The upgrade process will endeavor to fix any non-compliant keys installed on the system, but there is a small subset of possible keys that cannot be fixed (the Certificates > TLS Certificates page on the Administrator interface will display a status of "Private key is unusable" for any such key, and those keys will then need to be replaced). Administrators uploading their own keying material must ensure compliance with SP800-56b (any non-compliant keys will be rejected).

Deploying Pexip Infinity in a secure mode of operation
Security wizard removal of X-Frame-Options setting, and an additional default CSP frame-ancestors directive

The X-Frame-Options setting has been removed from the security wizard. The CSP frame-ancestors directive supersedes the X-Frame-Options setting and the system now calculates the X-Frame-Options value based on the configured CSP (Global Settings > Security > HTTP Content Security Policy Header).

The default CSP for new installations now includes frame-ancestors 'self'.

On upgrade to version 32, frame-ancestors 'self' will be automatically added to the existing CSP unless there is an existing frame-ancestors directive.

About global settings
Install wizard new email address option

When running the installation wizard, if Enable incident reporting is selected, administrators are now required to provide a contact email address. (This address can be changed at any point after installation via Platform > Global settings > Reporting > Contact email address.)

The address will be used by Pexip Support when following up on any incident reports received from your deployment.

Re-running the installation wizard
Voice Focus performance improvements

Voice Focus (a voice activity feature that distinguishes between actual speech and background noise) has improved accuracy and better performance. When enabled it now uses the equivalent of an extra 4 audio connections per participant (previously an extra 6).

Voice activity features
Concurrent call licenses statistics no longer split by location The usage statistics showing the maximum number of concurrent call licenses used per day is now a single daily total, and is no longer split by location. Viewing usage statistics
Hardware resource usage for presentations in Teams calls To improve the accuracy of the platform's resource management, extra hardware resources are now accounted for in a gateway call to a Microsoft Teams meeting. If a VTC participant presents content, additional resources are allocated on the Teams backplane while the presentation is in progress. Hardware resource allocation rules

Infinity Connect legacy webapp

The original "legacy" version of the infinity Connect web app, "Webapp1", is no longer actively developed or maintained and has been removed from the default installation of Pexip Infinity.

If you still require access to this version, please contact your Pexip authorized support representative.

About Connect web app versions

Features added in version 31

Pexip Infinity version 31 added the following features and enhancements:

Feature Description More information
Layout enhancements

Pexip's conference layouts have been enhanced:

  • The multiscreen participant display feature, which allows SIP and H.323 endpoints with dual screens to display conference participants across both screens, is now generally available. It was a technology preview feature in previous releases. Enhancements in this release include support for the Adaptive Composition layout, H.323 endpoints, and calls into Google Meet conferences.
  • Pexip's Adaptive Composition layout is now fully supported (generally available) for Google Meet calls (previously this was a technology preview feature).
  • Streaming participants can now view the presentation stream as part of the layout mix with the video stream of the active speaker shown alongside the presentation, if the main conference is using Adaptive composition layout. This option is enabled by default and can be configured using the ac_presentation_in_mix parameter in the transform_layout function of Pexip client REST API or PexRTC JavaScript client API.

Controlling the layout during a conference

Conference layout

Pexip client REST API

PexRTC JavaScript client API

New authentication requirements for Google Meet interoperability

Google Meet is transitioning to a new method of authenticating third-party systems that join a Google Meet conference via Pexip's interoperability gateway.

The new method uses the JWT (JSON Web Token) standard. To use JWT as your authentication method you need to upload to your Pexip Infinity system a token that has been signed by Pexip. This token then provides the authentication between your Pexip Infinity system and Google Meet whenever a third-party device uses Pexip's interoperability gateway to join a Google Meet conference.

If you do not upload a gateway token you will still be able to use Pexip's interoperability gateway in the short term, but we expect Google Meet to enforce JWT authentication in the near future. You must obtain and install your gateway token as soon as practicable after upgrading to version 31 or later.

Requesting and uploading your gateway token
NTLM support One-Touch Join and VMR Scheduling for Exchange now support NTLMv2 authentication for the service account in deployments using Exchange on-premises.

Configuring Exchange on-premises for scheduling

Configuring Exchange on-premises for One-Touch Join

Web proxy support for VMR Scheduling for Exchange VMR Scheduling for Exchange now uses the Management Node web proxy (where configured) for outbound requests. You can optionally elect to bypass the web proxy for individual Exchange integrations.

Using a web proxy

Disable web proxy

Web proxy bypass for OTJ One-Touch Join now has an option to bypass a system location's web proxy for Cisco OBTP endpoints (configured on a per-endpoint group basis).

Using a web proxy

Disable web proxy

Customizable web app paths and branding

Connect web app branding and customizations are now applied using unique URL paths. For each path, you can configure which web app version and branding users are offered when accessing the web app via that path, and you can create and configure additional paths to offer users a variety of differently-branded web app experiences within your environment.

Note that this new feature will require you to change any existing branding packages. For more information, see Changes in functionality in version 31.

Creating path-based web app branding
In-conference security classification indicators

Content classification indicators can be displayed within a conference to, for example, display the current security classification level to meeting participants.

When content classifications are configured in a theme, the specified classification text is overlaid (similar to a watermark) onto the video layout and splash screens during a conference. It is displayed in white text on a dark background by default, but the colors can be customized. In classic layouts it is positioned at the top of the screen, and in Adaptive Composition it is placed in the bottom-right corner.

  • Classification indicators are text only.
  • They are not included in the base theme. You must create and upload your own theme that includes your classification text strings.
  • You cannot configure the position, font or size of the message.

The classification indicator can be dynamically changed during the conference to display a different message. To change the classification level, you must use the new set_classification_level client API conference control function (/api/client/v2/conferences/<conference>/set_classification_level).

Rules and requirements for customized themes

Pexip client REST API

Teams Connector enhancements: improvements to the Teams-like layout* and support for dedicated hosting plans for Azure functions and VNet integration

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

  • The Teams-like layout has been improved:

    • A microphone muted icon is shown next to a participant's name if that person is muted.
    • If an off-screen video participant (shown as an audio avatar) starts speaking they are now promoted into the video layout.
    • Note that this layout is still a technology preview feature, and is only recommended for use with Teams gateway calls.

  • Other administrative changes to the installation/upgrade scripts and variables include new settings that optionally allow you to deploy the Teams Connector with dedicated hosting plans for Azure functions and with VNet integration.
New theme content to support the latest features

A new configuration item has been added to themes to support the new content classification features:

  • A new classification object can be defined with a theme to specify the content classification messages and the default classification level. Note that this object is not included in the base theme. You must create and upload your own theme that includes this object.

New configuration items have been added to version 2 themes to support the new direct media features:

  • Five new splash screens: "direct_media_welcome", "direct_media_waiting_for_host", "direct_media_other_participants_audio_only", "direct_media_escalate" and "direct_media_deescalate".
  • Two new labels: "direct_media_escalate" and "direct_media_deescalate".
Rules and requirements for customized themes
Conferencing Nodes can now use TURN servers configured in permissive mode Conferencing Nodes now support the use of time-limited credentials for server-side WebRTC TURN allocations. This means that a TURN server that is configured in permissive mode can now be used for both client and server-side allocations. Using TURN servers with Pexip Infinity
One-Touch Join Graph API: additional FQDNs It is now possible to configure the FQDN used to connect to the Graph API, for deployments where the default (graph.microsoft.com) is not appropriate.  
Media relay on TCP port 443 is now generally available

The option to enable media relay on TCP port 443 is now generally available. It was a technology preview feature in previous releases.

This setting (Platform > Global Settings > Enable media relay on TCP port 443) enables media relay on TCP port 443 on all Conferencing Nodes. It 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.

Global settings
Direct Media for end-to-end encrypted calls is now generally available

Pexip's direct media feature, which enables end-to-end encrypted calls, is now generally available. It was a technology preview feature in previous releases.

When enabled in a VMR, it provides non-transcoded, encrypted, point-to-point calls between any two WebRTC participants.

Enhancements in this release include:

  • Welcome screen and notification messages can be customized via themes.
  • Full configuration support in local and external policy, VMR provisioning via LDAP, and bulk CSV import/export of VMR data.
  • Perceived call quality statistics are available in the Administrator interface.
Direct media (end-to-end encrypted calls)
Voice Focus is now generally available

Pexip's Voice Focus feature, which provides improved voice activity detection, is now generally available. It was a technology preview feature in previous releases.

When enabled (Platform > Global Settings > Enable Voice Focus), this feature applies to all Virtual Meeting Rooms and Virtual Auditoriums.

Global settings
Administrative improvements

This release contains the following administrative improvements:

 
  • When the Softmute* feature is enabled at the global level (Platform > Global settings > Tech preview features > Enable Softmute), it can now be individually enabled or disabled at the VMR level (Services > Virtual Meeting Rooms > Advanced options > Softmute).
Tech preview features

* Technology preview only

Changes in functionality in version 31

Feature Description More information
Selection of default web app The way in which you select which version of the web app is offered to users by default has changed. Previously this was done via the Default web app option under Platform > Global settings > Connectivity; now this is set via the new Web App > Web App Paths page. Default paths and default branding
Branding of previous web app "Webapp2"

The directory structure of the ZIP file containing the branding customizations for the previous version of the Connect web app, "Webapp2", has changed.

Any existing custom branding applied to Webapp2 prior to upgrade will be automatically ported to the new structure (although you must associate it with a web app path in order to use it).

Any v30 or earlier Webapp2 branding packages generated by the Pexip Branding Portal, downloaded from a v30 or earlier deployment, or created manually, will need to be restructured before being uploaded to the Management Node. For full details, see Using a pre-v31 Webapp2 branding package.

 
Hardware resource usage To improve the accuracy of the platform's resource management, extra hardware resources are now accounted for when sending main video and presentation content to a standards-based (SIP or H.323) or WebRTC endpoint, and to dual-screen endpoints, than when compared to only sending main video. Hardware resource allocation rules
Default maximum outbound call bandwidth bitrate The default maximum outbound call bandwidth bitrate has changed to 4 Mbps. Previously it could have used up to 8 Mbps, and it can still be configured to any rate up to 8 Mbps.  

Features added in version 30

Pexip Infinity version 30 added the following features and enhancements:

Feature Description More information
Teams Connector enhancements: improved certificate management, and new Teams-like layout*

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

  • Management of the Teams Connector certificate has been improved:

    • The certificate is now stored in the Azure key vault and can be updated without having to redeploy the Teams Connector.
    • New alarms are raised on Pexip Infinity when the Teams Connector certificate is due to expire within the next 30 days, and if it has expired.
  • There is a new Teams-like layout for VTC systems that looks and operates in a similar manner to the meeting experience seen by native Teams clients. In this layout, spotlighting, use of avatars for audio-only participants, active speaker indication and raised hand indicators all have a similar look and feel to the native Teams layout. Note that:

    • The layout cannot be customized via themes.
    • It has the same hardware resource usage requirements as the Adaptive Composition layout.
    • This layout is a technology preview feature, and is only recommended for use with Teams gateway calls.
  • Content presentation is now stopped if a CVI participant's role is changed to Attendee while it is currently presenting to the conference.

  • Other administrative changes are:

    • You must be using Az module version 7.0.0 or later (previously the minimum was 5.1.0).
    • The procedure for uploading Teams Connector logs to Pexportal has changed.
Raised hand indicator in classic layouts

When a participant raises their hand, an indicator slides out on the left side of the layout, and remains in view while the hand is raised. This applies to classic layouts only (i.e. not supported in Adaptive Composition layouts), and is typically only used by default in Virtual Auditoriums.

There is an associated, new themes graphic icon_raise_hand.svg.

Raised hands
Updated Connect web app

A new release of the Connect web app, "Connect Webapp3", is now available. This release includes:

  • an updated user interface
  • revised join flows — one for regular users, and one for less experienced or "guest" users that guides them through their pre-call setup
  • background replacement
  • native support for over 20 languages; additional languages can be added by an Administrator
  • simplified branding
  • noise suppression
  • improved troubleshooting
  • WCAG 2.0 compliance (for accessibility)

  • integrated support for upcoming new Pexip Infinity features.

Administrators can choose which version of the Connect web app is offered to users by default via the Global Settings page. Note that this has resulted in a change in functionality around the how the default web app is determined, and the preconfigured URLs used to access the web app.

Additionally, users themselves can elect to use a specific web app version by appending /webapp2/ or /webapp3/ to the IP address or domain name of a Conferencing Node (or reverse proxy), for example:
https://meet.pexample.com/webapp3/

About Connect web app versions

Using Webapp3

Presentation audio support

The Connect web apps now support sharing audio when you share your screen in a conference.

When you select Share my screen, there is a new option to Share system audio (if you share your entire screen), or Share tab audio (if you share a browser tab).

Supported on Chrome and Edge browsers only. On Mac and Linux, you can only share audio from a browser tab. On Windows you can share either system audio or browser tab audio.

Using Connect apps to share content
Google Meet interoperability improvements: denoising, transcribing prompts, and DTMF layout controls

Pexip's Google Meet integration has been enhanced:

  • Background noise is now removed from the audio streams. This feature is enabled by default but can be configured via a new Denoise audio setting when configuring the Call Routing Rule for Google Meet integrations. There is also an associated new built_in_denoising object in the vendordata.json theme customization file where you can identify any endpoints that perform their own built-in denoising.
  • If a Google Meet conference is transcribed, relevant audio prompts indicating that transcribing has been started/stopped are played to callers who are gatewayed via Pexip Infinity into the conference, and a transcribing indicator is displayed.
  • VTC participants can now use DTMF/keypad controls to control the meeting layout during an ongoing conference.
Configuring Pexip Infinity as a Google Meet gateway
Support for Korean and Traditional Chinese language The Pexip Infinity Administrator interface now supports Korean and Traditional Chinese language. Using the Pexip Infinity Administrator interface
OpenID Connect support for SSO The participant authentication SSO process now supports the OpenID Connect security protocol (in addition to SAML). About participant authentication
Additional variable supported in VMR Scheduling for Exchange When configuring the use of personal VMRs within the VMR Scheduling for Exchange feature, the email address of the VMR's owner can now be used as a variable within the jinja2 templates. Working with jinja2 templates
End-to-end encrypted call enhancements *

End-to-end encrypted calls between two WebRTC participants now supports the following additional features:

  • A conference can now be escalated beyond the two WebRTC participants (using any call protocol such as WebRTC or SIP for the additional participants, including via dial-out from the conference) but this means the call is no longer a Direct Media call and instead is a standard, transcoded call with media sent via Conferencing Nodes. In conference history, the original participants are shown as being transferred to a new call. If the call de-escalates back to two WebRTC participants then it becomes a Direct Media call again.
  • Support is now provided for chat, Connect app clients that are registered to Pexip Infinity, and joining as audio-only, and presentation and control-only connections.
  • When defining (in a system location) the Client TURN servers that will be provisioned to Connect app WebRTC clients, there is a new Enforce media routing via a client TURN server option that, when selected, forces the WebRTC client to route its media through one of the specified client TURN servers.
  • Media stream details and a Direct Media status flag are available when viewing participant status/history via the Administrator interface, and calls can now be monitored via Live View.

This is still a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Enable Direct Media, and then by enabling Direct Media on each required VMR (in the Advanced options section).

Tech preview features

Configuring Virtual Meeting Rooms (VMRs)

Using TURN servers with Pexip Infinity

Softmute*

Softmute is advanced speech-aware audio gating which helps to minimize noise coming from a participant who has their microphone turned on in a conference, but is not speaking. If non-voice noise is detected, this feature softens the gain from that participant. It does not entirely suppress noise from an audio signal.

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

Tech preview features

Live captions*

Live captions are now supported on VMRs. Participants using the web app can now enable live captions where the live meeting audio is converted to a readable text (live transcription). Live Captions will be offered as an optional feature at an additional cost.

There are also two associated, new theme audio files: conf-live_captions_started_48kHz_mono.wav and conf-live_captions_started_48kHz_mono.wav.

This is a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Enable Live Captions. Please contact your Pexip authorized support representative or your Pexip Solution Architect for guidance on enabling this feature specific to your environment.

Tech preview features

* Technology preview only

Changes in functionality in version 30

Feature Description More information
New top-level Certificates menu in Administrator interface In the Pexip Infinity Administrator interface, all of the certificate management options have been moved to a new top-level Certificates menu, including separate options for viewing and managing root trust and intermediate CA certificates. Managing TLS and trusted CA certificates

Trusted CA certificate management

For CA certificates uploaded by the Administrator, only root CA certificates are now included in Pexip Infinity's list of trusted CA certificates used for verification purposes (previously, uploaded intermediate certificates were also included). This means that when Pexip Infinity needs to verify a far end connection, that far end system must present an entire chain of intermediate certificates in addition to its own leaf certificate. This means that:

  • By default, Pexip Infinity will not use any intermediate CA certificates that have been uploaded to the Management Node for the purposes of verifying certificates for external services.
  • Under normal circumstances this should not require any changes as those far end systems should already be presenting their entire certificate chain.
  • If required, you can override this behavior for specific intermediate certificates by using a new Certificates > Intermediate CA certificates > Advanced > Trusted intermediate option which instructs Pexip Infinity to use that certificate in the TLS verification chain.
Managing trusted CA certificates
Resource allocation changes for Adaptive Composition layout in gateway calls, and Media Playback Service usage

Hardware resource allocation rules have been updated to improve the accuracy of the Conferencing Node media load statistics:

  • Gateway calls that use the Adaptive Composition layout now consume additional Conferencing Node resources (the actual amount depends on many factors, but as a guide, it uses an additional 0.5 HD of resource for each video participant that is on stage). This brings it into line with existing resource usage counting for VMRs that use Adaptive Composition.
  • Connections to a Media Playback Service now use 1.2 times as much hardware resource as a connection to a VMR.

Hardware resource allocation rules

Configuring a Media Playback Service

RTVideo codec, Lync Server 2010 and Lync 2010 clients no longer supported Support for the RTVideo codec has been removed. This disables interoperability with Lync Server 2010 and Lync 2010 clients.  
Setting the default web app

The previous Do not default to the legacy Web App option (Platform > Global settings > Connectivity) has been replaced with a new Default web app option.

  • For new installations from v30 or later, Default web app is set to Always use latest at upgrade which results in Webapp3 being offered to users by default.
  • For older, existing installations, after upgrading to v30 or later:

    • if Do not default to the legacy Web App was previously enabled (the previous default), the new Default web app option will be set to Webapp2.
    • if Do not default to the legacy Web App was previously disabled, the new Default web app option will be set to Webapp1.
About Connect web app versions
Preconfigured URLs for conferences

Preconfigured URLs used to access Connect Webapp2 are supported by the new Connect Webapp3, with the following exceptions:

  • role=guest will result in the participant being offered an alternative join flow that takes them through the setup of their camera, microphone and speakers before they are able to Join the meeting.
  • callType is no longer supported as the new join flow does not require it.
Creating preconfigured links to launch conferences via Connect apps