VidyoConnect™ is Vidyo's enterprise meeting solution for team collaboration. It offers a unified experience across desktop, WebRTC, and mobile devices. This article describes version 18.2.6 of the VidyoConnect for WebRTC.
What's New in This Release
- Vidyo fixed an issue so that far end camera participants (camera owners and controllers) using Chrome 72 can now see and hear each other during video conferences.
Upgrading from VidyoDesktop™ or Vidyo Neo™
If you’re planning to upgrade to VidyoConnect from VidyoDesktop or Vidyo Neo, we'd like to clarify a few important points that you should pass along to your users:
- If you've just switched from Vidyo Neo or 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.
Platform and Browser Compatibility for VidyoConnect for WebRTC
The following table defines the compatibility between VidyoConnect version 18.2.6 and OS platforms.
OS X Platforms
|Other Compatible Platforms||Compatible Browsers|
|Windows 7 32-bit and 64-bit||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
Resolved and Known Issues
This section lists the resolved and known issues in this release of VidyoConnect for WebRTC.
The following table lists the resolved issues in VidyoConnect for WebRTC version 18.2.6:
|VidyoConnect for WebRTC Version 18.2.6 - Resolved Issues|
||Vidyo fixed an issue so that far end camera participants (camera owners and controllers) using Chrome 72 can now see and hear each other during video conferences.|
The following table lists the known issues in VidyoConnect for WebRTC version 18.2.6:
|VidyoConnect for WebRTC Version 18.2.6 - Known Issues|
|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|
|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.