Partners Blog Contact Us

Vidyo Neo for WebRTC: About Version 17.1


What's New in this Release

Here's what's new in this release:

  • Far End Camera Control
    • When you're in a video meeting with a VidyoRoom™ system, you may at times wish you could adjust the far-end camera to get a better view. If you’re a doctor, for example, wouldn't it be helpful if you could zoom in to monitor a patient’s IV drip? Or if someone else pops into the conference room, wouldn't it be nice if you could pan the camera to see that other person? With the Far End Camera Control (FECC) feature, you can do just that.


    • FECC works for VidyoRoom systems which have a supported camera that’s capable of panning, tilting, and zooming. In addition, this feature is available for registered users only (not for guest users).
    • You can access all the controls you need to adjust a participant’s camera by clicking the participant's name in the Participants panel and selecting NewUI_FECC_Camera.png from the drop-down.
  • Custom Invocation
    • Third-party partners, developers, and admins: you can now customize the Vidyo Neo client experience and workflow. Vidyo Neo lets you easily choose which features and functionality you can enable and disable for all your users.
    • Here’s a small sampling of the Custom Invocation parameters that you can change:
      • Enabling and disabling the left panel to better manage the real estate of the screen.
      • Bypassing the Welcome, Beauty, and Login pages to provide users with direct access to a conference.
      • Muting all participants’ microphones or cameras upon entry into a call.
    • You can also invoke Vidyo Neo with iFrames. iFrames are the pre-call, in-call, and post-call URLs that allow you to load content from your domain or a third-party system into Vidyo Neo per tenant. For example, you can use iFrames to:
      • Display your own Welcome page.
      • Display content around the main in-call window (such as the names of the participants in the call).
      • Display a thank-you message at the end of each call.


    • For more information about the powerful new Custom Invocation feature, see the Custom Invocation of Vidyo Neo Technical Note.
  • Microsoft® Outlook® and Google Calendar™ Integration 
    • Vidyo Neo for WebRTC can now remind you of every Vidyo meeting you have scheduled on your Microsoft Outlook calendar and your Google Calendar.
    • All you have to do to join the meetings is click the reminder that pops-up five minutes before the meeting is scheduled to start.
    • The reminder pop-ups appear on your Vidyo Neo app whether or not you’re in a call.
    • You can also see the full list of your meetings for the day by clicking  in the Participants and Search panel. The list displays each meeting’s name, organizer, and start time.


  • Theater Mode 
    • When you select Theater Mode as your video layout, the participant who’s currently speaking is displayed in a larger tile (known as the theater screen). If content is shared, the theater screen will split between the shared content and the active speaker.
    • If you want a certain participant to remain in a bigger tile even when others speak, you can hover over that participant’s tile to expand it, and then click to pin it to the larger size.
    • Theater Mode is the default, but you can easily toggle between Gallery View (where all the tiles are the same size) and Theater Mode by clicking  and  on your Vidyo Neo in-call screen.


  • Redesigned Meeting Invitations
    • This release of Vidyo Neo introduces a completely revamped look for meeting invitations. In addition to plain text invitations, you can now send HTML invites via email.
    • By using the variables that we provide in the Admin UI, you can easily add details to your meeting invitations, such as the user’s title, display name, avatar, tenant logo, and local and international dial-in numbers.
    • For more information about how to customize the invite text, refer to the VidyoConferencing Administrator Guide version 17.1.0.

  • Intuitive Recording
    • Want to record your video meeting so you can refer to it later, use it for training, or share it with colleagues who were unable to attend? For organizations that have recording capabilities, Vidyo Neo makes it easy for users to record meetings.
    • All recordings are stored in the same place they are stored today.
    • If you’re the conference moderator, you can simply open the Participants and Search panel in the Vidyo Neo app, and click  to begin recording your meeting. You can also pause and stop the recording from the same panel.
  • Participants’ Camera and Microphone Status
    • Along with the name of everyone in the call, the Participants panel now displays icons indicating whether the participant’s camera and microphone are muted.
    • Registered users can see the camera and mic status of all participants, whereas guest users cannot see the device status of any participants.
  • Microsoft Edge™ Support
    • Microsoft recently announced support for the Edge browser with WebRTC, and Vidyo is proud to be among the first video conferencing companies to support Edge for WebRTC with our Vidyo Neo version 17.1 release.
    • Please note that when using Edge for WebRTC, you cannot share content with your Vidyo Neo app. This is not limitation of Vidyo Neo, but rather a limitation of Microsoft Edge.



