What's new in version 38?

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

• Watermarked Teams meetings are now supported (no action is required in Pexip Infinity to enable support).

Ensuring your CVI app ID is assigned

You must ensure that your CVI app ID is specified in your Cloud Video Interop connection information. This is normally done as part of the initial deployment of your Teams Connector when defining the CVI app behavior and granting interoperability.

If your CVI app ID is not assigned then your CVI calls will fail with Teams Connector version 38 or later. Your CVI app ID is also required to receive PowerPoint Live content.

Full details of how to check and (if necessary) assign your CVI app ID via the Get-CsVideoInteropServiceProvider and Set-CsVideoInteropServiceProvider commands are contained in the Teams Connector upgrade instructions.

We recommend checking that your CVI app ID is assigned in advance of starting the upgrade process.

Note that version 38 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 38 as soon as practicable.

Local and external policy has the following enhancements:

• The call information now contains a previous_service_name field which can be used to identify the name of the previous service prior to a call transfer.

• Participant policy includes new options:

  • rx_presentation_policy: controls whether the participant can receive presentation content.
  • can_receive_personal_mix: controls whether the participant can receive a personal layout.
• The response for Infinity Gateway calls can now specify via a new transcoding_enabled field if the video and presentation streams of SIP-to-SIP calls are transcoded or not.
• The response for VMR and Virtual Auditorium service types can now specify denoise_enabled and softmute_enabled settings (when the denoise and softmute technology preview features are enabled).

Call information variables

Participant configuration responses

Infinity Gateway service type response fields

Virtual Meeting Room / Virtual Auditorium service types response fields

Administrators configuring Secure Scheduler for Exchange Integrations can now use a jinja template to generate a description of the aliases used for single-use VMRs. These alias descriptions may be displayed to users of registered Pexip clients and apps who are performing a directory search.

By default the organizer's email address is included in the description, but this can be changed via the template.

Registering devices via an SSO Identity Provider has the following improvements:

• Device alias validation against Identity Provider attributes is now case-insensitive, allowing for a smoother experience when users who are registering their device via SSO enter an alias with a different case to that configured in the Identity Provider.
• The LDAP synchronization template, used for bulk creation and updating of device aliases, now includes fields for Enable registration using IdP SSO and Identity Provider group so you no longer need to manually set these fields after a bulk import/update.

Authenticating registrations using Identity Providers

LDAP synchronization template

There are two new administrator permissions which provide edit and view access to OTJ Endpoints only:

• May modify OTJ Endpoints
• May view OTJ Endpoints.

The Google Meet SIP Guest Join meeting processing rule now includes a Pexip Service Customer ID field, allowing you to track these calls within Pexip Control Center.

After upgrade, you must update this rule to include your customer ID to ensure that these calls will continue to work in the future.

This release contains the following administrative improvements:

• Warning-level alarms on the Management Node can now be acknowledged by the administrator and thus hidden from Live View.
• When logging out of the Administrator interface you now have the option to log out of all active sessions.

Viewing alarms

Using the Pexip Infinity Administrator interface

Meeting Manager is a new participant type designed for someone who needs to join a meeting via the web app as a control participant only and does not need to present, view presentation, or send and receive audio and video. The Meeting Manager participates in the meeting but only to manage the participants and conference controls such as mute participants, lower raised hands, and admit participants waiting in the lobby.

Managing meetings on the web app

Creating preconfigured links to launch conferences via Pexip apps

Advanced Pexip web app branding and customization

The web app interface now supports languages that are written from right to left such as Arabic and Hebrew. Although Pexip provides native support for Arabic and Hebrew, not all RTL language translations are included by default. The interface will automatically adapt, however, if you supply a custom language file with an RTL locale code such as fa (Farsi).

If you use the callType parameter in preconfigured links to launch conferences via Pexip apps, note the following changes:

• callType=none now determines that the participant will join as a control-only participant. They will have participant and conference controls but will not have presentation, audio, or video.
• callType=presentation-only determines that the participant will join as a presentation and control-only participant. They will have conference controls and can view or share presentation, but they will not send or receive audio and video. Note: This is exactly how callType=none previously worked.

All callType values in the defaultUserConfig, used for manually customizing the user-configurable settings for sending and receiving audio, video, and presentation, have been updated. The value descriptions such as "audioonly" have not changed from the descriptions in Pexip Infinity 37 and earlier.

If you have applied custom branding that includes callType values from an earlier Pexip Infinity version, these values will no longer work upon upgrading. You must manually update the defaultUserConfig section of the application manifest file with the following values:

• 0: ("none") to join as a control-only participant, i.e. the user will not send or receive any audio, video, or presentation.
• 96: ("presentation-only") to join as a presentation and control-only participant, i.e. the user will not send or receive any audio or video.
• 102: ("audioonly") to join as an audio-only participant, i.e. send and receive audio but not send or receive video.
• 100: ("audiorecvonly") to receive but not send audio, and not send or receive video.
• 98: ("audiosendonly") to send but not receive audio, and not send or receive video.
• 120: ("videoonly") to send and receive video, but not send or receive audio.
• 112: ("videorecvonly") to receive but not send video, and not send or receive audio.
• 104: ("videosendonly") to send but not receive video, and not send or receive audio.
• 106: ("audiovideosendonly") to send audio and video, but not receive audio or video.
• 116: ("audiovideorecvonly") to receive audio and video, but not send audio or video.
• 126: ("video") to join as a full (send and receive) audio and video participant.

If this value is not set, or is set to a value other than one listed above, the default 126 (full send and receive video and audio) is used.

Advanced Pexip web app branding and customization

Managing administrator access via LDAP

Configuring an LDAP data source

In a future release we will remove the OAuth (delegate access with a service account) Authentication method option when configuring a Secure Scheduler for Exchange Integration.

This is because from February 2025 Microsoft disabled Application Impersonation role assignments to service accounts (for more information, see Microsoft's announcement). Therefore:

• One-Touch Join customers using O365 with an OTJ Exchange Integration must migrate to using Graph API instead. For full instructions, see Migrating from EWS API to Graph API for One-Touch Join.
• Secure Scheduler for Exchange customers still using O365 with a service account to access equipment resources and mailboxes must migrate to using app permissions instead. For full instructions, see Configuring Office 365 for scheduling using app permissions.

Certificate-based authentication (CBA) is now the default method to authenticate the Teams Connector CVI application towards MS Graph. You can still use the previous password-based authentication method, but we plan to deprecate it in a future release, thus we recommend using CBA for new installations, or migrating to CBA as soon as practicable when upgrading existing deployments.