Coturn Integration for MDM Server

Understand how a TURN (Coturn) server enables reliable Remote View connectivity for managed devices in restricted network environments.

Before you begin

A TURN (Traversal Using Relays around NAT) server acts as a relay to enable communication between devices and browsers when direct connectivity is not possible due to NAT or firewall restrictions.

In MDM environments, configuring a TURN (Coturn) server ensures that Remote View sessions can be established reliably, even in restricted networks.

The TURN (Coturn) server enables Remote View connectivity when direct communication between browser and device is not possible. It relays traffic and ensures stable connections across NAT and firewall environments.

  • Relays WebRTC traffic
  • Enables connectivity in restricted networks
  • Supports Remote View sessions
Why TURN Configuration is Required:
  • Enables Remote View sessions across NAT/firewall-restricted environments
  • Ensures consistent connectivity between admin browser and managed devices
  • Provides fallback when peer-to-peer connection fails
How It Works:

The MDM server is associated with a configured TURN server. During a Remote View session, the TURN server relays traffic between the browser and the managed device when direct communication cannot be established.

Key Considerations:
  • TURN server must be publicly reachable
  • Required ports must be open (3478, 5349, media ports)
  • DNS resolution must be properly configured
  • Optional TURN URL override can be used for advanced routing setups
Ensure:
  • TURN (Coturn) server is installed and configured
  • MDM server is online and reachable

Procedure

  1. Navigate to Configuration.
    1. Log in to the BigFix Web UI and navigate to Apps > MCM > Admin.
    2. Expand Coturn Service and click Configure MDM Server.
  2. Under Target Devices, click Select.
  3. Select the MDM server device.
    Purpose: Identifies where the TURN configuration will be applied.
    Note:
    • Select only the MDM server
    • Ensure it is online
  4. Under Coturn Configuration, select a TURN server from the Coturn Server dropdown.
    Purpose: Links the MDM server to a TURN server for Remote View sessions.
  5. Configure TURN URL Override (Optional): Enter a custom TURN/TURNS URL if required.

    Example:

    • turn:host:3478
    • turns:host:5349

    Use when:

    • Load balancer is used
    • Proxy or custom routing is configured
  6. Review the Effective TURN URL.
    Note:
    • This field is read-only
    • Ensure it is reachable from browser and devices
  7. Review all values and click Configure.

Results

After configuration:

  • MDM server is linked with TURN server
  • Remote View sessions use the configured endpoint
  • Connectivity works across restricted networks