**Updated as of switch to Okta based log-in platform, May 2022**

Contents

Click on a title to jump straight to the section.

1. Network configuration requirements
2. Network performance requirements

Note that we also offer the following pre-call tester which can help check network bandwidth availability at the location where you're expecting to perform a Connect call. This does not identify dynamic fluctuations to bandwidth availability after the test that may be encountered, such as changes in location, or local network or ISP (Internet Service Provider) network congestion.

Click on the image below to access the pre-call tester, or copy and paste the following link into your web browser: https://tokbox.com/developer/tools/precall/

1. Network Configuration Requirements

In order for the Mira apps and web suite to work as expected, you may need to configure your network as described in this article.

Outbound connections

The following table lists requirements for connectivity from a user's machine to Mira services.

Ruleset configuration requires hostnames, rather than IP addresses

As demonstrated in the above table, we define only hostnames (FQDNs) to include in your rulesets, at this time. This is because most of our service providers use dynamic IP addressing in order to route traffic geographically and adapt to demand (i.e. autoscaling). We do not recommend that you manually resolve the hostnames to IP addresses using a simple dig or nslookup before adding them to your rulesets statically, as the IP addresses may change at any time and without notice.

Most professional and enterprise firewalls support the definition of rules using hostnames. Typically, they automatically determine the list of IPs to allow by responding to the DNS requests made by clients in the network and then recording those IPs into a dynamic list with a TTL. If you’re unsure about how to configure your firewall in this manner, reference the documentation for your firewall. For your convenience, we’ve linked the relevant pages for Zscaler Internet Access (ZIA), Barracuda CloudGen Firewall, pfSense, OpenWrt.

If is is essential to have a list of IP ranges to operate in your network environment, contact our sales team.

Not using a proxy server is recommended

For Mira traffic, we recommend bypassing proxies. Mira traffic is already encrypted, so using a proxy does not make the connection more secure.

Proxies can cause degraded performance and interruptions, as direct, real-time communication is essential for audio and video streams.

NAT configuration

We recommend that your NAT’s configuration has “Endpoint-Independent Filtering” behavior. If a more stringent filtering behavior is important, it is highly recommended that the NAT has an “Address-Dependent Filtering” behavior (see RFC 4787 REQ-8). All NATs shall also have an “Endpoint-Independent Mapping” behavior (see RFC 4787 REQ-1).

For example, if a client behind a Symmetric NAT attempts to connect to a Port Restricted NAT, direct UDP connections will fail. But a Symmetric NAT <-> Address Restricted NAT connection will succeed.

Wi-Fi configuration

The following guidance applies to most enterprise environments. A wireless engineer should evaluate more complex environments, such as manufacturing floors, areas with high levels of radio frequency (RF) noise, or sparsely covered spaces.

• Prefer 5 GHz bands over 2.4 GHz bands.

• Disable low data rates.

• Optimize AP cell placement and configuration for throughput and capacity, rather than purely coverage.

• Implement Wireless Multimedia Extensions (WMM) for WebRTC traffic.

• To allow for seamless roaming, a wireless network should be centrally managed and operated—not a collection of standalone APs.

QoS configuration

QoS is not required to use Mira Connect as it already adapts to network conditions. Use QoS only if you have compelling reasons, such as a congested network, and are able to deploy and maintain an end-to-end QoS model in your network. For more guidance, contact us at support@mirareality.com.

More information

If you have any additional questions, please contact us at support@mirareality.com.

2. Network Performance Requirements

To help answer the question of "what network bandwidth do I need to use Mira Connect?":

• We recommend a minimum dedicated 350kb/s down per downloaded stream, as well as 350kb/s up per uploaded stream to maintain a stable video connection.

For various resolutions and quality combinations, the bandwidth requirements are outlined below.

• • Excellent - None or imperceptible impairments in media
  • Acceptable - Some impairments in media, leading to some momentary disruptions

     

Audio & Video Streams

For the given qualities and resolutions, all the following conditions must be met.

Audio-Only Streams (when extremely low bandwidth environments are encountered)

For the given qualities, the following conditions must be met. Audio only will be sustained at the lowest bandwidth available to allow for the opportunity for continued communication AND resurrection of video feed.

Additional Information

Video quality dynamically adjusts based on the strength of a user's network connectivity.

If you have any additional questions, please contact us at support@mirareality.com.