If you are on a work network or any network behind a firewall, you may need to speak with your IT department or network administrator to ensure you have the best setup to enjoy Swapcard. When you do, please provide them the websites and IP addresses below for whitelisting, as well as the ports listed to open.
Domains to allow
*.swapcard.com (Event/Community App)
*.tokbox.com (Video call/Roundtable)
*.opentok.com (Video call/Roundtable)
*.mux.com (Video delivery)
IP addresses to whitelist for inbound traffic to your organization
Swapcard infrastructure outbound IP addresses :
Dedicated email server outbound IP addresses :
IP addresses and ports to whitelist for outbound traffic from your organization to Swapcard
⚠️ Domain whitelisting is strongly recommended, instead of IP’s whitelisting
CDN’s IP address range :
The Swapcard minimum requirement is that TCP port 443 is open. Some firewall/proxy rules only allow for SSL traffic over port 443. You will need to make sure that non-web traffic (TCP/UDP) can also pass over this port.
STUN is a network protocol used primarily for realtime voice/video and messaging, we recommend not to block STUN traffic over port 443.
In addition to the minimum requirements being met, we also recommend that UDP port 3478 is open. This port is used by a piece of hardware called [STUN server](https://www.3cx.com/pbx/what-is-a-stun-server/#:~:text=A STUN (Session Traversal of,outside of the local network.) that helps establish the connection between the participants in the call with a firewall in the middle.
For the best possible experience, we recommend that UDP ports 1025 - 65535 be open. Once these ports are open, there is no need for intermediary STUN/TURN servers which removes a hop from the media traffic.
Use this exclusive Bandwidth Calculator to understand your internet needs as you plan your next event. Select the categories that apply to your event and follow the instructions for each section to estimate your total bandwidth requirement:
Bandwidth for attendees and moderators
Because Conferences i/o is built for performance, even over slow connections, the bottleneck at events tends to be wireless access point saturation. That is, a wireless access point may not be able to accept every device that is trying to connect to it.
Conferences i/o total data consumption varies by the size of a session, and how actively the session is being used. Larger sessions consume more data per person, because there are more transactional changes.
The following table gives estimates on bandwidth usage assuming very heavy usage (e.g., non-stop polling and Q&A). These numbers assume that everyone at the event is using the venue's wireless network. Your actual usage is likely to be far below these numbers.
Average bandwidth per attendee, per hour
Average bandwidth consumed by entire session, per hour
Recommended connection speed
In general, a minimum rating of 30 Kbps per attendee is recommended.
For a 100-person session, this works out to a 3.0 Mbps connection.
For a 1000-person event, this means a 30 Mbps connection.
Considerations for presentation computers
Presentation computers connect to the same real-time services as attendees and moderators, however, we recommend using a wired connection to the Internet if one is available. A wired connection with 5 Mbps connectivity should be more than sufficient for Conferences i/o.
Total data consumption by a presentation computer will be minimal when compared to the total data used by attendees. However, the following table gives estimates on bandwidth consumption per hour, during very heavy usage (non-stop polling and Q&A). These numbers assume that everyone at the event is using the venue's wireless network. Your actual usage is likely to be far below these numbers.
Average bandwidth consumed by presentation computer, per hour