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.
How media connections are established
Every call gathers several candidate paths in parallel (ICE) and uses the best one that works, so a blocked path normally lowers call quality rather than failing the call. From best to worst:
- Direct over UDP: media flows straight between the browser and the Auvious media servers (SFUs), with the lowest latency and best quality. It needs outbound UDP to the media server addresses, and STUN (UDP 443 to the STUN/TURN address of your region) so the browser can discover its public address.
- TURN relay over UDP: media is relayed through an Auvious TURN server on UDP 443. It adds one hop but keeps UDP's low latency.
- TURN relay over TCP: the same relays on TCP 443, for networks without outbound UDP. TCP adds delay whenever packets are lost.
- TURN relay over TLS (
turns:, TCP 443): the last resort, which gets through most firewalls. The media, already encrypted end to end with DTLS-SRTP, is encrypted a second time inside TLS and carried over TCP, which costs more latency and CPU. It is also the path most affected by proxies and TLS inspection.
For the best call quality, allow the direct path and the UDP relays, not just the TLS relay.
- The address listed for STUN is also a TURN relay (UDP and TCP 443). Blocking it to "disable STUN" also removes the primary relay. If the direct path is unavailable at the same time, calls depend only on the remaining relays.
- STUN and TURN are not HTTP(S). Exclude the addresses below from web proxies, secure web gateways, TLS/SSL inspection and endpoint-protection traffic filtering, and don't apply bandwidth or session-length limits to them. A connection that is set up but then throttled or reset can result in calls where one side's video never arrives.
- Use the test page of your region (for example https://test.auvious.video) from an agent's computer to check connectivity.
If you are using an instance other than the default (EU) one, make sure to update the Auvious application URL on the integration side as well. For Genesys Cloud this should happen before the setup process.
For example, if you are using the us.auvious.video instance in Genesys Cloud, go to Genesys Cloud > Admin > Integrations, locate the Auvious application, and in the Configuration tab update the domain found in application URL from genesys.auvious.com (or auvious.video) to us.auvious.video.
Example:
https://us.auvious.video/setup?pcEnvironment={{pcEnvironment}}&lang={{pcLangTag}}
If you are using the Permissions-Policy header on your website, you need to add auvious to the allowed websites. Make sure to replace auvious.video to your specific region. Value to be added to the header:
camera=(self "https://auvious.video") microphone=(self "https://auvious.video") geolocation=(self "https://auvious.video") fullscreen=(self "https://auvious.video") display-capture=(self "https://auvious.video") autoplay=(self "https://auvious.video") speaker-selection=("https://auvious.video")
-
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 tcp 443 turns.auvious.video (35.205.85.105) ** TCP/TLS Traversal Using Relays around NAT egress tcp 443 turn.auvious.com (78.46.238.121) ** Legacy Traversal Using Relays around NAT *** egress udp 443 34.78.48.106 Session Traversal Utilities for NAT + UDP relay * egress udp 443 turn.auvious.com (78.46.238.121) Legacy UDP Traversal Using Relays around NAT * *** egress udp 1024-65535 35.187.21.205, 34.78.125.217, 34.78.101.155 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 tcp 443 turns.us.auvious.video (34.173.192.204) ** TCP/TLS Traversal Using Relays around NAT egress udp 443 35.222.178.127 Session Traversal Utilities for NAT + UDP relay * egress udp 1024-65535 34.170.135.44, 34.71.149.245 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 tcp 443 turns.au.auvious.video (34.40.205.112) ** TCP/TLS Traversal Using Relays around NAT egress udp 443 34.116.93.218 Session Traversal Utilities for NAT + UDP relay * egress udp 1024-65535 35.201.4.238, 35.189.50.153 WebRTC Media over DTLS/SRTP to/from SFUs * -
Middle East (Saudi Arabia) site (https://me.auvious.video). Test at https://test.me.auvious.video
direction protocol ports network description egress tcp 443 me.auvious.video (34.117.133.228) me.auvious.video static html/javascript/css + https/wss api egress tcp 443 test.me.auvious.video (34.54.205.231) test.me.auvious.video static html/javascript/css + https/wss api egress tcp 443 turn.tcp.me.auvious.video (34.166.146.220) ** TCP Traversal Using Relays around NAT egress udp 443 turn.udp.me.auvious.video (34.166.133.62) ** UDP Traversal Using Relays around NAT egress tcp 443 turns.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
direction protocol ports network description egress tcp 443 uae.auvious.video (51.112.84.49, 51.112.18.166, 40.172.127.140) uae.auvious.video static html/javascript/css + https/wss api egress tcp 443 test.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 egress tcp 443 turn.tcp.uae.auvious.video (51.112.114.58, 40.172.4.247, 40.172.244.168) ** TCP Traversal Using Relays around NAT egress udp 443 turn.udp.uae.auvious.video (40.172.200.172, 40.172.237.212, 51.112.56.55) ** UDP Traversal Using Relays around NAT egress tcp 443 turns.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
direction protocol ports network description egress tcp 443 in.auvious.video (34.8.129.164) in.auvious.video static html/javascript/css + https/wss api egress tcp 443 test.in.auvious.video (34.8.41.126) test.in.auvious.video static html/javascript/css + https/wss api egress tcp 443 turn.tcp.in.auvious.video (35.200.187.86) ** TCP Traversal Using Relays around NAT egress udp 443 turn.udp.in.auvious.video (34.47.221.57) ** UDP Traversal Using Relays around NAT egress tcp 443 turns.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.
***: Legacy relay, still maintained and usable, but planned to be decommissioned in the future. Allowing it is optional: if it is blocked, calls use the current STUN/TURN addresses of the European site (34.78.48.106 and turns.auvious.video).
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.