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:
| OS | Minumum Hardware | Recommended Hardware |
|---|---|---|
| Windows | Intel Core i3 with 4GB of RAM | Intel Core i5 with 8GB of RAM |
| Mac0S | Intel Core i3 with 4GB of RAM | Intel Core i5 with 8GB of RAM |
| Linux | Intel Core i3 with 4GB of RAM | Intel Core i5 with 8GB of RAM |
| Android | 4 core 1,5 ghz, 2gb ram | 6 core 2ghz+ , 3gb ram |
| iOS | iOS13+ ( iPhone 6s, SE, ipad air 2 ) | iOS14 |
Browser
| Browser | Min. Version | Max. Version | |
|---|---|---|---|
| Windows/Linux/MacOS | Chrome | 75.x | current |
| Firefox | 65.x | current | |
| Edge | 21.x | current | |
| MacOS | Safari | 13.x | current |
| Android | Chrome | 75.x | current |
| iOS | Safari | 13.x | current |
Operating Systems
The Auvious platform supports the following operating systems:
| OS requirements | |
|---|---|
| Microsoft Windows | Windows 7, 8.x, 10+ |
| Linux | Ubuntu 20 LTS |
| MacOS | 10.13.x + |
| Android | 7.0 + (Device camera required) |
| Apple iOS | 13.0 + (Device camera required) |
Device Requirements
For the platform’s optimal usage and performance, we suggest the following devices:
| Speakers & Microphone | Camera | |
|---|---|---|
| Microsoft Windows | Any OS supported device | Built-in / OS supported |
| Linux | Any OS supported device | Built-in / OS supported |
| Android | Built-in / Headphones | Front / Back |
| Apple iOS | Built-in / Headphones | Front / 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
direction protocol ports network description egress tcp 443 34.149.124.157 auvious.video static html/javascript/css + https/wss api egress tcp 443 34.120.52.117 test.auvious.video static html/javascript/css + https/wss api egress tcp 443 34.78.48.106 Traversal Using Relays around NAT egress udp 443 34.78.48.106 Session Traversal Utilities for NAT * egress udp 1024-65535 Google Cloud scope europe-west1 WebRTC Media over DTLS/SRTP to/from SFUs * US site (https://us.auvious.video). Test at https://test.us.auvious.video
direction protocol ports network description egress tcp 443 34.120.10.56 us.auvious.video static html/javascript/css + https/wss api egress tcp 443 34.110.200.66 test.us.auvious.video static html/javascript/css + https/wss api egress tcp 443 35.222.178.127 Traversal Using Relays around NAT egress udp 443 35.222.178.127 Session Traversal Utilities for NAT * egress udp 1024-65535 Google Cloud scope us-central1 WebRTC Media over DTLS/SRTP to/from SFUs * Australian site (https://au.auvious.video). Test at https://test.au.auvious.video
direction protocol ports network description egress tcp 443 34.120.134.245 au.auvious.video static html/javascript/css + https/wss api egress tcp 443 34.117.36.183 test.au.auvious.video static html/javascript/css + https/wss api egress tcp 443 34.116.93.218 Traversal Using Relays around NAT egress udp 443 34.116.93.218 Session Traversal Utilities for NAT * egress udp 1024-65535 Google Cloud scope australia-southeast1 WebRTC 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.
| Type | Quality | Bandwidth |
|---|---|---|
| Audio | 48Khz | ~7Kbytes/sec |
| Video | 720p/30fps | ~38Kbytes/sec |
| Screen | 1080p/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.