FUTURE PROOF CONNECT

Virtual Meetings Platform: whitelist guidelines for your IT team.

For IT Teams

Whitelist Guidelines

Individuals from your organization are participating in Future Proof Connect, a virtual meetings event. From time to time, participants have indicated they are unable to access our platform due to corporate firewall or device management restrictions. To ensure your team members can access their meetings, please complete the steps outlined below no later than Tuesday, November 3.

If you have any other questions or need support, please email breakthru@futureproofhq.com and we will be happy to help.

How meetings work on this platform: Meetings open inside the Future Proof Connect app (web browser and mobile app) using the Zoom Video SDK, not the Zoom desktop or mobile client. If any required domain or port is blocked, attendees from your organization will be unable to join their meetings.

Section 1

Web Application

Desktop & iPad / tablet browser. Please ensure all domains and ports listed below are whitelisted. Partial whitelisting will result in meeting connection failures.

Domains

*.personatech.com
*.zoom.us
*.zoom.com

Ports

TCP: 80, 443, 8801, 8802
UDP: 443, 3478, 3479, 8801–8810

Blocking the UDP ports above will prevent all audio and video.

Critical Notes

⚠ UDP Ports 3478, 3479 & 8801–8810 are required. The Zoom Video SDK uses these UDP ports for all audio and video transmission. If these ports are blocked, participants cannot join meetings. These must be open for outbound browser traffic on all participant devices.

⚠ Exempt Zoom domains from SSL/TLS inspection. The SDK loads a WebAssembly (WASM) module on session start. SSL inspection by a corporate proxy can corrupt this download, causing the meeting to appear to load but transmit no audio or video. Exempt *.zoom.us and *.zoom.com from SSL inspection entirely.

⚠ Do not strip Cross-Origin HTTP headers (web only). The SDK requires Cross-Origin-Opener-Policy (COOP) and Cross-Origin-Embedder-Policy (COEP) headers. If a web security gateway strips these, multi-participant gallery view and virtual backgrounds will break. Do not modify these headers for *.personatech.com.

Section 2

Mobile App

iOS & Android. The Future Proof Connect mobile app uses the same Zoom Video SDK integration as the web platform, so the same core domain and port rules from Section 1 apply. Additional considerations for mobile are outlined below.

✓ Personal devices (iOS & Android) — no action required. The Zoom Video SDK works out of the box on personal devices. Participants joining on personal phones over cellular or personal WiFi generally bypass corporate firewalls entirely. No whitelisting is needed for these users.

Corporate-Managed Devices — Additional Rules Required

If participant devices are managed via MDM (e.g. Jamf, Intune, VMware Workspace ONE), the following requirements apply, in addition to all domain and port rules provided above.

If a forced VPN profile is active on the device, all app traffic routes through the corporate network. The same firewall rules from Section 1 apply within the VPN gateway.
Recommended: configure a per-app VPN exclusion for the Future Proof Connect app so its traffic bypasses the VPN tunnel entirely.

If the Future Proof Connect app is installed in the Work Profile, traffic is subject to corporate proxy rules.
Apply all Section 1 domain and port rules to Work Profile outbound traffic.

Some MDM solutions install a root certificate on the device and perform SSL inspection at the device level. The same WASM corruption risk applies as with desktop proxies.
Exempt *.zoom.us and *.zoom.com from device-level SSL inspection in your MDM policy.

Push Notification Domains (Corporate-Managed Devices)

Required for the Future Proof Connect app to deliver meeting notifications and alerts on managed devices.

Platform	Domain	Protocol & Port	Purpose
iOS	`*.push.apple.com` `api.push.apple.com`	TCP 443 TCP 2197 (fallback)	Apple Push Notification Service
Android	`fcm.googleapis.com` `.firebase.com` `.google.com`	TCP 443	Firebase Cloud Messaging (FCM)

⚠ Managed iOS devices — check content filtering profiles. MDM-deployed content filtering profiles (e.g. Cisco Umbrella, Zscaler on-device) can block UDP ports 3478, 3479 and 8801–8810 even on cellular networks. If managed iOS users report connection failures on cellular, check for on-device filtering profiles in your MDM console and add Zoom domain exemptions.