Web RTC Launcher can supports various browsers and can be used on any Windows platform. Please make sure you have the latest version of your browser installed. Also read the Web Portal Requirements below.

Windows Features

Before starting the RTC Launcher installation, check that the following minimum applications are installed on the system that is supposed to run RTC Launcher.

  • Microsoft .NET Framework 4.5.2
  • Microsoft Unified Communications Managed Runtime
  • Microsoft Visual C++ 2010 Redistributable x64
  • IIS - Internet Information Services
  • Windows Identity Foundation

More information can be found here: https://technet.microsoft.com/en-us/library/gg398686(v=ocs.15).aspx

Windows Features Script

You can use the following Powershell Script (run with administrator permissions) to automatically check required Windows Features for RTC

PowerShell Script: Windows Features Installation

Import-Module ServerManager

$Features = @("NET-Framework-Features",
"NET-Framework-Core",
"NET-Framework-45-Features",
"NET-Framework-45-Core",

"NET-Framework-45-ASPNET",
"NET-WCF-Services45",
"NET-WCF-TCP-PortSharing45",
"Web-Server",
"Web-WebServer",
"Web-Common-Http",

"Web-Default-Doc",
"Web-Dir-Browsing",
"Web-Http-Errors",
"Web-Static-Content",
"Web-Health",
"Web-Http-Logging",
"Web-Performance",

"Web-Stat-Compression",
"Web-Security",
"Web-Filtering",
"Web-App-Dev",
"Web-Net-Ext45",
"Web-Asp-Net45",
"Web-ISAPI-Ext",

"Web-ISAPI-Filter",
"Web-Mgmt-Tools",
"Web-Mgmt-Console",
"Windows-Identity-Foundation")

foreach ($f in $Features) {
    Get-WindowsFeature $f 
}
POWERSHELL

SQL Requirements

RTC Launcher will also require a running SQL server, as described in our Database Preparation. We usually recommend to run this on a separate machine 

Supported Platforms for the Database are:

  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2017

Web-Admin Portal Requirements 

The RTC Launcher Admin Portal is compatible with the following browsers:

  • Internet Explorer 11*
  • Edge
  • Mozilla Firefox (choose latest version)
  • Chrome (choose latest version)
  • Safari (Mac OS)

* With earlier Internet Explorer, users may face a problem with data updating (when data does not get pushed automatically than manually reload of the page is needed). It is recommended to update the Internet Explorer browser to versions 11.

Certificates for access via secure https should not be self-signed. please contact authorized third-party companies to get them.

O365 / Azure Users

The Web-Admin Portal is installed on your system to administrate RTC Launcher via assignment of User RolesWhen an O365 account login is required, make sure you have an Azure AD application ready with the following configuration:

  • Select the Azure Active Directory and then App registrations
  • Click on New registration
  • Under authentication add a new platform web
    • with your redirect URI followed by /signin e.g.  https://rtclauncheradmin.dev.luware.com/signin
  • Enable access tokens and id tokens under implicit grant
  • Under API permissions add the Microsoft.Graph delegated permission for
    • User.Read
    • profile
    • openid
  • Copy the application (Client) ID and the Tenant ID for later use ((info) See System Settings Configuration as a System Administrator)

RTC Installation

RTC Launcher relies on a running Skype for Business Server. There are several options how to use the RTC Launcher:

  • Only chat
  • Audio/Video calls and chat (optional)

Active / Passive Installation types

To make RTC Launcher high available it's possible to run several instances of RTC Launcher components. Different instances should be installed on different servers with the same settings.
In this case it will work in the following way:

SignalR Chat solution

This implementation will use SignalR for chat and doesn't require any additional installations. SignalR allows bi-directional communication between server and client. It supports Web Sockets, and falls back to other compatible techniques for older browsers.

(info) More information can be found on Wikipedia and our Config Tweaks > SignalIR Section..

Pexip - Audio, Video, Screensharing

(tick) Optional: Pexip is a scalable meeting platform, which works as a software-based trans-coding and interoperability engine. It connects Skype for Business with web browsers.

(info) Using of this option will require an additional → Installation of Pexip server.

The following Pexip features are available in browsers:

Web RTC Client

Internet
Explorer

Edge

Mozilla
Firefox

Chrome

Safari
Mac OS

IM

(tick)

(tick)

(tick)

(tick)

(tick)

Audio Call

(error)

(tick)

(tick)

(tick)

(tick)

Video Call

(error)

(tick)

(tick)

(tick)

(tick)

Co-Browsing

(error)

(tick)

(tick)

(tick)

(tick)

Desktop Presenting

(error)

(tick)

(tick)

(tick)

(tick)

Pexip browser compatibility

A visiting user can use a camera and microphone for Audio/Video conversation. Pexip supports this for the following browsers:

Web RTC Client

Edge

Mozilla Firefox

Chrome

Safari
Mac OS

Change microphone before A/V call

(tick)

(error)

(tick)

(tick)

Change camera before A/V call

(tick)

(tick)

(tick)

(tick)

Change microphone during A/V call

(error)

(error)

(tick)

(error)

Change camera during A/V call

(error)

(tick)

(tick)

(error)

Mute microphone during A/V call

(tick)

(tick)

(tick)

(tick)

Mute camera during Video call

(tick)

(tick)

(tick)

(tick)

Pexip device compatibility

Surfly - Co-Browsing

(tick) Optional: Surfly enables Co-Browsing functionality for your RTC Launcher users, so they can see the customer's browser content and assist with navigation. There are two options to integrate Co-Browsing into RTC Launcher:

  • SaaS by Luware: Surfly licences and API keys are automatically generated. You won't need to take further action.
  • Self hosted (on-prem): If you want to host RTC Launcher yourself you need to licence Surfly to retrieve API keys for each tenant. The keys are entered in the System Settings and the feature must be enabled in User Settings (Co-Browsing Tab) for each tenant. One "Agent" user is defined to access Surfly features.
    (lightbulb) Each additional "Agent" (per Tenant) will require further Surfly licences with corresponding running cost.

Network requirements

Please ensure that the ports used for the RTC Launcher components are not used by another application.

Mobile Client

RTC Launcher can also be run on mobile devices (currently only supporting iOS).

  • Currently supported modalities are: Chat, Audio and Video.
  • Escalation is not supported
  • Desktop presenting is possible.

Supported Mobile Browsers:

  • Latest version of Chrome for Android 7+ version;
  • Latest version of Samsung Internet for Android 7+ version;
  • Latest version of Safari for iOS 11+ version.