This article describes the new features, functionality, and resolved issues for each of the VidyoConnect™ for WebRTC releases since 2019. Additionally, this article includes information on upgrading from VidyoDesktop™, platform and browser compatibility, and known issues.
- 2021 Releases
- 2020 Releases
- 2019 Releases
- Upgrading from VidyoDesktop™
- Compatibility (Native)
- Compatibility (Transcoded)
- Known Issues (Native)
- Known Issues (Transcoded)
2021 Releases
VidyoConnect for Native WebRTC: About Version 20.4.2
What's New?
- New Custom Invocation Parameters
- In this release, we've added these new custom invocation parameters:
- muteCameraOnJoin
- muteMicOnJoin
- camMuteCntrl
- micMuteCntrl
- share
- leftPanel
- chat
- These parameters allow third-party partners, developers, and admins to customize VidyoConnect for WebRTC by controlling whether the camera and microphone are muted upon entering a conference and whether certain buttons, panels, or features display in the app. These customizations are especially useful when coordinating webinars.
- For more information, refer to the "Using Custom Invocation" section of the Using VidyoConnect: Admin-Level Functions article.
- In this release, we've added these new custom invocation parameters:
Resolved Issues
The following table lists the resolved issues in VidyoConnect for WebRTC version 20.4.2:
| VidyoConnect for WebRTC Version 20.4.2 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEP-15122 |
When a user on an iOS device joins a VidyoConnect for WebRTC call with Safari and rotates the device to change orientation, the self-view tile no longer turns black. |
| NEP-15120 |
When a Chrome user on Android device rotates the device, some VidyoConnect UI elements (such as the control menu) that previously disappeared now remain on the screen as expected. |
| NEP-15042 |
A compatibility issue has been fixed for the upcoming release of Chrome 89 where a user would drop from the call right after joining if the remote participant had their camera enabled. |
| NEP-15004 |
When a call participant using an Android device unmutes or switches their camera, their self-view tile no longer freezes or turns black. |
| NEP-14940 |
When a user joins a call and the Welcome page parameter is set to "false", the Instructions for Authorizing Devices now displays as expected so the user can give permission to use the microphone. |
Known Issues
To view the known issues for this release, as well as for previous releases, please click here.
2021 Releases
VidyoConnect for Native WebRTC: About LA Version 20.4.1
What's New?
- Resolved Chrome Issue
- This release fixes a known issue with Chrome on Android 11 that caused the UI to freeze when closing WebRTC streams.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 20.4.1:
| VidyoConnect for WebRTC Version 20.4.1 - Resolved Issue | |
|---|---|
| Key | Summary |
| NEP-14994 |
An issue that caused the UI to freeze when using Chrome on Android 11 has been fixed. |
Known Issues
To view the known issues for this release, as well as for previous releases, please click here.
VidyoConnect for Native WebRTC: About LA Version 20.4.0
What's New?
- BeautyScreen and WelcomePage Custom Invocation Parameters Available for Native WebRTC
- The beautyScreen and welcomePage Custom Invocation parameters, which were previously available only for VidyoConnect desktop users, are now available for Native WebRTC users.
- These parameters allow third-party partners, developers, and admins to customize VidyoConnect for WebRTC so users can bypass the Welcome and Beauty pages and go directly to their video conferences.
- For more information, refer to the "Using Custom Invocation" section of the Using VidyoConnect: Admin-Level Functions article.
- Easily Join a Single VidyoConnect Call Instead of Multiple Sessions
- Sometimes participants may accidentally open several browser window tabs when joining the same call. Once a new browser tab is opened, the session in the previously opened tab is terminated.
- To let you know which browser tab to close, this helpful message will now display: “Please close this tab. A new VidyoConnect session was started in another tab.”
Resolved Issues
There are no resolved issues for this release.
Known Issues
The one new issue, NEP-14940, was subsequently resolved in Version 20.4.2.
2020 Releases
VidyoConnect for Native WebRTC: About LA Version 20.2.3
What's New?
- Resolved Issue
- An issue was corrected where sometimes a participant using a Safari or Chrome browser could not be heard when joining a call with three or more participants with enabled microphones.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 20.2.3:
| VidyoConnect for WebRTC Version 20.2.3 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEP-14622 |
An issue was corrected where sometimes a participant using a Safari or Chrome browser could not be heard when joining a call with three or more participants with enabled microphones. |
Known Issues
There are no new known issues for this release; however, if you want to review previously documented Known Issues for Native WebRTC, please click here.
VidyoConnect for Native WebRTC: About LA Version 20.2.2
What's New?
- New Instructions for Authorizing Devices
- This release includes new onscreen instructions in a pop-up window with a link to a video in the VidyoConnect app to help users authorize the use of their camera and microphone in their browsers, which is especially useful in cases where users previously denied authorization.
- Below are the different pop-ups that may display based on your device, platform, and browser. When the pop-up displays in your device, click the “How to give access to device” link to see a video on how to authorize the devices.
iOS Device in Safari Browser
Android Device in a Chrome Browser
MacOS in a Safari Browser
Windows & MacOS in a Chrome Browser
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 20.2.2:
| VidyoConnect for WebRTC Version 20.2.2 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEP-14654 |
An issue was fixed where sometimes users get dropped from calls when using Chrome version 86. |
| NEP-14572 |
The lists of supported browsers for VidyoConnect for WebRTC are available here for Native compatibility and here for Transcoded compatibility. |
| NEP-14571 and NEP-14570 |
Onscreen instructions and videos were added to the VidyoConnect app to help users authorize usage of their devices in their browsers, especially in cases where they previously denied authorization. The instructions include a message indicating that users are not allowed to join a call unless they authorize the use of their camera and microphone. |
Known Issues
There are no new known issues for this release; however, if you want to review previously documented Known Issues for Native WebRTC, please click here.
VidyoConnect for Native WebRTC: About LA Version 20.2.1
What's New?
- Enghouse Vidyo corrected an issue so VidyoConnect ™ for Native WebRTC (desktop and mobile) users can easily join calls when using the upcoming release of Google Chrome™ version 85. Previously, some users experienced issues on the Goolge Chrome version 85 beta version when connecting to calls and may have received timeout errors.
- This issue specifically impacted customers using the VidyoConnect Health4 Meetings platform.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 20.2.1:
| VidyoConnect for WebRTC Version 20.2.1 - Resolved Issues | |
|---|---|
| Key | Summary |
| IOWEBRTC-1297 |
Enghouse Vidyo fixed an issue affecting VidyoConnect for Native WebRTC users who had issues joining calls using Google Chrome version 85. |
| IOWEBRTC-1337 |
An issue was resolved affecting VidyoConnect for Native WebRTC users who had issues getting disconnected from calls when using Google Chrome version 85. |
Known Issues
There are no new known issues for this release; however, if you want to review previously documented Known Issues for Native WebRTC, please click here.
VidyoConnect for Native WebRTC: About LA Version 20.2.0
What's New?
- Support for VidyoConnect Native WebRTC
- In this release, guest customers can easily and quickly join calls using a browser and no longer need to install any application or plugin. Simply, click on a conference link and the browser will open.
- Click Join via the Browser and the VidyoConnect app opens. (Enter your name and mute your speaker, microphone, and camera, if needed).
Desktop Experience
Mobile Experience
- In this release, guest customers can easily and quickly join calls using a browser and no longer need to install any application or plugin. Simply, click on a conference link and the browser will open.
- Supported Browsers
- The VidyoConnect for Native WebRTC application runs on the following supported WebRTC browsers:
- Google Chrome™ version 83 and later on Windows, Mac OS and Android™
- Safari®version 13.1.1 and later on iOS/iPad OS and Mac OS
- Firefox is not supported in this version.
- The VidyoConnect for Native WebRTC application runs on the following supported WebRTC browsers:
- Support for Epic Context-Aware Linking (CAL) Workflows
- Epic customers can connect using CAL capabilities from Epic combined with a turnkey integration using VidyoConnect for Native WebRTC (desktop and mobile).
- If you are an Epic deep embedded customer and you want to migrate to CAL Integration with VidyoConnect for Native WebRTC, please read about the benefits to moving to Epic CAL in the Migrating from Epic Deep Embedded Integration to CAL Integration with VidyoConnect for WebRTC article.
- Features
- The Using VidyoConnect: About Each Feature article provides detailed information about how to use the pre-call and in-call features of the VidyoConnect™ application—whether you're using the application on your desktop, with WebRTC, or on your mobile device. Refer to the below native WebRTC pre-call and in-call feature sections in this article.
- Pre-Call Features
- Configuring the Audio/Video Settings
- Viewing and accepting the Terms and Conditions & Privacy Policy
- Using the Calendar Integration Feature
- In-Call Features
- Using the Participant's List to view call participants
- Using the in-call chat feature to send and receive chats
- Using the Content/Screen Share Feature
- Using the Whiteboard Feature (View only)
Important Considerations:
- Toggle layout is not available.
- Mobile participants can view shared or whiteboard content; however, cannot share content or annotate on the whiteboard during a call.
- Although participants cannot use the Moderation and Recording features, a notification will display as a red circle in the top right of the application if someone is recording the meeting.
- Pre-Call Features
- The Using VidyoConnect: About Each Feature article provides detailed information about how to use the pre-call and in-call features of the VidyoConnect™ application—whether you're using the application on your desktop, with WebRTC, or on your mobile device. Refer to the below native WebRTC pre-call and in-call feature sections in this article.
- Troubleshooting
- If you are having issues, desktop and mobile customers can download logs by going to Settings>Help>Downloads.
- To troubleshoot media issues, create a WebRTC internals dump file on chrome://webrtc-internals/.
- A simple way to detect device and connectivity issues is to use this test environment: https://test.webrtc.org
Resolved Issues
There are no resolved issues in the VidyoConnect for Native WebRTC version 20.2.0 release.
Known Issues
Please refer to the Known Issues for Native WebRTC here.
VidyoConnect for WebRTC: About LA Version 20.1.3 (Transcoded)
What's New in This Release
- Enghouse Vidyo corrected an issue so users on macOS Big Sur can now join calls when using the Google Chrome™ browser.
- Because of a browser restriction that prevents sites from playing audio without user permission, the VidyoConnect user is directed to the Welcome page and must give permission to use the microphone even if the Custom Invocation WelcomePage parameter is set to "False".
Resolved Issues
The following table lists the resolved issues in the Limited Availability release of VidyoConnect for WebRTC version 20.1.3:
| VidyoConnect for WebRTC Version 20.1.3 (LA) - Resolved Issues | |
|---|---|
| Key | Summary |
| NEP-14790 |
Users on macOS Big Sur can now join calls using the Chrome browser. |
| NEP-14789 |
Prior to this release, if the user didn’t have a microphone, didn’t give permission to use the microphone, or joined the call with a disabled microphone and the WelcomePage parameter was set to "False" using Custom Invocation, the user would not see the Welcome page; however, they would be unable to hear any audio in the call because of a browser restriction that prevents sites from playing audio without user interaction. With this release, the user is directed to the Welcome page regardless of the WelcomePage parameter setting; in this way, they must interact with the page and, thereby, overcome the browser restriction. |
There are no new known issues for this release.
VidyoConnect for WebRTC: About Version 20.1.2 (Transcoded)
What's New in This Release
- Enghouse Vidyo corrected an issue so users can easily join calls when using the upcoming release of Google Chrome™ version 85. Previously, some users experienced issues on the Goolge Chrome version 85 beta version when connecting to calls and may have received 404 timeout errors.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 20.1.2:
| VidyoConnect for WebRTC Version 20.1.2 - Resolved Issues | |
|---|---|
| Key | Summary |
| IOWEBRTCGW-450 |
Enghouse Vidyo fixed an issue affecting VidyoConnect for WebRTC (transcoded) users who joined calls using Google Chrome version 85. |
There are no new known issues for this release.
VidyoConnect for WebRTC: About Version 18.2.9 (Transcoded)
What's New in This Release
- Enghouse Vidyo corrected an issue so users can easily join calls when using the upcoming release of Google Chrome™ version 85. Previously, some users experienced issues on the Goolge Chrome version 85 beta version when connecting to calls and may have received 404 timeout errors.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 18.2.9:
| VidyoConnect for WebRTC Version 18.2.9 - Resolved Issues | |
|---|---|
| Key | Summary |
| IOWEBRTCGW-451 |
Enghouse Vidyo fixed an issue affecting VidyoConnect for WebRTC (transcoded) users who joined calls using Google Chrome version 85. |
There are no new known issues for this release.
VidyoConnect for WebRTC: About Version 18.2.8
What's New in This Release
- Enghouse Vidyo corrected an issue so the iFrames for pre-call, in-call, and call post URLs now work correctly for enterprise organizations to load content from their domains or a third-party system into VidyoConnect per tenant.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 18.2.8:
| VidyoConnect for WebRTC Version 18.2.8 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEP-13290 |
Enghouse Vidyo fixed an issue affecting VidyoConnect for WebRTC users who joined calls using Google Chrome 78 and later. When users undocked the received remote content share, the content did not show in the new window. Now users can undock the content share and view it properly. |
There are no new known issues for this release.
2019 Releases
VidyoConnect for WebRTC: About Version 18.2.7
What's New in This Release
- Enghouse Vidyo fixed an issue where if you popped out the screen share window it would sometimes display as a black screen when using WebRTC versions prior to 18.2.7 with Google Chrome versions 71 and later.
- Another issue was fixed so customers can connect to calls when using VidyoConnect WebRTC with Firefox® version 68.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 18.2.7:
| VidyoConnect for WebRTC Version 18.2.7 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEPWEB-1497 |
An issue was resolved so customers using VidyoConnect WebRTC can now connect to calls when using Firefox® version 68. |
| NEP-12620 |
Enghouse Vidyo fixed an issue where if you popped out the screen share window it would sometimes display as a black screen when using WebRTC versions prior to 18.2.7 with Google Chrome™ versions 71 and later. |
There are no new known issues for this release.
VidyoConnect for WebRTC: About Version 18.2.6
What's New in This Release
- Vidyo fixed an issue so now Google Chrome™ Beta Version 74 renders audio and video with VidyoConnect for WebRTC. Previously, during preliminary testing with Chrome beta version 74, Vidyo discovered that the audio and visual was not working when multiple participants joined a call using VidyoConnect™ for WebRTC.
Resolved Issues
The following table lists the resolved issue in VidyoConnect for WebRTC version 18.2.6:
| VidyoConnect for WebRTC Version 18.2.7 - Resolved Issues | |
|---|---|
| Key | Summary |
| NEPWEB-1494 |
Vidyo fixed an issue so now Google Chrome™ Beta Version 74 renders audio and video with VidyoConnect for WebRTC. Previously, during preliminary testing with Chrome beta version 74, Vidyo discovered that the audio and visual was not working when multiple participants joined a call using VidyoConnect™ for WebRTC. |
There are no new known issues for this release.
Upgrading from VidyoDesktop™
If you’re planning to upgrade to VidyoConnect from VidyoDesktop, we'd like to clarify a few important points that you should pass along to your users:
- If you've just switched from VidyoDesktop and VidyoMobile™ to VidyoConnect, your users will now be redirected to the new VidyoConnect for Mobile app when they join a call from a mobile device. They will first be prompted to download the app from the Google Play™ Store or the Apple® App Store. Then, once the app is installed, they'll be routed to their call via the VidyoConnect for Mobile app.
- If you’re still using VidyoDesktop and VidyoMobile, we encourage you to upgrade to VidyoConnect to access all the latest features. Please contact us to initiate the upgrade to VidyoConnect, and click here to learn more about what to expect.
We invite you to visit our VidyoConnect page to find out more about the VidyoConnect applications, the benefits of moving to our cloud services, and the plans we offer.
Compatibility (Native)
- The VidyoConnect for Native WebRTC application runs on the following supported WebRTC browsers:
- Google Chrome™ version 83 and later on Windows, Mac OS and Android™
- Safari®version 13.1.1 and later on iOS/iPad OS and Mac OS
Supported Platforms
| Platform | OS Version | Browsers |
|---|---|---|
| Windows® | 10 and later | Google Chrome™ 83 and later |
| macOS® | 10.14 and later |
Google Chrome 83 and later Safari® 13.1.1 and later |
| iOS/iPad OS | 13.6 and later | Safari |
| Android™ | 8 and later | Chrome 85 and later |
Mozilla Firefox® and Microsoft Edge support for desktop is in Beta and is not yet officially supported.
Compatibility (Transcoded)
Platform and Browser Compatibility for VidyoConnect for WebRTC
The following table defines the compatibility between VidyoConnect and OS platforms.
| Compatible Windows® Platforms |
Compatible Mac® OS X Platforms |
Other Compatible Platforms | Compatible Browsers |
|---|---|---|---|
| Windows 7 32-bit and 64-bit | Mac OS X 10.14.x and Mac OS X 10.12.x | Linux® (Ubuntu 14.04 and 16.04 LTS) | Chrome™ (two most recent stable channel released versions) |
| Windows 8.1 32-bit and 64-bit | Mac OS X 10.13.x | Chrome OS (two most recent stable channel released versions) | Firefox® (two most recent supported official releases) |
| Windows 10 32-bit and 64-bit |
The table above reflect Vidyo’s current test matrix. Other platforms and browsers may also work, although they are not officially supported.
Portal Compatibility for On-Premises VidyoConnect Customers
If you are an on-premises customer, refer to the Vidyo Compatibility Matrix article to determine which version of the portal your VidyoConnect release is compatible with.
Known Issues (Native)
The following table lists the known issues for VidyoConnect for WebRTC (Native):
| VidyoConnect for WebRTC (Native) - Known Issues | |
|---|---|
| Key | Summary |
| NEP-15009 |
When using Android 11 on a Pixel 2 XL, the VidyoConnect page may freeze when another participant in the call mutes and unmutes their camera a few times. If this occurs, send the VidyoConnect app to the background and then back to the foreground. |
| NEP-15004 | The self-view tile may freeze or turn black when a call participant using an Android device unmutes or switches their camera. |
| NEP-14940 | When a participant joins a call, and the Welcome page parameter is set to "false"; the Instructions for Authorizing Devices should display; however, the participant incorrectly joins the call with the microphone muted. |
| NEP-14622 | On occasion. when there are three or more participants with enabled microphones during a call, the newly joined participant cannot be heard. The workaround is to drop from the call and then rejoin. |
| NEP-14424 | Sometimes when using Safari version 13.1.x no audio is sent or heard. Workaround: Audio issue is resolved when using Safari Technology Preview 111 or Google Chrome version 83 or later. |
| NEP-14369 | When joining a call with several participants (desktop and Native WebRTC) the video tiles' aspect ratio is not maintained when the video resolution changes. |
| NEP-14331 | When using iOS version 13.5.1 with Safari sometimes after several minutes in a call, the audio becomes choppy and/or a clicking sound is heard. |
| NEP-14298 |
When using VidyoConnect for WebRTC (native), Safari does not allow the user to select the microphone as it uses the system default microphone of the macOS. If the default microphone is changed in the macOS settings, the VidyoConnect for WebRTC application should immediately start using the new system default microphone; however, this does not work in the VidyoConnect for WebRTC version 20.2.0. |
| NEP-14270 | When accepting an incoming cellular call while on a VidyoConnect Native WebRTC call with a remote participant, the camera is not displayed as muted for the remote participant. |
| NEP-14269 | After ending a cellular call that was answered while on a VidyoConnect Native WebRTC call, the audio is not received by the remote participant. |
| NEP-14159 | Sometimes when using iOS version 13.0 with Safari no audio is sent or heard. Workaround: Audio issue is resolved when using iOS version 13.5.5 and later. |
| NEP-14156 |
If you use a Safari or a Chrome browser and a narrow content share window displays, the window will disappear if you decrease the size of your browser window. |
| NEP-14155 | Repetitive Safari microphone permission pop-ups are displayed after the user has previously denied this permission. |
| NEP-14072 | You cannot switch microphone when using Safari on macOS as the audio is not sent after unplugging the default microphone. |
| NEP-14069 | Participants who enter and send more than a certain number of characters in the Chat will get disconnected from the call. |
| NEP-14054 |
After ending a VidyoConnect for Native WebRTC call, the browser does not release the microphone and the notification "Microphone in use" will display incorrectly. Only the notification displays and the participant's microphone no longer transmits audio to the call since the call was ended. |
Known Issues (Transcoded)
The following table lists the known issues for VidyoConnect for WebRTC (Transcoded):
| VidyoConnect for WebRTC (Transcoded) - Known Issues | |
|---|---|
| Key | Summary |
| NEP-11009 | A black tile occurs for a remote participant when switching from one camera to another camera and back again. |
| NEPWEB-1275 | When a Sessheiser headset is connected, the Firefox browser transmits audio on both external mics (e.g., the built-in mic on the camera and the mic on the Sessheiser headset) during a call. |
| NEPWEB-1253 | When using the Firefox browser, TURN relay calls may fail and the “ICE connection failed” error message may appear. |
| NEPWEB-1183 | When a user clicks the … button near a name in the VidyoConnect left panel, the stethoscope indicator is missing. |
| NEPWEB-1118 | Due to a limitation with the Firefox browser, if a user opens the application share list and then changes the name of an app, the app's name is not updated on the application share list. |
| NEPWEB-1116 | Due to a limitation with the Firefox browser, the application share list does not update in real time; therefore, if a user opens a new app, they will not see it in the VidyoConnect share list unless they relaunch Firefox. |
| NEPWEB-1087 | When using Firefox, the video displayed in the participant’s tile may not be from the camera selected on the Device Settings screen. |
| NEPWEB-1083 | Due to a limitation with the Firefox browser, even if multiple audio output devices are connected, only the system default device appears as the speaker and ringing device on the VidyoConnect Device Settings screen. |
| NEPWEB-932 | If there are no lines available on the portal when a VidyoConnect guest user tries to join a call, the guest user will receive the erroneous message “Unable to join the conference. Please contact your administrator” instead of the correct message “Unfortunately, all lines are in use. Please contact your administrator or try again”. |
| NEPWEB-930 | If a logged-in VidyoConnect user tries to log out during an ongoing call, that user will receive an “Application Error” message. |
| NEPWEB-916 | If a Firefox user joins a call, shares content, and then edits the shared content, the other participants in the call will not see the edits. |
| NEPWEB-914 | If a Firefox user joins a call as a guest and then gets disconnected, after refreshing the browser, that user will receive a message saying the server is full and asking them to “Try again”. If the user then clicks the “Try again” button, the Firefox browser icon will keep spinning and never load the page. |
| NEPWEB-824 | When using Firefox, headsets do not appear in the list of available ringing devices on the Devices page. |
| NEPWEB-369 | When a user who is using Firefox on Ubuntu 16.04 OS starts sharing an application, the application is not brought to the foreground. |
| NEPWEB-198 | When using Chrome on Windows 8.1, the device list may show an invalid speaker and microphone option with the label "Communications". |
Content Sharing Known Limitation
The following table lists the lists the known OS limitation when sharing content with VidyoConnect:
| Content Sharing Known Limitation | |
|---|---|
| OS | Limitation |
| Windows 10 and 8.1 |
Universal Window Platform (UWP) applications that are displayed in a window on the desktop cannot be shared. Applications that render all or part of their window’s content using Microsoft DirectComposition, such as Chrome 50 and Firefox 46, cannot be shared. Instead, the user must share the entire display. |
Comments
1 comment
This article is now condensed into the VidyoConnect for WebRTC Releases article and will be archived in one week.
Please sign in to leave a comment.