Before we get you set up on class:room make sure that you meet the minimum device system requirements. This document is intended to take you through everything you need to verify on your end, to help ensure that you can run either product effectively on your network and device.
Device Client System Requirements
The minimum system requirements for the client are:
iOS version 11+
100MB Free Space
Android version 7+
100MB Free Space
For example, most modern laptops or desktop PCs can run the Device Client.
|Any modern Chromebook device is able to run the Device Client. ChromeOS version 66 was released in April 2018.||Any modern iOS device is able to run the Device Client. iOS 11 was released on September 17, 2017.||Any modern Android device is able to run the Device Client. Android 7 was released on September 23, 2008.|
Network Access Requirements
It is necessary that the following addresses and ports, depending on region, are allowed in your firewall or security application. By doing this helps ensure that the client can connect safely and securely to the server and users can authenticate into the application.
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.
uk.backdrop.cloud TCP port 443
us.backdrop.cloud TCP port 443
ae.backdrop.cloud TCP port 443
au.backdrop.cloud TCP port 443
(It is necessary that both HTTPS and Secure Websocket connections are allowed)
The Device Client uses the below URLs to communicate with the Web App over the Internet and therefore being able to use the application.
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)
*xirsys.com TCP/UDP TCP/UDP port 80, 443, 1024-65535**
**The Impero class:room utilizes webRTC technology to provide the live view from devices in the web browser. webRTC uses TCP/UDP ports in the following range: 1024-65535.
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.
AE (Arab Emirates)
au-southeast-production-iothub.azure-devices.net TCP/UDP port 8883, 5671
au-southeast-production-iothub-dps.azure-devices-provisioning.net TCP port 443
au-southeast-production-iothub-dps.provision.proxy.global.backdrop.cloud TCP Port 443 (ChromeOS only)
au-southeast-production-iothub.hub.proxy.global.backdrop.cloud UDP port 8883 (ChromeOS only)
- AU (Australia)
west-eu-production-iothub.azure-devices.net TCP/UDP port 8883, 5671
west-eu-production-iothub-dps.azure-devices-provisioning.net TCP port 443
west-eu-production-iothub-dps.provision.proxy.global.backdrop.cloud TCP Port 443 (ChromeOS only)
west-eu-production-iothub.hub.proxy.global.backdrop.cloud UDP port 8883 (ChromeOS only)
UK (United Kingdom)
uk-west-production-iothub-dps.azure-devices-provisioning.net TCP port 443
uk-west-production-iothub.azure-devices.net TCP/UDP port 8883, 5671
uk-west-production-iothub-dps.provision.proxy.global.backdrop.cloud TCP Port 443 (ChromeOS only)
uk-west-production-iothub.hub.proxy.global.backdrop.cloud UDP port 8883 (ChromeOS only)
US (United States)
us-southcentral-production-iothub.azure-devices.net TCP/UDP port 8883, 5671
us-southcentral-production-iothub-dps.azure-devices-provisioning.net TCP port 443
us-southcentral-production-iothub-dps.provision.proxy.global.backdrop.cloud TCP Port 443 (ChromeOS only)
us-southcentral-production-iothub.hub.proxy.global.backdrop.cloud UDP port 8883 (ChromeOS only)
The URLs below are used for trial accounts or trial environments.
By allowing the following emails in your firewall or security application, you enable push notifications and email access.