Version 22.3.0
What's new in this release?
- Support for DTMF tones
- This release adds the ability to send Dual Tone Multi-Frequency (DTMF) tones on the audio channel. You can use this in combination with the InviteToConference API to invite a SIP endpoint and enter IVR selection.
- For more information about sending DTMF over WebRTC, refer to the browser capability described in the Using DTMF with WebRTC article.
- For more information about the Vidyo Web User Services API InviteToConference Request, refer to the Web Services API User Guide.
- Improved network conditions adaptation
- The code has been optimized to adapt the outgoing video resolution more rapidly to changing network conditions. This means that the sent camera resolution now adapts more quickly to meet the available bandwidth.
- Enhanced receiver algorithm
- We have improved the algorithm at the receiver side to take better advantage of the device type (desktop, Android phone or tablet, or iOS phone or tablet) and the receive bandwidth.
- With this enhancement, you will be able to receive clearer audio without interruption as well as view better quality video tiles. In addition, this feature enables video tiles to be restored when network conditions improve.
- Support for multiple tiles on tablets
- You can now see more call participants when you join a video call with your Android or iOS tablet. Both types of tablets now support up to three video tiles.
- VP9 SVC support for Safari
- VP9 SVC (Scalable Video Coding) is now supported on macOS Safari. When compared with VP8, this improves video quality while using significantly less bandwidth.
Resolved issues
The following table lists the issues we have resolved in VidyoClient for WebRTC JavaScript Library version 22.3.0.
|
VidyoClient for WebRTC JavaScript Library version 22.3.0 - resolved issues |
|
|---|---|
|
Key |
Summary |
|
IOWEBRTC-2964 |
An issue was fixed where the Native WebRTC client was not receiving remote microphone mute/unmute events from VidyoConnect Binary clients. |
|
IOWEBRTC-2923 |
When the vidyoConnector.ShowViewLabel(...) method is called with the showViewLabel parameter set to false to hide the label, visible artifacts no longer appear. |
|
IOWEBRTC-2773 |
We've improved compliance with the Content-Security-Policy (CSP): "unsafe-eval" is no longer needed to use the Native WebRTC JavaScript library. |
|
IOWEBRTC-2009 |
The enhanced receiver algorithm feature introduced in 22.3.0 fixed some issues, such as the number of participant video tiles sometimes dropping to one even under good network conditions. |
Known issues
The following table lists the known issues in VidyoClient for WebRTC JavaScript Library version 22.3.0.
|
VidyoClient for WebRTC JavaScript Library version 22.3.0 - known issues |
|
|---|---|
|
Key |
Summary |
|
IOWEBRTC-2978 |
On macOS, video from remote participants may freeze after disconnecting a Bluetooth headset while in a call. |
|
IOWEBRTC-2876 |
On macOS and occasionally on iOS, audio stops sending when a call participant switches to another microphone or plugs in an additional microphone. |
|
IOWEBRTC-2650 |
There is an issue with unprocessed audio occurring when a stethoscope is connected and selected as a microphone, causing the remote user not to be heard. This issue was investigated and determined to be an issue with Safari. When Safari is acquiring audio stream from one microphone, it breaks all previous streams from other microphones. For more information, refer to https://bugs.webkit.org/show_bug.cgi?id=235713. |
|
IOWEBRTC-2619 |
Some Samsung devices on Android 11 may not be able to join a call or send/receive media. This was investigated and was determined to be an issue with Samsung. |
|
IOWEBRTC-2423 |
If a user mutes their microphone during a call, the browser still reports that the microphone is in use. This is not a bug. This behavior occurs because VidyoClient still has access to the muted microphone resource to ensure that unmuting the microphone works properly. |
|
IOWEBRTC-2222 |
When a mobile device is in portrait mode, the browser rotates the applied video constraints and switches to landscape mode. This has been investigated and determined to be the behavior for the current Safari and Chrome browsers. |
|
IOWEBRTC-2218 |
When using VP9 codec in desktop or mobile Chrome browsers, the application reacts too quickly to bandwidth fluctuations, which can sometimes lead to reduced outgoing video resolution. |
|
IOWEBRTC-1942 |
On iOS, when a user starts sharing their camera (selects the camera as a source for content sharing), the video stream stops and remote participants see a black video tile. This is due to an iOS bug: https://bugs.webkit.org/show_bug.cgi?id=179363 |
|
IOWEBRTC-1823 |
VP8/VP9 users with limits for receive/send bandwidth may experience fluctuations in frames per second (FPS) and resolution during video calls. |
|
IOWEBRTC-1784 |
Audio lip-sync is delayed on iOS Safari after flipping the camera during a call. This is a known issue with Safari that cannot be fixed by Enghouse Vidyo at this time. |
|
IOWEBRTC-1719 |
On iOS 14+, video continues to transmit during an incoming voice call. |
|
IOWEBRTC-1705 |
Chrome browser sometimes encodes only 720p/10-15 fps, even when the network has enough bandwidth to support a higher frame rate. |
|
IOWEBRTC-1673 |
On Chrome in macOS with dual-core CPUs, the resolution drops when the CPU idle is at 30-50%. |