Version 3.3.19
What's new in this release?
- Write protection mode feature
- We’ve implemented a new write protection mode feature that adds full File Based Write Filtering. This feature is recommended for deployments where the probability of ungraceful shutdowns is high and where, up until this point, the systems were unable to recover.
- Admins can easily enable write protection mode from the Admin UI.
- Enable and disable super sensitive mode for Phoenix audio devices
- If you want the audio to be processed through your Phoenix audio device, you can now disable Phoenix Super Sensitive mode via the Admin UI. If, on the other hand, you want to hear the audio in its native state, you can enable this mode.
- This feature is useful in cases where you want to hear all the noise coming from a certain location. For example, a nurse at a nurse’s station in a hospital might want to enable this mode in order to hear every sound in a patient’s room.
- View the firmware version of connected devices
- For your convenience, in addition to displaying the firmware version of INOGENI devices, the Admin UI and the VidyoRoom On Screen UI now display the firmware version of some Sony cameras, such as the EVI-H100V and SRG-120DH, as well as some Phoenix devices, such as the Quattro3 and Spider.
- Track the temperature of your VidyoRoom systems
- VidyoRooms now monitor their CPU temperature. If the temperature gets to a high or critical level, the temperature reading appears on the Admin UI page that you are currently viewing so that you can promptly address the issue.
- The temperature is also tracked in a log file. This log file is accessible via the Admin UI, and if you’ve enabled the Splunk® forwarder feature, it will also be forwarded to your Splunk server.
- Receive notification that the CMOS battery needs to be replaced
- If the CMOS battery fails, the system date reverts back a few years. When you attempt to manually correct the date via the Admin UI, the CMOS Battery Warning notification appears to remind you to check if the battery needs to be replaced.
- Debug more easily with Recovery Console logs
- To make debugging easier, you can now access the Recovery Console logs.
- These logs are accessible via the Admin UI, and if you’ve enabled the Splunk forwarder feature, they will also be forwarded to your Splunk server.
- Important bug fixes
- In this release, we've addressed some important issues to improve usability and reliability.
- System updates
- For added security and stability, updates for multiple third-party packages and libraries are included as part of this release.
Resolved issues
The following table lists the issues we have resolved in VidyoConnect Room and VidyoRoom version 3.3.19 - resolved issues
VidyoConnect Room and VidyoRoom version 3.3.19 - resolved issues |
|
---|---|
Key |
Summary |
GS-3547 and GS-3161 |
VidyoRoom systems no longer display green video for camera restarts that are due to a false positive. |
GS-3530 |
INOGENI cameras will be selected automatically (if available) after a system reboot. |
GS-3527 |
If a VidyoRoom system is set for an automatic maintenance reboot, it will skip the reboot if another maintenance reboot occurred within the last 10 minutes. |
GS-3468 |
If a VidyoRoom system image file fails due to am ungracefully shutdown or network outage, the new image will now be able to successfully install upon restart. |
GS-3451 |
VidyoRoom systems no longer experience inconsistent audio volume behavior with the speakers when volume changes are applied while the system is not in a call. |
GS-3426 |
New Kingston firmware added to version 3.3.19 prevents VidyoRoom systems from displaying an erroneous message stating that the operating system detected an error on the hard drive. |
GS-3290 |
To improve performance, VidyoRooms now check the call state and block Remote API requests to the VidyoPortal that are not applicable when the VidyoRoom is not in a call. |
GS-3108 and GSI-86 |
In previous releases, an issue caused VidyoRoom HD-100 Rev 4A and HD-40 Rev A systems to go offline after being online for 50 consecutive days. The systems were then unable to successfully reboot. A fix was added to this release, thereby resolving this issue. |
GS-3100 and GS-2804 |
When leaving a conference, if the VidyoRoom system has not completely left within two minutes, the system will forcefully restart the app and will be available to make calls within 30 seconds. |
GS-3058 |
If an INOGENI device was selected as the camera source, it may be deselected after the VidyoRoom HD-40 Rev A is upgraded or rebooted. |
GS-2801, GS-2799, GS-2700, GS-2699, GS-2697, GS-2691, GS-2690, GS-2623, GS-2602, GS-2601, and GS-2580 |
Issues with ungraceful shutdowns, upgrading, booting, and re-imaging VidyoRoom systems have been resolved with the implementation of the Write Protection mode feature, the new Recovery Console, and the CMOS battery warning notification in version 3.3.19. |
GS-2592 |
When a VidyoRoom system experiences the error that caused it to display an unknown software exception error message, the message no longer displays; instead, when the call is over, it generates a dump file from which Vidyo can get the current call state for further debugging, and the application is automatically restarted (which takes about 10 to 15 seconds). |
GS-2472 |
With the Phoenix Super Sensitive mode feature added to version 3.3.19, Phoenix devices can now be enabled to not suppress background noise (such as ventilator sounds). |
Known issues
There are no new known issues for this release.