Skip to main content

Client Requirements

Following you'll find the requirements that users (both agents and customers) must meet in order to be able to use the Auvious platform.


The Auvious Video Counselor platform supports most modern hardware. If the manufacturing company of a device still supports it, it is almost certain that it is also supported on the Auvious platform.

Exceptions and accompanying recommendations as provided below:

OSMinumum HardwareRecommended Hardware
WindowsIntel Core i3 with 4GB of RAMIntel Core i5 with 8GB of RAM
Mac0SIntel Core i3 with 4GB of RAMIntel Core i5 with 8GB of RAM
LinuxIntel Core i3 with 4GB of RAMIntel Core i5 with 8GB of RAM
Android4 core 1,5 ghz, 2gb ram6 core 2ghz+ , 3gb ram
iOSiOS13+ ( iPhone 6s, SE, ipad air 2 )iOS14


BrowserMin. VersionMax. Version

Operating Systems

The Auvious platform supports the following operating systems:

OS requirements
Microsoft WindowsWindows 7, 8.x, 10+
LinuxUbuntu 20 LTS
MacOS10.13.x +
Android7.0 + (Device camera required)
Apple iOS13.0 + (Device camera required)

Device Requirements

For the platform’s optimal usage and performance, we suggest the following devices:

Speakers & MicrophoneCamera
Microsoft WindowsAny OS supported deviceBuilt-in / OS supported
LinuxAny OS supported deviceBuilt-in / OS supported
AndroidBuilt-in / HeadphonesFront / Back
Apple iOSBuilt-in / HeadphonesFront / Back

Network Requirements

On most networks there will be no need for any special setup, as long as the outgoing traffic to port 443 is not filtered or blocked. However it is standard practice on large corporate networks to filter/block outgoing traffic as well in order to have more control over what parts of the Internet their employees can access. For such occasions, the firewall must allow the traffic in the table that corresponds to the Auvious region that is used:

  • European (default) site (

    egresstcp44334.149.124.157static html/javascript/css + https/wss api
    egresstcp44378.46.238.121 (deprecated)Traversal Using Relays around NAT
    egressudp44378.46.238.121 (deprecated)Session Traversal Utilities for NAT *
    egresstcp44334.78.48.106Traversal Using Relays around NAT
    egressudp44334.78.48.106Session Traversal Utilities for NAT *
    egressudp20000-40000Google Cloud scope europe-west1WebRTC Media over DTLS/SRTP to/from SFUs *
  • US site (

    egresstcp44334.120.10.56static html/javascript/css + https/wss api
    egresstcp44335.222.178.127Traversal Using Relays around NAT
    egressudp44335.222.178.127Session Traversal Utilities for NAT *
    egressudp20000-40000Google Cloud scope us-central1WebRTC Media over DTLS/SRTP to/from SFUs *
  • Australian site (

    egresstcp44334.120.134.245static html/javascript/css + https/wss api
    egresstcp44334.116.93.218Traversal Using Relays around NAT
    egressudp44334.116.93.218Session Traversal Utilities for NAT *
    egressudp20000-40000Google Cloud scope australia-southeast1WebRTC Media over DTLS/SRTP to/from SFUs *

*: Optional but highly recommended, in order to avoid using tcp relay for media.

Bandwidth Requirements

Bandwidth usage is directly proportional to the number of outgoing and incoming media streams that are active simultaneously. Listed below are typical values for each type of stream.


To illustrate, to support ten concurrent calls with two participants sharing their microphone and camera, and one of them also sharing their screen, the bandwidth required on the infrastructure will be 10 * (2 * (7 + 38) + 40) ~= 1.3MByte/sec both upload and download a full duplex ~10.5Mbit/sec line. Each participant needs 7 + 38 + 40 ~= 85Kbyte/sec or ~ 680kbps upload and download to support simultaneous use of audio, video, and screen sharing.