Classroom - Minimum System Requirements and Technical Considerations

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:

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

Below is a whitelist of ip address Single Device View functionality.  At a minimum, whitelist those specific to your geographical regions. For best performance, whitelist IPs for all regions. To enhance performance traffic will route to other regions. Whitelisting only your region my results in times of slow single device view resolution and blurriness. 

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

Gateways

Xirsys is now available in the following regions

• Check that your firewall has the following ports open for both TCP and UDP: 80, 443, 3478, 5349.
• Allow STUN and TURN at the application level.
• Full cone NAT is recommended.
• Unrestricted UDP connectivity is preferred for local connections.

• (Internal) LAN to WAN (External)

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

• STUN/TURN: Allow port 19302.

Windows Device Client Auto-update

The Windows client can automatically update when new versions are available. To ensure your devices can access the file the following destinations should be whitelisted:

• https://cdn.imp.contentkeeper.net
  
  

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)

Google Stun

• stun.l.google.com
• stun1.l.google.com
• stun2.l.google.com
• stun3.l.google.com
• stun4.l.google.com

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.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.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.azurewebsites.net/*

United Kingdom (UK)

• https://peerjs-production-west-europe.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://peerjs-production-us-southcentral.azurewebsites.net/*
• https://peerjs-production-us-southcentral-2.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.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.azurewebsites.net/*
• https://peerjs-production-us-southcentral.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

Emails

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

• @mailsend.au.backdrop.cloud
• @mailsend.ca.backdrop.cloud
• @mailsend.eu.backdrop.cloud
• @mailsend.uk.backdrop.cloud
• @mailsend.uk.edaware.cloud
• @mailsend.us.backdrop.cloud
• @mailsend.us2.backdrop.cloud