Most Engageli users wont' need to make any changes to their device or network access to join an Engageli class. However, for some users connecting using corporate devices and/or networks, some checks and adjustments may be needed.
What software do I need to access Engageli classes?
If you are using a PC or Mac, all you need is an up to date version of Google Chrome, Microsoft Edge, or Brave browser. No additional download, plug-in or extension is needed.
If you will join the class as a Learner, and have an iPhone, iPad or Android device, you have the option of using the Engageli for Learners app, available from your app store.
When you first join a class, you will need to accept the permissions request to access your Camera and Microphone. Mac users who wish to screen share in-class will also need to grant Screen Recorder permissions to their browser.
Can I test my access?
Before checking the rest of the configurations, use Engageli’s Test Your System to ensure the permissions have been enabled for your audio and video devices. If user workstations have audio, video, and screen share system permissions locked, these will need to be allowed by an IT administrator to ensure the classroom functionality works correctly.
Can I join an Engageli class using a VPN?
While we don't block access through VPNs, we recommend you avoid using a VPN if possible, so that our systems can be free to monitor and adjust the communication between our servers and your device. The way VPNs transfer your data can interfere with the technologies we use to make our platform work. If your employer requires you to use a VPN, please ask your IT team to review this page and the details below about required access, because they may be able to make some optimizations for you.
How are users authenticated on the platform, and how are they managed?
For larger deployments, we recommend an integration with at least one of your systems to provide authentication. This can either be a single-sign-on (SSO) integration with your identity provider, or an LTI 1.3 integration with a Learning Management System (LMS). The LTI 1.3 integration also provides additional capabilities around creation of Engageli classrooms and populating the roster. If you would like to talk about these options, please reach out to your Engageli representative.
Network Access Requirements
For client devices accessing Engageli classrooms, the following Internet resources must be accessible to them.
For loading the classroom interface and any presented material (e.g. PDF, Videos) in-class:
- HTTPS (TCP on port 443) to *.engageli.com and *.engageli-prod.com
For connectivity to power classroom engagement tools (e.g. Chat, Polls):
- WSS (WebSocket Secure) to *.engageli.com and *.engageli-prod.com
For video and audio streaming (using WebRTC technologies) allowing you to see and hear each other in-class:
- STUN (Session Traversal Utilities for NAT) to global.stun.twilio.com:3478
- RTP (Real Time Protocol) to Engageli Media Servers (see below for details) over UDP on ports 5000 to 65000
-
TURN (Traversal Using Relays around NAT) using:
- UDP to global.turn.twilio.com:3478
- TCP to global.turn.twilio.com:3478
- TCP to global.turn.twilio.com:443
Streaming Protocols
Engageli has several ways to provide video and audio streaming to your client device. We try to use the best performing option first, and offer additional options to cater for devices behind firewalls with restrictive connectivity.
- STUN is a protocol used briefly by your client device to determine its public IP address.
- RTP is the protocol that carries the actual video and audio streams. For best performance, we try to send this directly between your client device and the Engageli Media Server. The IP address of the specific Engageli Media Server hosting your Engageli class session will be provided to your client when it loads the Engageli class URL. Your client device will send its public IP address (as discovered through STUN) when establishing the RTP connection to that Engageli Media Server.
- TURN is a protocol that encapsulates RTP traffic and relays the traffic between your client device and the Engageli Media Server. It acts as a backup mechanism when the direct RTP connection cannot be established. Because it encapsulates and relays, it adds latency to the connection which increases the risk of some packets arriving too late to be used in the video stream, which will appear to the end user as reduced resolution, dropped frames, or pixelation.
Firewall Bypass vs Allow Rules
For reliable streaming and the best user experience, we recommend that bypass rules are applied in your firewalls, web filters and/or VPN servers for the above WebRTC resources, to ensure packets are delivered as quickly as possible without any delay due to inspection or scanning.
WebRTC has built-in controls to adjust performance related to latency and jitter, and network delays can adversely affect the perceived performance. Simply allowing the traffic without configuring bypass and/or Quality of Service rules may not be sufficient to ensure good performance.
Engageli IP Ranges
Engageli uses Twilio for high-availability services supporting our streaming technologies. Twilio hostnames will resolve to different IP address ranges depending on your geographical location. See Twilio's documentation here for further information. Please ensure all global ranges are allowed on your network, to cater for your users globally.
Your Engageli instance (including Media Servers) will be hosted on dynamically provisioned IP addresses in an AWS or Oracle Cloud region specific to your Engageli implementation. Please contact your Engageli Partner Success Manager for confirmation of the infrastructure (AWS or OCI) and region used for your Engageli instance. IP ranges for both services are available here:
If you need assistance or clarification, please reach out to support@engageli.com and we can help you understand what is needed to give your users a great experience in Engageli classes.
CDN Providers
Engageli utilizes Gcore for its CDN. If your network requires a list of Gcore IPs, please visit the following page: https://gcore.com/docs/api-reference/cdn/ip-addresses-list/get-cdn-servers-ip-addresses