To determine which version of the VidyoPortal™ your Vidyo Neo for WebRTC release is compatible with, do one of the following:

The following table defines the compatibility between Vidyo Neo for WebRTC version 17.1.x, OS platforms, and browsers.

Mac® OS X
Windows 7 32-bit and 64-bit Mac OS X 10.9.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.10.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.11.x    


The table above reflects Vidyo’s current test matrix. Other platforms and browsers may also work, although they are not officially supported.


Known Issues

The following table lists the known issues in Vidyo Neo for WebRTC version 17.1:

Vidyo Neo for WebRTC Version 17.1 - Known Issues
Key Summary

Due to a limitation with the Microsoft Edge™ browser, if the TURN configuration is set to OFF, calls cannot successfully be made with Vidyo Neo for WebRTC.

Workaround: Go to Session Manager > Configuration > Advanced and ensure that the TURN configuration is set to ON (which is the default).


Due to a limitation with the Microsoft Edge browser, Vidyo Neo for WebRTC users cannot share content.


If there are no lines available on the VidyoPortal™ when a Vidyo Neo for WebRTC 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 Vidyo Neo for WebRTC user tries to log out during an ongoing call, that user will received an “Application Error” message.

The receiving resolution rate for WebRTC clients does not always match with the resolution configured on the server.


When using Firefox®, if multiple windows of the same application are open, sometimes only one appears in the application share list.

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-643 When using Chrome™ on Windows® and sharing an application into the conference, if the shared application is dragged between monitors, the contents of the desktop behind the original location of the application may be briefly displayed to the conference participants while the application is being moved. This is due to a bug in the Chrome browser.

Due to a bug in Firefox on Windows 8.1, no audio and video may be received or sent when joining a call if the TURN server is enabled but the TURN port is unreachable. 

Workaround: Ensure that the TURN port is reachable or disable TURN via the Admin Web Portal.

On occasion when using an open microphone and speaker with the Firefox browser, echo may be heard by the remote participant. This is a bug in Firefox. 

Workaround: If you experience this problem, use a headset when using Firefox.


When using Chrome on Windows10, if a USB headset is unplugged in the middle of a call, the microphone does not automatically switch to another microphone.


Muting via the button on a USB headset locally mutes the headset, but does not affect the mute state of the Vidyo Neo for WebRTC application.


When using a Firefox browser and plugging-in a USB headset during a call, the self-view may freeze and the browser may crash. This is a due to a bug in Firefox.


Sometimes under impaired network conditions, the video and audio can lose lip-sync. The condition will often self-repair as the network improves.


When using Firefox, if a headset is connected during a call, the name of the headset is not displayed in the browser device selection nor on the Vidyo Neo Devices page.


When older MacBooks® are using multiple monitors with higher resolution and Chrome is configured to use hardware acceleration for video encoding, the GPU may run out of resources and the resulting encoded video may have a low frame rate and poor quality.


If a user previously installed version 1.3 of the VidyoWeb™ for Chrome plug-in, the WebPluginVirtualCamera will appear in the list of cameras; however, selecting this device will result in others not seeing that user’s video.


While in a call with the Firefox browser, if a user clicks the browser’s reload button, they are not warned that they will be dropped from the call.


When sharing an application window on Windows10, after resizing the window, a few pixels of the background are visible around the outside edges of the shared application.


When using Firefox on Ubuntu® 16.04 OS, when you start sharing an application, the application is not brought to the foreground.


The Vidyo Neo for WebRTC page takes about 26 seconds to load completely as well as to refresh.


When a guest joins a call, the Vidyo Neo for WebRTC menu has a “Sign Out” option; however, this button behaves like a “Leave the call” button.


If a user is already using an instance of Chrome that’s in the foreground, and that user then shares content using a different instance of Chrome, the instance with the shared content won’t come into the foreground.


On Firefox, every time a user unmutes their camera, they will be prompted by the browser to share their camera unless they have told the browser to "Always Share" their camera to the Vidyo Neo for WebRTC domain.


When using Chrome on Windows 8.1, the device list may show an invalid speaker and microphone option with the label "Communications".


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



Please sign in to leave a comment.