Firewall Settings for Scalefusion

Scalefusion is a cloud-hosted solution with servers across the continents. This means devices enrolled and managed by Scalefusion need to have continuous access to Scalefusion's servers so that they can be managed in real-time. The devices also need to have a connection with Google Push services, Apple Push services and Windows Push services, along with other components that are required for the management of devices. Also, to access Scalefusion's Dashboard, the PC/Laptop needs to have access to certain IPs and URLs.

However, an organization might be restricting internet access on their corporate-managed devices and/or PCs/Laptops by using a firewall or a proxy. In such cases, it becomes important to allow the URLs, IPs and ports required for Scalefusion to work smoothly in your organization.

This guide outlines the Firewall settings that need to be done for Scalefusion and OneIdP.

Scalefusion Instances

To comply with data residency regulations, Scalefusion operates multiple regional instances:

Ensure firewall rules are applied according to the instance your organization uses.

General Firewall Requirements (All Regions)

Pushy Service Endpoints: Pushy's firewall requirement is covered by the wildcard domains .pushy.me and .pushy.io. Individual service endpoints such as api.pushy.me and mqtt.pushy.me do not need to be added as separate firewall entries.

Pushy does not publish a complete list of FQDNs/subdomains for firewall allowlisting. Wildcard allowlisting is the supported approach.

Recommendation: Whitelist wildcard domains to simplify firewall maintenance and include all current and future subdomains.

Why do we require Port 80 for mobilock.in and scalefusion.com?

These URLs are typically used to access Dashboard/Console and when a user/Admin types in the URL without explicit https:// prefix, then the request is made on port 80. We use this call to redirect to https:// URL. However if you don’t want this routing then allowing port 80 can be avoided.

Why does the Xirsys URL require port 80?

Scalefusion uses Xirsys to support Remote Cast & Control sessions that happen over WebRTC. Xirsys services, particularly WebRTC TURN/STUN servers, require specific firewall configurations to ensure connectivity, generally relying on HTTP/HTTPS ports for signalling and specialised ports for TURN traffic.Essential settings include enabling TCP and UDP, allowing outbound traffic on ports 80, 443, 3478, and 5349, and permitting outbound UDP traffic for media transmission, with options to narrow down to specific IP addresses if necessary.

Device Platform Specific Firewall Settings

Android

• Google GCM/FCM IPs: Allow all IPs from Google's ASN 15169 (Google ASN IP list) due to frequent IP changes.

• Push notifications: For devices without Google Play Services, ensure the required Pushy domains are whitelisted.

iOS and macOS

• Follow Apple’s official firewall guidelines for Push Notifications:
  Apple Push Notifications Firewall Configuration

• Follow Apple’s official guidelines for Apple Device Management
    Host and Ports required for Apple Device Management
    TCP and UDP ports used by Apple Software Products

Windows

• Windows Update Delivery Optimization:
  See Microsoft’s documentation for URLs and ports required for update optimization and delivery:

  • Ports: 7680 (TCP), 3544 (UDP), 443 (HTTPS)

  • Domains: *.prod.do.dsp.mp.microsoft.com, *.dl.delivery.mp.microsoft.com, *.windowsupdate.com, etc.

Certificate Validation Endpoints (All Regions)

OneIdP Firewall Settings

Remote Cast V2 Firewall Settings (by Region)

Remote Cast V2 Network Overview

Remote Cast V2 uses WebRTC for real-time media streaming. Traffic is split across three endpoints depending on the connection type:

• rc-<region>.scalefusion.com — Signaling for session setup and control.

• turn-<region>.scalefusion.com — TURN relay used when direct media connectivity is unavailable.

• rtc-<region>.scalefusion.com — Direct WebRTC media endpoint for audio/video streams.

A typical session uses the signaling and direct media endpoints. The TURN relay is used as a fallback when direct media connectivity is blocked or unavailable.

Use the region-specific hostnames listed in the table below. Do not construct the hostname by substituting the region name manually.

Minimum Rules for Restrictive Networks

If your firewall policy only permits TCP traffic and UDP ports cannot be opened, allow the following minimum rules:

Running on TCP only can degrade media quality compared to UDP. Users may experience higher latency and reduced video quality. UDP is strongly recommended wherever your network policy permits it.

In closed or restrictive network environments, UDP traffic may be blocked. In such cases, allow the required TCP ports.

Network Connectivity Decision Flow

1. Can the device reach rtc-<region>.scalefusion.com over UDP 50000–60000?

   • Yes: Use the direct media path.

   • No: Attempt the TURN relay.

2. Can the device reach turn-<region>.scalefusion.com over UDP 3478 or UDP 443?

   • Yes: Use the TURN relay over UDP.

   • No: Attempt TURN over TLS.

3. Can the device reach turn-<region>.scalefusion.com over TCP 5349?

   • Yes: Use the TURN relay over TLS.

   • No: Media connectivity may fail. Contact your IT administrator.

Proxy and SSL Inspection

Do not enable SSL inspection on rc-<region>.scalefusion.com if the proxy terminates and re-encrypts TLS traffic, as this can interfere with WebSocket (WSS) connectivity.

UDP media traffic cannot traverse standard HTTP/HTTPS proxies. Ensure UDP traffic to turn-<region>.scalefusion.com and rtc-<region>.scalefusion.com is allowed directly through the firewall.

If your environment uses a PAC file or explicit proxy, ensure WebRTC UDP traffic to the Remote Cast V2 endpoints is sent directly rather than through the HTTP/HTTPS proxy.

IP and Hostname Allowlisting

Remote Cast V2 endpoints may resolve to multiple IP addresses, and the underlying IP addresses may change by region.

Where supported by your firewall, use hostname/FQDN-based rules rather than hard-coded IP addresses.

Remote Cast V2 Quick Reference

For IT administrators configuring endpoint or network firewalls, allow the following outbound traffic for the applicable region:

Content Delivery and CDN URLs by Region

Webhook & Integration IPs (Outbound Server Connections)

Note: These IPs are subject to change without prior notice. Ensure both inbound (client-to-server) and outbound (server-to-client) firewall rules include these IPs for uninterrupted service.

Regional deployments: Ensure the appropriate region-specific Scalefusion endpoints and IP addresses are allowed for deployments in India, MEA, US, and Global regions.

Additional Notes

• TLS Support: Scalefusion supports TLSv1.2 and TLSv1.3 only; ensure your firewall permits traffic over these protocols.

• Allow wildcard subdomains (e.g., *.mobilock.in) where applicable for smoother updates.

• Regular updates to firewall rules may be necessary, especially for Microsoft IP ranges and Google ASN blocks.

• Smokescreen IPs: IP addresses used for server-to-client communications may change without prior notice. Ensure firewall rules are reviewed periodically.