Version 18.2.5

What's new in this release?

  • feature
  • Vidyo fixed a back end issue that caused WebRTC calls to fail in FireFox versions 61, 62, and 63.
  • The device mute and unmute works on Chrome version 69.
  • When using Chrome 69, you can now successfully switch your camera or microphone from mute to unmute during a VidyoConnect call and successfully see the video and hear the audio of all participants.

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.

Resolved issues

The following table lists the issues we have resolved in VidyoConnect for WebRTC version 18.2.5.

VidyoConnect for WebRTC version 18.2.5 - resolved issues

Key

Summary

NEPWEB-1447 and NEPWEB-1443

Vidyo fixed a back end issue that caused WebRTC calls to fail in FireFox versions 61, 62, and 63. When joining a VidyoConnect for WebRTC call with the audio and video initially disabled, the Session Description Protocol (SDP) details will now display in FireFox 61, 62, and 63.

NEWEB-1455

Fixed an issue in Chrome 69 where user audio and video occasionally did not work as expected when switching camera or microphone from mute to unmute.

Known issues

The following table lists the known issues in VidyoConnect for WebRTC version 18.2.5.

VidyoConnect for WebRTC version 18.2.5 - 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 Sennheiser 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".

Windows 10 and 8.1 (known limitation)

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.

Known issues

There are no new known issues for this release.