--- title: Networking Requirements for Video Calls description:   Grip uses WhereBy which relies on WebRTC for its Video Calls, a framework that uses peer to peer (p2p) connections and MESH networking. With these types of connections, audio and video data streams --- [Skip to content](https://support.grip.events/networking-requirements-for-video-calls#main-content) [![Grip-Vertical-Logo-Purple-1.png\]](https://support.grip.events/hs-fs/hubfs/Grip-Vertical-Logo-Purple-1.png?width=23&height=34&name=Grip-Vertical-Logo-Purple-1.png)](https://support.grip.events/?hsLang=en) - [EVENT PARTICIPANT: GET HELP](https://share.hsforms.com/1-lydyoYDTxesUecWSiACWAcomhj) - [EVENT ORGANISER: GET HELP](https://share.hsforms.com/10sOhGhwFQIWjGMDJPxmjbAcomhj?__hstc=193303666.01968b48a56d3c61cbc83cbe4252ad11.1741013975689.1751443637200.1751448757763.154&__hssc=193303666.17.1751448757763&__hsfp=3075744378) Open main navigation Close main navigation - [EVENT PARTICIPANT: GET HELP](https://share.hsforms.com/1-lydyoYDTxesUecWSiACWAcomhj) - [EVENT ORGANISER: GET HELP](https://share.hsforms.com/10sOhGhwFQIWjGMDJPxmjbAcomhj?__hstc=193303666.01968b48a56d3c61cbc83cbe4252ad11.1741013975689.1751443637200.1751448757763.154&__hssc=193303666.17.1751448757763&__hsfp=3075744378) Hello. How can we help you today? - There are no suggestions because the search field is empty. 1. [Grip Knowledge Base](https://support.grip.events/?hsLang=en) 2. [EVENT PARTICIPANTS](https://support.grip.events/event-participants?hsLang=en) 3. [Virtual events](https://support.grip.events/event-participants?hsLang=en#virtual-events) # Networking Requirements for Video Calls #### *\*As of October 2021, Grip Web Networking is no longer supported on Internet Explorer due to Microsoft announcing that they will be sunsetting the browser come June 2022*   Grip uses WhereBy which relies on [WebRTC](https://webrtc.org/) for its Video Calls, 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. | Meeting Type | Required Speeds | Notes | | --- | --- | --- | | One on One Meetings | At least 2.0 Mbps outbound and 2.5 Mbps inbound or higher | | | Four or more participants | At least 3.2 Mbps outbound and 3.2 Mbps inbound are required | Due to the way peer to peer connections are designed, the more participants you add to the call the higher bandwidth you will need. | --- **Latency** 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](https://www.howtogeek.com/126265/how-to-troubleshoot-internet-connection-problems/) test or [TraceRoute](https://www.howtogeek.com/134132/how-to-use-traceroute-to-identify-network-problems/). --- #### Network Configuration & Security #### Firewall 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: - Opening port 443 for outgoing traffic for both TCP and UDP. - Additionally, outgoing traffic should preferably be direct and not sent through a proxy. #### VPN Right now we don't recommend using Whereby 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 Whereby conversation, and then turn it back on after finishing the meeting. --- Quick Answers **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. If you're not able to resolve the issue, be sure to look at our [troubleshooting article](https://whereby.helpscoutdocs.com/article/519-i-keep-having-network-connection-issues). **Using Wifi or Ethernet** Poor WiFi connections are the biggest cause of quality and connectivity problems with Whereby. 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.  - [EVENT PARTICIPANTS](https://support.grip.events/event-participants?hsLang=en#main-content) - [Logging in](https://support.grip.events/event-participants?hsLang=en#logging-in) - [Managing your profile](https://support.grip.events/event-participants?hsLang=en#managing-your-profile) - [Networking on the platform](https://support.grip.events/event-participants?hsLang=en#networking-on-the-platform) - [Virtual events](https://support.grip.events/event-participants?hsLang=en#virtual-events) - [Exports](https://support.grip.events/event-participants?hsLang=en#exports) - [Event Exhibitors and Sponsors](https://support.grip.events/event-participants?hsLang=en#event-exhibitors-and-sponsors) - [GRIP ENGAGE](https://support.grip.events/grip-engage?hsLang=en#main-content) - [Event Setup & Configuration](https://support.grip.events/grip-engage?hsLang=en#event-setup-configuration) - [Profile & Data Management](https://support.grip.events/grip-engage?hsLang=en#profile-data-management) - [Integrations & APIs](https://support.grip.events/grip-engage?hsLang=en#integrations-apis) - [Event Design & Branding](https://support.grip.events/grip-engage?hsLang=en#event-design-branding) - [Event Agenda](https://support.grip.events/grip-engage?hsLang=en#event-agenda) - [Event Engagement](https://support.grip.events/grip-engage?hsLang=en#event-engagement) - [Grip Support](https://support.grip.events/grip-engage?hsLang=en#grip-support) - [MustMeet](https://support.grip.events/grip-engage?hsLang=en#mustmeet) - [Mobile App Management](https://support.grip.events/grip-engage?hsLang=en#mobile-app-management) - [Insights & Reporting](https://support.grip.events/grip-engage?hsLang=en#insights-reporting) - [GRIP MANAGE](https://support.grip.events/grip-manage?hsLang=en#main-content) - [Grip Manage - Integrations](https://support.grip.events/grip-manage?hsLang=en#grip-manage-integrations) - [Grip Manage - Company Portal](https://support.grip.events/grip-manage?hsLang=en#grip-manage-company-portal) - [Grip Manage - Emails](https://support.grip.events/grip-manage?hsLang=en#grip-manage-emails) - [Grip Manage - Registration](https://support.grip.events/grip-manage?hsLang=en#grip-manage-registration) - [Grip Manage - Side Events](https://support.grip.events/grip-manage?hsLang=en#grip-manage-side-events) - [Grip Manage - LQT](https://support.grip.events/grip-manage?hsLang=en#grip-manage-lqt) [![Chill listening crop-3](https://support.grip.events/hs-fs/hubfs/Grip-logo-512x512-light-1.png?width=24&height=24&name=Grip-logo-512x512-light-1.png "Chill listening crop-3")](https://www.grip.events) Grip Help Center Copyright © 2025, Grip