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.

Hardware​

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

Browser​

BrowserMin. VersionMax. Version
Windows/Linux/MacOSChrome75.xcurrent
Firefox65.xcurrent
Edge21.xcurrent
MacOSSafari13.xcurrent
AndroidChrome75.xcurrent
iOSSafari13.xcurrent

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​

Auvious uses WebRTC for media connections, and WebRTC practices involve setting up STUN RFC5389 and TURN (https://datatracker.ietf.org/doc/html/rfc5766) services to allow for direct low latency connection using DTLS-SRTP over UDP (established through NAT traversal using STUN) when network conditions allow it, and indirect using DTLS-SRTP over UDP or TCP (established through NAT traversal using TURN) on more restricted networks. TURN over TCP uses port 443, which is the default port for HTTPS connections and thus will likely be allowed. STUN and TURN are NOT HTTP(s) which means that traditional web application firewall policies might not work. Please consult with your web application firewall and/or network endpoint protection vendor on how to configure it. Listed on the following tables is the ip traffic that should be allowed on your network.

  • European (default) site (https://auvious.video). Test at https://test.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp44334.149.124.157auvious.video static html/javascript/css + https/wss api
    egresstcp44334.120.52.117test.auvious.video static html/javascript/css + https/wss api
    egresstcp44334.78.48.106Traversal Using Relays around NAT
    egressudp44334.78.48.106Session Traversal Utilities for NAT *
    egressudp1024-6553535.187.21.205, 34.78.125.217, 34.78.101.155WebRTC Media over DTLS/SRTP to/from SFUs *

  • US site (https://us.auvious.video). Test at https://test.us.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp44334.120.10.56us.auvious.video static html/javascript/css + https/wss api
    egresstcp44334.110.200.66test.us.auvious.video static html/javascript/css + https/wss api
    egresstcp44335.222.178.127Traversal Using Relays around NAT
    egressudp44335.222.178.127Session Traversal Utilities for NAT *
    egressudp1024-6553534.170.135.44, 34.71.149.245WebRTC Media over DTLS/SRTP to/from SFUs *

  • Australian site (https://au.auvious.video). Test at https://test.au.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp44334.120.134.245au.auvious.video static html/javascript/css + https/wss api
    egresstcp44334.117.36.183test.au.auvious.video static html/javascript/css + https/wss api
    egresstcp44334.116.93.218Traversal Using Relays around NAT
    egressudp44334.116.93.218Session Traversal Utilities for NAT *
    egressudp1024-6553535.201.4.238, 35.189.50.153WebRTC Media over DTLS/SRTP to/from SFUs *

  • Middle East (Saudi Arabia) site (https://me.auvious.video). Test at https://test.me.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp443me.auvious.video (34.117.133.228)me.auvious.video static html/javascript/css + https/wss api
    egresstcp443test.me.auvious.video (34.54.205.231)test.me.auvious.video static html/javascript/css + https/wss api
    egresstcp443turn.tcp.me.auvious.video (34.166.146.220) **TCP Traversal Using Relays around NAT
    egressudp443turn.udp.me.auvious.video (34.166.133.62) **UDP Traversal Using Relays around NAT
    egresstcp443turns.me.auvious.video (34.166.105.216) **TCP/TLS Traversal Using Relays around NAT

  • Middle East (United Arab Emirates) site (https://uae.auvious.video). Test at https://test.uae.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp443uae.auvious.video (51.112.84.49, 51.112.18.166, 40.172.127.140)uae.auvious.video static html/javascript/css + https/wss api
    egresstcp443test.uae.auvious.video (40.172.252.181, 40.172.133.33, 40.172.27.15)test.uae.auvious.video static html/javascript/css + https/wss api
    egresstcp443turn.tcp.uae.auvious.video (51.112.114.58, 40.172.4.247, 40.172.244.168) **TCP Traversal Using Relays around NAT
    egressudp443turn.udp.uae.auvious.video (40.172.200.172, 40.172.237.212, 51.112.56.55) **UDP Traversal Using Relays around NAT
    egresstcp443turns.uae.auvious.video (40.172.250.82, 40.172.207.24, 3.29.155.107) **TCP/TLS Traversal Using Relays around NAT

  • India (Mumbai) site (https://in.auvious.video). Test at https://test.in.auvious.video

    directionprotocolportsnetworkdescription
    egresstcp443in.auvious.video (34.8.129.164)in.auvious.video static html/javascript/css + https/wss api
    egresstcp443test.in.auvious.video (34.8.41.126)test.in.auvious.video static html/javascript/css + https/wss api
    egresstcp443turn.tcp.in.auvious.video (35.200.187.86) **TCP Traversal Using Relays around NAT
    egressudp443turn.udp.in.auvious.video (34.47.221.57) **UDP Traversal Using Relays around NAT
    egresstcp443turns.in.auvious.video (34.47.232.191) **TCP/TLS Traversal Using Relays around NAT

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

**: It's recommended to allow all of these, but allowing just one of these will be enough to allow media traffic.

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.

TypeQualityBandwidth
Audio48Khz~7Kbytes/sec
Video720p/30fps~38Kbytes/sec
Screen1080p/15fps~40Kbytes/sec

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.