For those wanting to understand more about Firewalls and why they can be a little difficult to diagnose, please read below.
Data is exchanged between a computer and a network of computers, like the Internet, through a series of "ports" or connection places.
For LearnCube to stream video from outside a network/firewall to inside (and vice versa), we require certain "ports" to be open.
Firewalls block or hinder data from passing through these ports (i.e. experienced in the video not rendering or being very slow or cutting out)
LearnCube uses two types of rooms: (1) peer-to-peer room and (2) rooms using a video-server. We find peer-to-peer room the best default option, in general, but larger group classes with more than 6 students may need the video-server.
In an ideal firewall setup, a firewall will keep the ports open to allow the data being exchanged with LearnCube's video servers and the participants. Some ports are more better than others.
If the ideal ports get blocked for any reason (for example a firewall is detected), the connection is routed to another server that LearnCube manages called a TURN (Traversal Using Relays around NAT).
This server tries to traverse (get around) the firewall by relaying all data through another server. A TURN server uses fewer ports and tries to use the ports that are open.
Group rooms are more likely to be impacted by firewall issues as they require more ports to be open.
This is why we provide a Firewall Settings to all companies that have a firewall. An IT department can view the settings through Google doc link here and make the appropriate changes.
We keep this document up-to-date, so we suggest sharing directly with the company IT department, rather than PDF, because then it remains updated automatically.
Once the Firewall is set up correctly to allow LearnCube, please complete this important automated test. It takes just one minute and makes a big difference.
If that all passes green, and the company has sent you a screenshot that this is complete, then it's worth doing an initial test with the company's IT team who will be the most tech-savvy.
If that succeeds, then the logical next step is to roll out to an initial few classes (to reduce risk and iron out any issues) before a full roll-out.