Network requirements

For optimal performance, verify that the network where AirSync and the AirSync client operates has the firewall configured to allow the following connections:


Relay connection

Relay connections are used in scenarios where direct connections between devices are not possible due to network configurations.


With wildcards

  • TCP 443 for *.myviewboard.cloud
  • TCP 443 for *.myviewboard.com
  • TCP 443 for *.viewsonic.com
  • TCP 443 for *.airsync.net
  • TCP 443 for *.cloudflare.com
  • TCP 443 for *.googleapis.com
  • TCP 443 for *.in.applicationinsights.azure.com
  • TCP 443 for *.sentry.io


Without wildcards

For firewalls that don't allow wildcards.


  • TCP 443 for airsync.net
  • TCP 443 for www.airsync.net
  • TCP 443 for airsync.viewsonic.com
  • TCP 443 for api.airsync.net
  • TCP 443 for us-east-1.gateway.airsync.net
  • TCP 443 for ap-northeast-1.gateway.airsync.net
  • TCP 443 for ap-southeast-1.gateway.airsync.net
  • TCP 443 for us-west-1.gateway.airsync.net
  • TCP 443 for us-east-2.gateway.airsync.net
  • TCP 443 for eu-west-2.gateway.airsync.net
  • TCP 443 for appconfig.airsync.net
  • TCP 443 for getice.myviewboard.cloud
  • TCP 443 for store2.myviewboard.com (OTA)
  • TCP 443 for store2.airsync.net (OTA)
  • TCP 443 for firebaseremoteconfig.googleapis.com
  • TCP 443 for firebaseinstallations.googleapis.com
  • TCP 443 for firebaseremoteconfigrealtime.googleapis.com
  • TCP 443 for api2.amplitude.com (Analytics)
  • TCP 443 for eastus-8.in.applicationinsights.azure.com (Analytics)
  • TCP 443 for o4508005887442944.ingest.us.sentry.io (Analytics)


Video/Audio (WebRTC)

  • TCP 443 for turn.myviewboard.cloud
  • TCP 3478 for turn.myviewboard.cloud
  • UDP 3478 for turn.myviewboard.cloud (Optional)
  • UDP 3478 for stun-cloud.airsync.net
  • UDP 3478 for turn-cloud.airsync.net
  • TCP 80 for turn-cloud.airsync.net
  • TCP 443 for turn.cloudflare.com
  • Local UDP ports 32768~65535



Local Connection (Direct connection)

Establish a network connection directly between devices within the LAN without relying on external servers or services.

  • TCP 5100


Remote Screen

  • TCP 7000


Video/Audio (WebRTC)

  • Random UDP ports in the range of 32768~65535


Mirror

AirPlay, Googlecast, and Miracast do not require access to the Internet.


  • AirPlay, Google Cast
    • Does not work in different subnet/VLAN
    • Random UDP ports in the range of 32768~65535

  • Miracast
    • Use Wi-Fi Direct (WiFi P2P). Does not require wireless AP.



Bandwidth requirements

To improve image quality and user experience, ensure that the network bandwidth should be at least: 

  •  5Mbps for a WebRTC session casting on full HD, or 
  • 15Mbps for a WebRTC session casting on higher resolutions 


The casting resolution is determined by:

  • Resolution of the sharing screen, and
  • If "High image quality" setting is active


If the "High image quality" is: 


  • OFF: 
    Max casting resolution up to QHD (2K), if the device sharing its screen supports this resolution.  

  • ON: 
    Max casting resolution goes up to UHD (4K), if the device sharing its screen supports this resolution.  


To compute for total network bandwidth usage, multiply the minimum bandwidth per session by the number of concurrent sessions.



Miscellaneous info

Note the following information for the systems mentioned below.


  • Limit WebRTC port range in Chrome

Chrome policies (WebRtcUdpPortRange) can limit the range of local UDP ports used by WebRTC. Refer to setting UDP port ranges in the following page:



Need additional help?

Check our other resources — we'll be happy to assist you.