What are the network requirements for Avatour?

Successfully hosting an Avatour session requires certain capabilities on your local network, including bandwidth availability and certain open ports.

Bandwidth Requirements

Avatour dynamically manages the uplink bandwidth used, subject to the settings in the Avatour Host app as well as real-time network conditions. 

We recommend a minimum of 6mbps uplink for the Host side, and the same downlink for the Guest side. With this bandwidth available, the default Host app setting of 4mbps can be reliably accommodated.

When more bandwidth is available, the Avatour Host app may be set to a higher target bitrate to enable higher quality, up to 10mbps.

If less than 6mbps uplink is available, set the target bitrate in the Avatour Host app to a value that is below your measured available bitrate. This will reduce or eliminate the need for the app to adjust its bitrate on the fly, avoiding interruptions in service.

Network Testtest

To verify network compatibility, we have created a free and easy to use online connectivity diagnostic tool designed to analyze your internet speeds and environment for Avatour session use. This tool can be assessed by going to avatour.testrtc.com and entering your email and reason followed by pressing the orange Start Button.

 

Port Requirements

Accessing an Avatour session from behind a hard firewall or enterprise network requires that you work with your IT/ network administrator to open the following ports in your OS or router’s firewall settings. These requirements apply to all client users, including VR and Web guests and camera operators using the Avatour mobile applications.


 

Hostname

Hostname/ DNS¹

IP / Protocol

Port

Avatour API

api.avatour.live 

https

443

Knack API (legacy)

api.knack.com

https

443

 Signaling Server

webrtc.imeve.com

mediaserver-eu-01.avatour.live (EU)

mediaserver-asia-01.avatour.live (Asia)

52.9.97.68  (TCP)

18.159.49.201

13.251.163.97

443 (TCP)

10000-15000 (UDP)

10000-15000 (UDP)

Twilio TURN servers global.turn.twilio.com https://www.twilio.com/docs/stun-turn/regions

3478 (UDP/TCP)

443 (TCP/ fallback)

Edge Cloud Processor

repeater.avatour.live

18.158.166.94 (Frankfurt)

35.177.213.245 (London)

54.177.91.240 (US West N. California)

35.153.108.146 (US East W. Virginia)

18.219.40.105 (US East Ohio) 

18.179.109.98 (Tokyo)

15.152.83.99 (Osaka)

13.213.133.135 (Singapore)

443 (TCP)

Name Server

ns.photonindustries.io

20.54.217.218  

20.48.71.78

52.142.36.3

5058 (UDP) or

443 (TCP / fallback)

Master Server

azeu707-master.photonindustries.io

52.148.217.242 

5055 (UDP) or

443 (TCP/ fallback)

Game Server

azeu707-game.photonindustries.io

52.148.216.243 

5056 (UDP) or

443 (TCP/ fallback)

Chat Server

azeu707-chat.photonindustries.io

52.148.221.13 

443 (TCP)

Cloud Auth Service

cognito-identity.us-east-1.amazonaws.com

<dynamic>

443 (TCP)

Cloud Asset Storage

avatourweba8d09308da1e423b9e350c521b34b4c8122329-dev.s3.us-east-1.amazonaws.com

<dynamic>

443 (TCP)

Cloud CDN Resource

d2dd9rgq31by0t.cloudfront.net

<dynamic>

443 (TCP)

1. Resolving the host names stated in this list requires the DNS query port 53/UDP to be open to a public name server or for a local name server to be available with request forwarding to a public source.