Issues fixed in v38 and earlier
These are the resolved issues in earlier versions of Pexip Infinity.
For a list of resolved issues in the previous versions of the Pexip web app see the Pexip Web App release notes.
Fixed in version 38.1
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 45993 | Transfer of outbound RTMP participants to another meeting is now specifically prevented. This resolves an issue whereby an attempted transfer of a recording participant could be initiated but would fail, with the result that the participant would be removed from the participant list but would remain in the call. |
Pexip Teams Connector
| Ref # | Resolution |
|---|---|
| 45706 | Fixed an issue which was causing Teams CVI application bot deployment failures. |
| 45533 | Due to recent changes with the CIS STIG images, configuration has been added to increase the default disk size to prevent issues with Teams Connectors in high-security environments. |
Fixed in version 38.0
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 45119 | Fixes an issue where changes to event sink authentication credentials made via the Administrator interface did not take effect. |
| 44858 | Content classification indicators are now displayed to the calling party in gateway calls. |
| 44791 | Resolved an issue where connectivity lost alarms would be erroneously raised. |
| 44553 | Resolved an issue whereby if a participant enabled live captions while they were the only participant in a VMR that had Enable direct media set to Best effort, and a second participant then joined the call from a different location, the second participant's call fluctuated between a transcoded call and a direct media call every 40 seconds. This appeared to the second participant as momentary disconnects. |
| 38908 | RTMP participants connected via a Proxying Edge Node who experience a connection failure are now properly disconnected from the conference. |
| 34884 |
JPEG presentations are now available to participants without presentation capabilities when they are the only participant joining from a new location. |
Pexip web apps
Webapp3
| Ref # | Resolution |
|---|---|
|
44581 GL5333 |
Fixes an issue in breakout rooms that allowed Guests to see control-only Host participants in the participants list of the breakout room they were in. Guests can no longer see control-only Host participants in their breakout room's participant list. |
|
43864 GL5276 |
Fixes an issue that caused an error message to incorrectly appear in white text even though the Webapp3 theme included "overlay": "light". Now, when the theme includes "overlay": "light", the message is in dark text. |
|
42958 GL5202 |
Fixes an issue that caused live captions to obstruct the in-meeting buttons when using the web app in landscape mode on mobile. |
| GL5233 | Fixes an issue that could cause the web app to stop sending video when the close browser confirmation was rejected while background blur was enabled. |
|
GL5386, GL5387, GL5388, GL5389, GL5390, GL5391 |
General fixes and improvements to the user interface for accessibility. |
Fixed in version 37.2
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 45198 | Resolved an issue with VMs deployed in Azure with SSH keys provisioned at boot time that meant they may not have deployed successfully. |
Fixed in version 37.1
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 43854 | Resolved an issue affecting version 37.0 whereby the new May view user groups and May modify user groups administrator permissions needed to be added manually to the user/service account used by the VMR portal for Management Node API access. |
|
44317 44278 |
Resolved an issue when using the Administrator interface to add a new configuration item from an existing configuration page via the button, whereby after entering the details and selecting a blank page appeared and the new item was not added. |
One-Touch Join
| Ref # | Resolution |
|---|---|
| 44757 | Improved resilience to ensure OTJ meeting processing concludes in a timely manner. |
| 44755 | Added Safe Links support for GCC High customers. |
| 44545 | Updated Microsoft Teams SIP Guest Join meeting processing rule to support 13-digit Global Meeting IDs. |
Secure Scheduler for Exchange
| Ref # | Resolution |
|---|---|
| 43651 |
Administrators can now configure authentication for the Outlook add-in. For full instructions, see Add-in authentication for O365. This resolves an issue for users in Microsoft 365 environments whereby the Outlook add-in was unable to authenticate with Pexip Infinity, resulting in a "failed to get user identity token" error when adding joining instructions. This was due to the recent deprecation of Microsoft's getUserIdentityTokenAsync API. (For more information, see https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). |
Fixed in version 37.0
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 43389 | When creating a new snapshot, any existing snapshots older than an hour are now deleted as expected. |
| 43130 | Resolved an issue where multiscreen participant display was incorrectly being enabled on gateway calls between two SIP devices. |
| 40810 | Portrait mode is now available in meetings with 1+0, 1+1 and 2x2 layouts. |
One-Touch Join
| Ref # | Resolution |
|---|---|
| 43430 | Invitations rewritten by Proofpoint's URL Defense that use the format https://urldefense.proofpoint.us are now supported. |
Fixed in version 36.2
One-Touch Join
| Ref # | Resolution |
|---|---|
| 43134 | Resolved an issue caused by a change to the Webex API in RoomOS 11.24.1.5 that meant OTJ was unable to provide details for any meetings to an endpoint if the endpoint was registered to Cisco Webex Cloud and its mailbox had received one or more OTJ meeting invitations for meetings other than Teams, Zoom, Webex or Google. |
Fixed in version 36.1
One-Touch Join
| Ref # | Resolution |
|---|---|
| 41705 | Resolved an issue where 8-character Microsoft Teams SGJ meeting passcodes were not working with OTJ. |
Pexip web apps
Webapp3
| Ref # | Resolution |
|---|---|
| 41886 | Resolved an issue that caused an "Invalid PIN" error when certain combinations of <PIN> and <role> parameters were used in preconfigured links for launching conferences in Webapp3. |
| 41820 | Resolved an issue that caused Webapp3 to become unresponsive in conferences with over 500 participants. |
| 41560 | Resolved an issue where presentation may have be sent to endpoints at a very low frame rate. |
| 39045 | Resolved an issue that sometimes caused users of Chromium-based browsers on Windows devices with an Intel GPU to experience black video or frozen self-view when enabling background effects such as blur or replacement. |
Fixed in version v36.0
Pexip Infinity
| Ref # | Resolution |
|---|---|
| 41093 | Resolved an issue that caused packet captures to fail when the Management Node was configured to use a web proxy. |
| 40517 | Streaming participants now see the "You are the only participant in the conference" splash screen instead of the Welcome screen when no other participants are sending video. |
| 36428 | OIDC JWT 'aud' claims can now be sent to Pexip Infinity in an array. Previously only strings were supported. |
Pexip web apps
Webapp3
| Ref # | Resolution |
|---|---|
|
40796 GL5045 |
Resolved an issue whereby a Webapp3 participant whose video or audio was administratively muted and who then experienced connectivity issues would subsequently start sending video or audio. |
|
39138 GL4902 |
Resolved an issue that affected direct media conferences joined via a webapp3 path with branding applied which included shouldMaskConference, whereby if a third participant joined, none of the participants received media after it was escalated to a transcoded conference. |
|
38808 GL4871 |
When a Webapp3 participant joins a conference with their bandwidth set to `Auto`, change their bandwidth to a different setting, and then change their bandwidth back to `Auto`, the correct bandwidth limitations are now applied. |
|
37887 GL4743 |
There is now a differentiation between administrative muting and self-muting of participants, and these states are now controlled separately. |
Webapp2
There were no significant user-facing fixes in this release.
button, whereby after entering the details and selecting