Partners Blog Contact Us

VidyoConnect for Desktop: About Version 17.3.0 (Includes WebRTC)

Follow

With version 17.3.0, Vidyo introduces VidyoConnect™, our next generation user interface. It has all the features and functionality of Vidyo Neo™, plus a unified experience across desktop, WebRTC, and mobile devices. This article describes the VidyoConnect desktop app, which includes WebRTC. For information about the mobile app, see the About VidyoConnect for Mobile Version 17.3.0 article.

What's New in this Release


Here's what's new in this release:

  • SIP/H.323 Endpoint Dial-Out
    • SIP/H.323 endpoints have always had the ability to dial in to Vidyo meetings. However, with the new SIP/H.323 endpoint dial-out feature available with this release, you can now dial out to these endpoints.

      1.png

    • To initiate a call, simply click the new 2.png button and then enter a SIP dial string or the IP address of an H.323 endpoint.

  • Camera and Microphone Status
    • The VidyoConnect Participants list displays the name of everyone in the call as well icons indicating whether each participant’s camera and microphone are muted.
    • Prior to this release, only registered users could see the camera and mic status, but now guest users can also see the device status of all the participants.

 

What Happens to Vidyo Neo and VidyoDesktop™ When You Upgrade

 

  • If you already have the Vidyo Neo desktop application installed on your system when you upgrade to the VidyoConnect desktop application, the VidyoConnect application will replace Vidyo Neo. Please note that if you’ve manually created a shortcut for the Vidyo Neo application, the Vidyo Neo shortcut icon may still appear on your system and you should delete it.

  • If you have the VidyoDesktop application installed on your system when you upgrade to the VidyoConnect desktop application, the VidyoConnect application won’t replace VidyoDesktop. Instead, you’ll see both applications on your system.

 

Compatibility

Platform and Browser Compatibility for VidyoConnect for Desktop

The following table defines the compatibility between VidyoConnect version 17.3.0, OS platforms, and browsers. 

 

Compatible Windows®
Platforms
Compatible Mac®
OS X Platforms
Other Compatible Platforms Compatible Browsers
Windows 7 32-bit and 64-bit Mac OS X 10.10.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.11.x Chrome OS (two most recent stable channel released versions) Firefox® (two most recent supported official releases)
Windows 10 32-bit and 64-bit Mac OS X 10.12.x    

 

The tables 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.

 

Resolved and Known Issues

This section lists the resolved and known issues in this release of VidyoConnect for Desktop.

 

Resolved Issues

The following table lists the resolved issues in VidyoConnect for Desktop version 17.3.0:

VidyoConnect for Desktop Version 17.3.0 - Resolved Issues
Key Summary
NEP-8432 If a Google Calendar meeting is created with a title or description that contains a string such as <img src="x" onerror="alert(1)">, a JavaScript alert no longer appears when the meeting details are viewed on the VidyoConnect Meetings tab.
NEP-8249 If an admin joins a room that is not their own room and then searches for users who are online, the Invite icon now appears for those users.
NEP-8210 Users who are logged into one portal can click a guest link for a different portal and successfully log in as a guest.
NEP-8191 If a user answers a direct call and then loses and regains their network connection within 30 seconds, they no longer see an erroneous “Missed Call” notification.
NEP-8169 In a call with at least four participants where a participant is audio-only and the VidyoConnect window size is small, the audio-only tile resizes correctly and no longer gets cropped when the layout is switched to Theater Mode.
NEP-8106 If an audio-only participant is the loudest speaker in call when the layout is switched from Theater Mode to Grid Mode and back, the audio-only participant’s tile continues to indicate (by a blue border) that the participant is the loudest speaker.
NEP-8103 The Call button on the Dial Out tab now gets disabled after the user clicks it.
NEP-8095 In a call with at least four participants, when the layout is switched to Theater Mode, the loudest speaker’s tile no longer gets stretched.
NEP-8079 When a remote participant mutes their camera and then speaks, that participant’s audio-only tile now appears on the screen of the other participants in the call.
NEP-8044 Participants can now successfully unmute their microphones when the conference moderator clicks the 3.pngbutton on the Control Meeting page.
NEP-7965 Meeting attendees’ details are no longer included in the logs.
NEP-7963 If a user on a Mac right-clicks the VidyoConnect icon and selects “Quit”, the application successfully quits, thereby allowing the user to be able to upgrade to a newer VidyoConnect version.
NEP-7961 If a user clicks “Send invitation” right after they log in, the room link displayed in the invitation is the correct link.
NEP-7943 The field on the Dial Out tab where a user enters the IP or SIP address now gets cleared out after a call ends.
NEP-7912 On both Windows and Mac, the View Page Source option no longer appears in the pop-up when right-clicking on the VidyoConnect window.
NEP-7804 Logged-in users now see their own camera status correctly on the Participant’s List.
NEP-7789 Users can now properly edit text that they have entered in the IP or SIP address field on the Dial Out tab.
NEP-7786 When the self-view window is maximized, it no longer covers the More (three dots) button.
NEP-7785 The extraneous text that was included in the “Format is not supported” message has been removed.
NEP-7777 When a user uses the Search bar in the Invite pop-up, search results display even if the call is not the first call made after launching the VidyoConnect app.
NEP-7776 The in-call Invite button now appears in the correct location.
NEP-7774 The dialer no longer appears in the left panel for guest users.
NEP-7755 A calendar integration issue that was incorrectly using SDK functions and causing crashes has been resolved.
NEP-7751 DTMF signals are no longer sent while a user is typing a chat message.
NEP-7742 The VidyoConnect app no longer crashes when two users call each other at the same time.
NEP-5779 When a user logs out while a search is activated and then logs back in, the Meetings tab no longer gets disabled.
NEPWEB-1319 When a user creates a meeting with no title in Google Calendar, it does not cause a VidyoConnect error and the meeting now appears in the calendar.
NEPWEB-1203 The specific cases where the incoming call alert tone would continue to play on a user’s headset during a call no longer occur.
NEPWEB-518 When a user presses “Lock this room”, an error message no longer displays and the room successfully locks.

 

