Network requirements
Third-party Video Conferencing providers
Generally, Mago has the same network requirements as any PC running video conferencing applications like Microsoft Teams, Zoom, Cisco Webex, Google Meet. Specific to Mago, the categories listed as "required" for the video conferencing systems must be open on your firewall. Mago also needs access to Windows Update and Microsoft Intune (if you use Microsoft Intune to manage your devices). For the full list of IPs and URLs required for Mago Room, see:
Microsoft Teams Office 365 URLs and IP address range
Windows Update Configure WSUS
Microsoft Intune Network Endpoints for Microsoft Intune
Mago Meet
Mago Meet uses WebRTC. WebRTC requires a small set of standard signaling and media ports. These ports must be accessible for reliable video conferencing.
Mago Meet works via meet.mago.io or an on-premises hosted domain, and is supported on all modern browsers. It also works with the Mago app for iOS and Android.
Required ports
80
TCP
Outbound
HTTP service for initial access and redirection
443
TCP
Outbound
HTTPS service for signaling, authentication and coordination
3478
UDP
Both
STUN server used for NAT traversal and ICE candidate gathering
5349
TCP
Both
TURN fallback (media relay) for environments where UDP is restricted
10000
UDP
Both
Encrypted A/V media transport (SRTP via WebRTC)
Technical notes
80/TCP and 443/TCP Used for accessing the Mago Link webpage, exchanging signaling messages and establishing secure WebRTC sessions. These ports must be reachable by the sender device.
3478/UDP (STUN) Allows WebRTC clients to discover their public IP and negotiate NAT traversal paths. This improves connectivity on restrictive enterprise networks.
5349/TCP (TURN over TLS, fallback media transport) Used only when UDP media is blocked by network firewalls or when NAT traversal is not possible. If UDP is unavailable, media traffic automatically switches to 5349/TCP.
10000/UDP (media transport) Primary port used for sending audio and video over WebRTC using encrypted SRTP. This port must be open in both directions between the sender and the Mago device to achieve optimal low-latency performance.
When UDP 10000 is blocked, Mago Meet will fall back to TCP 5349, which works but with reduced performance.
Last updated
Was this helpful?