Remotehour is built on WebRTC, a framework that uses peer to peer (p2p) connections and MESH networking. With these types of connections, audio and video data streams are sent directly between two or more user devices. This can be a great way to send data for smaller groups, but it relies on a fast internet connection and minimal latency. As more users join in on the call, more network speed and bandwidth is required.
We don't currently have a way to measure exactly what the required speed of the connection is between each of the callers, but we can recommend some average network speeds that are suggested for WebRTC products like ours! In general: the higher your internet speeds, the better quality of video and audio you will receive.
For latency, you will want to make sure you are experiencing less than 100 ms on your network for the best experience. Up to 400 ms is acceptable, but not ideal for high-quality conversations. You can check your latency by running a Ping test or TraceRoute.
If you or your company use a firewall, you may experience some connection problems depending on your firewall settings. For a smooth experience, we recommend:
Right now we don't recommend using Remotehour with a VPN. Because our service is peer to peer, not having a consistent IP address can cause problems connecting to rooms, or in some cases a specific guest in the room. Our recommendation is to turn off your VPN when having a Remotehour conversation, and then turn it back on after finishing the meeting.
What should I do if I'm experiencing connectivity problems?
It's a good idea to try out a few different networks to rule out the possibility of a WiFi issue. Switching to a different router or trying an ethernet connection may resolve the issue, so this is the first recommendation.
Using Wifi or Ethernet
Poor WiFi connections are the biggest cause of quality and connectivity problems with Remotehour. In many cases, the connection may be fast and stable enough at the modem, but a bad router or excessive traffic on the router can cause problems in the call. In an office environment, for example, a router may be overloaded due to the number of computers connecting. So if this is the case, we recommend using Ethernet.