Known Issues

The following table lists the known issues in VidyoConnect for Desktop version 17.3.0:

VidyoConnect for Desktop Version 17.3.0 - Known Issues
Key Summary
NEP-8426 If a user calls another user, but then the called user leaves the conference right after clicking the Answer button, the conference remains in progress on the caller’s side, the participant counter shows 0, and the caller can’t leave the conference.
NEP-8228

When using VidyoConnect on Windows, using the PrintWindow function occasionally causes VidyoConnect to hang.

Workaround: Either restart Windows or find the application that is causing PrintWindow to hang and close it.
NEP-8131 Closing the VidyoConnect window doesn’t prevent a user from joining a call. Therefore, if a user clicks to join a room and then closes the VidyoConnect window, that user will actually join the call.
NEP-8107 If all the participants in the call have muted their cameras, the VidyoConnect screen is blank until someone speaks.
NEP-8082

If a logged-in user joins a call with three or more participants in Gallery View, and then views a room or a contact’s details, when the user  double-clicks to go back to the in-call view, they see only two tiles instead of all the tiles that should appear in the Gallery View.

Workaround: Resize the VidyoConnect window to see the rest of the tiles.
NEP-7743 When using web proxy with basic authentication, the VidyoConnect app cannot connect to Google Calendar.
NEP-7250 Some default Windows apps, such as Photos, Calendar, and Groove™, do not appear in the application share list.
NEP-6836 When guest users or web browser users join a call with their cameras and microphones muted, they see audio-only tiles on the VidyoConnect in-call screen.
NEP-6787 If Outlook is the default email client and a user creates a meeting invitation with VidyoConnect, when the Outlook meeting invite opens, the HTML meeting invitation does not appear.
NEP-6706 The “Joining the call” message continues to display for three to four seconds after all the video tiles appear.
NEP-6674 When VidyoConnect is downloaded from the portal and the installer is launched, the message “VidyoConnect is an application downloaded from the Internet. Are you sure you want to open it?” appears twice.
NEP-6431 When a user has more than one display and shares a PowerPoint® slideshow when Presenter View is enabled, both the slideshow and Presenter View are shared.
NEP-6213

When in Theater Mode, if all cameras are muted and then unmuted from the Control Meeting page, only one tile appears.

Workaround: Switch to Gallery View to see all the tiles or disconnect and rejoin the call.
NEP-6082

When a new meeting is created, Outlook crashes one time after each clean installation of VidyoConnect on Windows 10 32-bit with Microsoft Outlook 2016.

NEP-6035

If a user tries to join a room as a guest, but the join fails (from, for example, a network disconnection or a network timeout), occasionally the camera turns off and the user can no longer see their self-view.

Workaround: Click on the guest link to join again.

NEP-6029

If VidyoConnect loses connection with the Microsoft Outlook calendar, the user will not receive a notification that the connection was lost.

NEP-6000

If a user has the room details page open at the same time the admin sets a PIN for the room, when the user clicks the Join button, they will not be asked to enter the PIN nor will they be able to join the room.

Workaround: Re-open the room details page. You will then be asked to enter the PIN.
NEP-5956 If a monitor is shared from a Mac, the other participants in the conference see the shared monitor but they also see the highlighted borders and the Share icon.
NEP-5955

When a user clicks to select their own room, there is a few second delay before the room link and the send invitation links appear.

NEP-5926

If a conference participant selects an application to share and then minimizes the application, that participant’s view will appear as if they are sharing the content, but the remote users will not see the shared content.

NEP-5776 When the portal is configured to not Allow Public Room creation by users, the + button (which enables the creation of new public rooms) appears for a few seconds after the VidyoConnect application starts.
NEP-5622

When using a Mac and sharing content, occasionally the “This video will resume when the remote connection improves” may appear on the tile that is displaying the shared content.

NEP-4921 If a user’s camera is being used by an application other than VidyoConnect, and then the user joins a call with VidyoConnect, that user will not see a notification that their camera is in use by another application.
NEP-4802 Due to an Apple® limitation, when sharing the Mail application on a Mac, the minimized view of VidyoConnect is also shared.
NEP-4801 Due to an OS limitation, while a participant is sharing their screen, the green outline that appears around the shared content does not include the taskbar even though the other conference participants can actually see the taskbar.
NEP-4713 Due to an OS limitation, when a participant views the list of apps available to share, Safari® windows are shown as “Untitled” and Chrome windows are shown as “New Tab”.
NEP-4313 Due to a limitation in Outlook on a Mac, when a meeting is scheduled via VidyoConnect on a Mac, the attendees’ availability information does not appear.
NEP-4221

In low bandwidth calls, lip sync issues might occur.

NEP-4047 Echo can be heard for approximately one second after a headset is disconnected from a MacBook Pro® or a MacBook®.
NEP-3685 The incorrect CDR call completion code displays when the call is ended by the caller.
NEP-3684 Incorrect CDR entries display when an incoming call times out.
NEP-3467 If the network is slow and a user is the first participant to join a call, the user sees a “[username] has joined the conference” message instead of the “You’re the only person in the call” message.
NEP-3187 If a user has more than one display and shares the main display, the video window does not move to the non-shared display.
NEP-2129 If a Tenant admin changes the name of a room, VidyoConnect users do not see the new room name in the UI until they log out and log back in.
NEP-1077 The order of items on the share selection list only updates when the VidyoConnect app is restarted.
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-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.

 

 

 

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.