Partners Blog Contact Us

Configuring Native WebRTC for VidyoPortal Version 20.1.1 - Limited Availability

Follow

If you are using the Limited Availability release of VidyoPortal version 20.1.1, you can use this article to get information about how to configure Native WebRTC, including details about the supported platforms, prerequisites, network and firewall configuration, certificates and encryption, VidyoRouter configuration, and VidyoPortal CORS domain configuration.

 

Supported Platforms

 

Platform OS Version Browsers
Windows® 10 and later Google Chrome 83 and later
macOS® 10.14 and later

Google Chrome 83 and later

Safari® 13.1.1 and later
iOS/iPad OS 13.6 and later Safari
Android™  8 and later Chrome 83 and later

 

Mozilla Firefox® and Microsoft Edge support for desktop is in Beta and is not yet officially supported.

 

In order to configure Native WebRTC with VidyoPortal and VidyoRouter™ version 20.1.1, there are a few additional requirements on the infrastructure.

 

Prerequisites

 

Compatibility Matrix

 

Product Version
VidyoConnect for Desktop 20.1 and later
VidyoConnect for iOS 20.1 and later
VidyoConnect for Android 20.1 and later
VidyoRoom 20.2 and later
VidyoGateway™ 20.1 and later
VidyoReplay™ 20.1 and later

 

Network and Firewall Configuration

 

For Native WebRTC, each VidyoRouter requires an additional two IP addresses (for a total of three). The two additional addresses are for TURN and websocket signaling. In addition, for these two addresses, you must configure two additional FQDNs as DNS entries with the format indicated in this table:

 

IP Address Purpose Public Ports FQDN in DNS
SCIP_IP* Media and binary client signaling

TCP 443 - VidyoProxy

TCP 17990 - SCIP Signaling

UDP 50,000-65,535 (this can be configured to a reduced range)
[vidyorouter].
example.com
 
TURN_IP TURN services for WebRTC TCP 443  [vidyorouter]-turn.example.com 
WEB_IP Websocket signaling for WebRTC TCP 443  [vidyorouter]-web.example.com 

 

*The SCIP_IP is exactly the same as in previous releases that existing clients connect over. In this table, only the public-facing ports are described; management ports like SSH are not mentioned since they are not expected to be public facing.

 

Certificates and Encryption

 

In order for Native WebRTC to work, you must enable HTTPS and media encryption for your deployment. For more information on how to configure this, see the Super Admin: Security article.

 

Configuring Your VidyoRouter

 

Configuring the TURN Interface

  1. Log into the VidyoRouter System Console.
  2. Select A for Advanced Options.
  3. Under Advanced Options, select 8 for TURN Configuration.

    8_TurnConfig.png
  4. Enter the TURN interface IP address and subnet mask.

    Turn_config.png
  5. Select y to save.

    Save_networkservice.png
  6. Proceed to configure Websockets as described in the next subsection.

 

Configuring the Websockets Interface

  1. Log into the VidyoRouter System Console.
  2. Select A for Advanced Options.
  3. Under Advanced Options, select 9 for Websockets Configuration.

    9_Websocket.png
  4. Enter the Websocket interface IP address and subnet mask.

    Websocket_Config.png
  5. Select y to save.

    Save_websocket.png
  6. Select 14 to reboot the VidyoRouter.

    Reboot_Router.png

 

VidyoPortal CORS Configuration

 If you are building your own web application using the VidyoPlatform Client SDK 20.1.0, you will need to configure the CORS domain on the VidyoPortal.

 In VidyoPortal 20.1.1, for both VIdyoCloud and on-premise deployments you must open a Support ticket to add a domain. 

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

Comments

0 comments

Please sign in to leave a comment.