What's new in version 29?
For full information about this release, see the release notes.
For information about new features and changes to the Infinity Connect web app, see the Infinity Connect web app release notes.
For information about earlier versions of Pexip Infinity, see Features added in previous versions.
|Improved presentation-sharing behavior for Infinity Connect / WebRTC clients||
When an Infinity Connect / WebRTC client sends or receives presentation content (files or screen sharing), it is now sent via the existing call connection used for audio and video media. This means:
Note that the internal PexRTC behavior has changed to support this feature. Any custom PexRTC developments that have not followed our documented API may no longer work correctly.
|Teams Connector enhancements: Azure licensing optimization, "failed sharing" messages for Attendees, and improved "Disable mic" synchronization||
Pexip's Cloud Video Interop (CVI) integration with Microsoft Teams has been enhanced:
Note that version 29 of the Teams Connector contains updates that necessitate an upgrade to your Pexip platform to ensure compatibility with the latest updates to the Microsoft Teams APIs and to the Teams Connector's latest features. We strongly recommend that you upgrade your Pexip deployment — both the Pexip Infinity platform and the Pexip Teams Connector — to version 29 as soon as practicable.
|Adaptive Composition enhancements to "presentation in mix" and conference indicators||
When using the Adaptive Composition layout:
|Receiving the presentation stream as part of the layout mix (Adaptive Composition)|
|Administrative improvements to Live View and Administrator interface start page||
Pexip Infinity administrators can configure two new settings in :
|Management web interface configuration|
|New "System integrity is compromised" administrator alarm||There is a new "System integrity is compromised" alarm which is raised if one or more of the Pexip Infinity system files have been modified by an external party/event.||Viewing alarms|
|Client TURN server provisioning and new TURN server authentication methods||
When configuring TURN servers for use with Pexip Infinity:
|Using TURN servers with Pexip Infinity|
|Google Meet interoperability improvements||Presentation content sent from a VTC endpoint to Google Meet now supports 1080p.|
|Pexip Macro for Meeting Controls||Enhanced endpoint controls for Microsoft Teams meetings on Cisco endpoints which include: changing the conference layout, enabling/disabling the overlay text, viewing the participants list, and spotlighting a participant.||Pexip Macro for Meeting Controls|
|Voice activity detection improvements
When enabled it applies to all call types and all layouts.
This is a technology preview feature and can be enabled via.
|End-to-end encrypted calls between two WebRTC participants
VMRs can now support non-transcoded, encrypted, point-to-point calls between two WebRTC participants.
This is a technology preview feature and can be enabled via Direct Media on each required VMR (in the section)., and then by enabling
|Updated Infinity Connect web app
A technology preview of the next release of the Infinity Connect web app, Webapp3, is available. This release includes a completely new user interface and revised join flows, along with support for upcoming new Pexip Infinity features.
Webapp3 can be accessed by appending /webapp3/ to the IP address or domain name of a Conferencing Node (or reverse proxy) in a v29 Pexip Infinity deployment, for example:
WebRTC clients now send and receive presentation content via the call connection used for audio and video media:
- All media is now sent on a single, bundled call. If you are developing your own apps using our client API directly, this will require code changes.
See Pexip client REST API for more information.
- The PexRTC API remains backwards compatible. Please ensure you always pull the version from the Conferencing Node you are connecting to.
- The internal workings of the PexRTC API have changed considerably. Any custom PexRTC developments that have not followed our documented API may no longer work correctly.
|Changes to formatting of Administrator Log and Support Log results||
In the Administrator Log and Support Log results, a value is enclosed by double quotes and sometimes there is an additional set of double quotes within the value which causes issues if you are manually parsing the logs.
The occurrence of double quotes within double quotes is now escaped using a backslash. For example:
Additionally, there are general updates to the log formatting which affect the casing of certain alphanumeric keys. Keys are now Kebab-Case by default. For example, Src-address is now Src-Address. If you currently parse the logs you may need to do case-insensitive matching on keys.
|"Legacy" Infinity Connect desktop client no longer supported||"Legacy" Infinity Connect desktop client versions, i.e. those released in 2018 or earlier, are no longer supported and are not compatible with Pexip Infinity v29 and later.|
Integrators and third-party developers: the changes in this section may necessitate updates to your applications, and lab testing is strongly encouraged. Please contact your Pexip authorized support representative if you need more information.
|RTVideo codec, Lync Server 2010 and Lync 2010 clients no longer supported||Technical support for the RTVideo codec is deprecated since Pexip Infinity v25. The RTVideo codec will be removed completely in a future release which will then disable interoperability with Lync Server 2010 and Lync 2010 clients.|