System Requirements (Interoperability)

Supported Devices and Browsers

11Sight native applications and web application works on most of the computers, mobile devices and browsers that have access to a camera and a microphone. In case we can’t access or find a camera and microphone, our system falls back to a text only session, ensuring a communication is established.

Below, you can find our interoperability matrix and platform specific functionality. 

Interoperability

CALLEE

 

 

C
A
L
L
E
R

 

 

 

 

Chrome – Firefox – Opera (Any OS) Safari (iOS 11+, MacOS High Sierra+) – Edge (Chromium)
iOS App (iOS 10+) Android App (Android 5+)
Chrome – Firefox – Opera (All but iOS) Video/Audio/Text Video/Audio/Text Video/Audio/Text Video/Audio/Text
Safari (iOS 11+, MacOS High Sierra+) – Edge (Chromium) Video/Audio/Text Video/Audio/Text Video/Audio/Text Video/Audio/Text
Android App (Android 5+) Video/Audio/Text Video/Audio/Text Video/Audio/Text Video/Audio/Text
Chrome – Firefox – Opera (iOS) Direct to Safari Direct to Safari Direct to Safari Direct to Safari
iOS App (iOS 10+) Video/Audio/Text Video/Audio/Text Video/Audio/Text Video/Audio/Text
Safari (iOS 10-, MacOS Sierra-) Text only Text only Text only Text only

 

Microsoft started to support WebRTC with its latest Chromium version of the Edge browser. Please click here to update or download the latest version.

Platform Specific Functionality

  1. Desktop sharing is available on:

Chrome and Firefox (both on MacOS and Windows, it is not available on mobile browsers)
iOS App

  1. Desktop call receiving is available on:

11Sight web application on Chrome, Safari, Firefox and Opera by keeping a dedicated tab open (both on MacOS and Windows, doesn’t work on mobile browsers)
You can also download our Chrome extension to get notified with a system notification.

  1. Call Recording:

In calls that are answered on Chrome, full video/audio call recording is available. In calls that are answered on iOS and Android apps, audio call recording is available.

  1. 11Sight video calls cannot be established on certain networks due to blocked ports.
    Some network administrators block access to VoIP ports. In these cases, the user should connect to another network or contact their network administrator. Please click here for more information.

  2. QR Codes/SMS Applications

Some QR Code scanners and SMS reading applications open the link in their application which only have limited browser capabilities. In some of those cases, 11Sight video calls will not work and we will ask the person to copy a link and open it in a supported browser.

     

    11Sight RESTful API Integration

    11Sight RESTful API

    External API allows you to communicate with the 11Sight SDK Server. You can create users, fetch their calls, get information related to calls and so on. You can connect to the External API by making REST requests to the API. Base URL to make requests are https://sdk.11sight.com for Production and https://sdktest.11sight.com for Sandbox.

    As an example, to get the list of your subscribers, make a request with the following curl command:

    curl "https://sdk.11sight.com/api/v2/users.json" \
    -H "S-Auth-Token: YOUR_TOKEN" \
    -H "Content-Type: application/json" \
    -d $'{}'

    11Sight Android SDK Integration

    11Sight Android SDK

    Our SDK allows you to add video calls to your app in matter of minutes by incorporating our SDK and using the following functions: loginUser, logoutUser, makeCall, and the callback onMessageReceived.

    The first two are used to sign in the user and sign out the user. Your app uses “makeCall” to initiate a video/audio/text call. Your app should use the onMessageReceived call back which implements “handleIISightNotification” to receive a video/audio/text call.

    All other complexity (session management, network management, call setup and tearing, notifications and recording) is handled and managed by 11Sight which makes your task of adding the communication app extremely simple.

    11Sight iOS SDK Integration

    11Sight iOS SDK

    Our SDK allows you to add video calls to your app in a matter of minutes by incorporating our SDK and using the following functions: signIn, signOut, makeCall, and shareManager.

    The first two are used to sign in the user and sign out the user. Your app uses “makeCall” to initiate a video/audio/text call. Your app should use “shareManager” to receive a video/audio/text call using iOS Call Kit.

    All other complexity (session management, network management, call setup and tearing, notifications and recording) is handled and managed by 11Sight which makes your task of adding the communication app extremely simple.

    11Sight iOS SDK Integration

    11Sight iOS SDK

    Our SDK allows you to add video calls to your app in a matter of minutes by incorporating our SDK and using the following functions: signIn, signOut, makeCall, and shareManager.

    The first two are used to sign in the user and sign out the user. Your app uses “makeCall” to initiate a video/audio/text call. Your app should use “shareManager” to receive a video/audio/text call using iOS Call Kit.

    All other complexity (session management, network management, call setup and tearing, notifications and recording) is handled and managed by 11Sight which makes your task of adding the communication app extremely simple.

    Necessary Ports to Establish Video Calls

    Our Server Addresses

    11Sight native applications and WebApp requires several servers to function. These are:

    1. app.11sight.com WebApp Server: Serves WebApp and the necessary connections for clients
    2. call.11sight.com Sip Server: Helps the video and audio get established
    3. ganymede.11sight.com Stun/Turn Server: fallback for audio / video establishment
    4. turn-eu.11sight.com
    5. turn-bh.11sight.com

     

    Relevant Ports and Their Functions

    List of ports and short functionality that need to be enabled: 

    1. app.11sight.com WebApp Server:

    Port ID Functionality
    80 http
    443 https
    53 DNS

    2. call.11sight.com Sip Server:

    Port ID Functionality
    5060, 5061, 7880, 7881 Session Initiation Protocol (SIP)

    3. ganymede.11sight.com Stun/Turn Server:

    Port ID Functionality
    3478, 3479, 3480, 3481 Stun/Turn

    What You Need to Do

    These ports need to be available in / out and TCP / UDP in the firewall of the network for our serves to be able to establish and maintain video / audio / text calls.