Minimum Requirements Explained

Before we get you set up on Classroom/Wellbeing you need to make sure that you meet the minimum device system requirements. This document takes you through everything you need to verify on your end, to help ensure that you can run either product effectively on your network. 

To complete these steps, it is necessary that you have access to the firewall and content filter. Please contact your Network Administrator or IT organization for assistance.

 

Device Client System Requirements

 

The minimum system requirements for the client are:

Windows	Chrome OS	Android	iOS
2.0 GHz+ Dual Core Processor 4GB RAM 5GB free disk space Windows 11, 10, 8.1 (x64) GoogleChrome or Microsoft Edge Access to cmd.exe	Version 66+ 100MB Free Space Screenshots enabled from Google Admin Console	Android version 9 100MB Free Space	iOS version 11+  100MB Free Space

 

Network Access Requirements

If you encounter issues connecting, the following is a list of end points used, per region, that you should consider whitelisting. 

 

Single Device View / WebRTC

Here is a whitelist by region for the Single Device View functionality.  Only whitelist those specific to your geographical region.  (US customers will have to whitelist both US West and US East).

https://docs.xirsys.com/?pg=ip-whitelist

 

Gateways

Xirsys is now available in the following regions

• Check that you have the correct ports open (80, 443, 3478, 5349).
• Check whether your network allows TCP and UDP packets.
• Allow STUN and TURN at the application level

(Internal) LAN to WAN (External)

Internal Web RTC Port Range (80,443,1024 – 65535)

Reverse Ruleset: -

WAN (XIRSYS IP or FQDN) to LAN (Internal)

Outbound to inbound Web RTC Ports (80,443,3478,5349)

 

Web App

 

The Web App is the front-end interface that the Teachers use with their Students. Whitelisting the below URLs allows the application to connect to the server and be functional. 

ae.backdrop.cloud  TCP port 443

au.backdrop.cloud  TCP port 443

ca.backdrop.cloud  TCP port 443

eu.backdrop.cloud TCP port 443

uk.backdrop.cloud  TCP port 443

us.backdrop.cloud  TCP port 443

us2.backdrop.cloud TCP port 443

(It is necessary that both HTTPS and Secure Websocket connections are allowed)

 

Device Clients

api.global.backdrop.cloud    TCP port 443

api.$cluster.backdrop.cloud   TCP port 443 (Make sure to replace the $cluster with the regional zone, i.e., api.au.backdrop.cloud)

 

In most cases, there is no need to open ports as networks allow for these types of communications without additional configuration.

Whitelist the below URLs depending on your region.  These URLs help ensure that the app connects to the region that you are based in.

 

Australia (AU)

https://sdy8xj00sa.execute-api.ap-southeast-2.amazonaws.com

wss://rlnbn7qy2g.execute-api.ap-southeast-2.amazonaws.com/production

https://peerjs-production-west-europe.scm.azurewebsites.net/*

 

Canada (CA)

https://mkdh9mizn5.execute-api.ca-central-1.amazonaws.com

wss://e1as4iekui.execute-api.ca-central-1.amazonaws.com/production

https://peerjs-production-us-southcentral.scm.azurewebsites.net/*

 

Europe (EU)

https://k04aqptwtb.execute-api.eu-west-1.amazonaws.com

wss://pmninb0fvh.execute-api.eu-west-1.amazonaws.com/production

https://peerjs-production-west-europe.scm.azurewebsites.net/*

 

United Arab Emirates (UAE)

https://nmnt65z4w9.execute-api.me-south-1.amazonaws.com

wss://qghgr11swi.execute-api.me-south-1.amazonaws.com/production

https://peerjs-production-west-europe.scm.azurewebsites.net/*

 

United Kingdom (UK)

https://hmsxbu6cmi.execute-api.eu-west-2.amazonaws.com

wss://txb6bgqyjk.execute-api.eu-west-2.amazonaws.com/production

https://peerjs-production-west-europe.scm.azurewebsites.net/*

https://chub1.imp.uk.contentkeeper.net

wss://chub1.imp.uk.contentkeeper.net

https://chub2.imp.uk.contentkeeper.net

wss://chub2.imp.uk.contentkeeper.net

https://chub3.imp.uk.contentkeeper.net

wss://chub3.imp.uk.contentkeeper.net

https://chub4.imp.uk.contentkeeper.net

wss://chub4.imp.uk.contentkeeper.net

 

United States (US)

https://yebu07gn6d.execute-api.us-east-2.amazonaws.com

wss://qxz3835d92.execute-api.us-east-2.amazonaws.com/production

https://37nrx1baxf.execute-api.us-west-1.amazonaws.com

wss://31e1d6tx50.execute-api.us-west-1.amazonaws.com/production

https://peerjs-production-us-southcentral.scm.azurewebsites.net/*

https://chub1.imp.us.contentkeeper.net

wss://chub1.imp.us.contentkeeper.net

https://chub2.imp.us.contentkeeper.net

wss://chub2.imp.us.contentkeeper.net

https://chub3.imp.us.contentkeeper.net

wss://chub3.imp.us.contentkeeper.net

https://chub4.imp.us.contentkeeper.net

wss://chub4.imp.us.contentkeeper.net

 

The following environments are used for demonstration and testing purposes only:

 

Demo UK

https://1erdi9esr7.execute-api.eu-west-2.amazonaws.com/

wss://35ha11hvwj.execute-api.eu-west-2.amazonaws.com/demo

https://peerjs-production-west-europe.scm.azurewebsites.net/*

 

Demo US

https://7o124w05d3.execute-api.us-east-1.amazonaws.com/

wss://0hvgipjs29.execute-api.us-east-1.amazonaws.com/demo

https://peerjs-production-us-southcentral.scm.azurewebsites.net/*

Emails

By allowing the following emails in your firewall or security application, you enable push notifications and email access.

@mailsend.ae.backdrop.cloud

@mailsend.au.backdrop.cloud

@mailsend.ca.backdrop.cloud

@mailsend.eu.backdrop.cloud

@mailsend.uk.backdrop.cloud

@mailsend.uk.edaware.cloud

@mailsend.us.backdrop.cloud