Ohmni Network Admin Guide

Overview

The Ohmni® Robot, is a robust and intuitive telepresence system that aims to promote connectivity and collaboration across vast distances through its high-definition video streaming, high quality audio capabilities, intuitive mobile control, modular software and hardware components, and high-fidelity fleet management. It provides connection and support to anyone, and is used in classrooms, hospitals, and offices in over 34 countries.

The aim of this Guide

This guide will help you understand:

• Ohmni network architecture model
• Ohmni best practices
• Ohmni security and privacy policies
• Requirements and considerations for best operation of an Ohmni system

Who should read this Guide? 

This guide is for network and IT administrators that require knowledge of networking guidelines and considerations for usage of their Ohmni system. It assumes that you are familiar with: 

• Enterprise deployment and issues
• Group policy administration
• Computer networking
• Network security

Important legal information

Please see our:

• Terms of Service
• Privacy Policy
• Terms of Sale
• End User License Agreement

Copyright

The content contained in this document is the property of OhmniLabs Inc.. The content, visual interfaces, information, graphics, design, and all other elements provided in this document are protected by copyright, trade dress, patent, and trademark laws, international conventions, and all other relevant intellectual property and proprietary rights, and applicable laws.   All OhmniLabs Materials are the copyrighted property of OhmniLabs or its subsidiaries or affiliated companies and/or third-party licensors.  All trademarks, service marks, and trade names are proprietary to OhmniLabs or its affiliates and/or third-party licensors.   Except as expressly authorized by OhmniLabs in writing, you agree not to sell, license, distribute, copy, modify, publicly perform or display, transmit, publish, edit, adapt, create derivative works from, or otherwise make unauthorized use of the OhmniLabs Materials.

---

Ohmni Network Architecture

Figure 1: Ohmni Network Data Architecture

Overview

The Ohmni telepresence system is implemented by the Ohmni Cloud Infrastructure (OCI) using the WebRTC standard for real time video, audio and data streaming. Call initialization is done through the ICE protocol which consists of using geographically deployed TURN servers to discover and negotiate connectivity. 

Figure 2: Ohmni Network Call Flow

 

Network Entities

There are 3 main entities in the Ohmni telepresence system, 

1. Ohmni - This is the robot side of the connection. It is important to note that this is not a “Host” in network terms. The Ohmni Robots do not host anything during communication, but serve as one of 2 endpoints in 2-way communication. 
   
   
2. User - This is the user endpoint in 2-way communication, in which a user is using the Ohmni WebApp from a browser on a computer or mobile device.
   
   
3. OhmniLabs Cloud Infrastructure (OCI) - Implements WebRTC real time streaming standard. Collects statuses at each endpoint, logs metrics, and hosts the entire telepresence system (Ohmni WebApp, internal data visualization and management).

 

Network Data Types

There are 4 main categories of data that are transmitted in Ohmni’s Network Data Architecture.

Call Initialization	Initiates the telepresence call and notifies the endpoints and finds the best network route (Local/STUN/Relay) to connect the Ohmni and User.
In-call	Media (video, audio) and other real-time robotic controls comprise the In-call data as part of the telepresence experience. There are 3 modes for this channel: Local (host), P2P, or relayed through OCI if P2P cannot be established.
Status Updates	Reports and updates the statuses and other control messages. E.g. Ohmni coming online and registering with OCI, Ohmni battery percentage update, user interactions with Ohmni WebApp: remote reboot, changing labels, or sharing access with other users, etc.
Logging	The Ohmni and/or User sends usage data: call metrics, call status, call duration and/or other data like login time, and connectivity statuses. This usage data is logged in OCI.

Table 1: Network Data Types

 

Connection Types

WebRTC supports 3 types of connectivity, Local/Host, STUN(srflx/prflx), and Relay. The best path between peers is found through the ICE framework in which Local, STUN, and Relay connections are initially pursued in parallel before the most efficient option is selected. 

Local	Endpoints are on the same network, discovery is simple and connection can be established even without a TURN server. P2P connection is established. When used, this is the most performant.
STUN	Endpoints are on different networks and possibly behind NAT. P2P connection is established. This is a preferred way for connectivity and highly performant.
Relay	Endpoints are behind complex network topology or firewalls. Data goes through our TURN servers and are “relayed” to each endpoint. Less performant than STUN.

Table 2: Connection Types

 

TURN Servers

TURN servers are used as part of the ICE protocol to discover telepresence endpoints and decide the best connection mode for each endpoint pair. During the call initialization process, a list of the Ohmni Network TURN servers is returned to each endpoint, and is enumerated by their latency to each TURN server.  

There are 5 TURN servers located globally that allow endpoints from different geographical regions to connect to the server with the best response time. 

If your network has a restrictive firewall configuration, be sure to allow stateful outbound UDP connection to domains and ports for the TURN servers found below:

Location	Domain	IP Address
US West Coast	turn-uswest.ohmniLabs.com:5349	52.34.180.53:5349
US East Coast	turn-useast.ohmniLabs.com:5349	3.228.252.159:5349
Tokyo	turn-tokyo.ohmniLabs.com:5349	13.230.118.186:5349
Sydney	turn-sydney.ohmniLabs.com:5349	13.211.75.149:5349
Frankfurt	turn-frankfurt.ohmniLabs.com:5349	3.123.222.89:5349

Table 3: TURN Servers

Update and Help Servers

These servers are used to host and provide over-the-air updates and remote support to Ohmni Robots in the event of new software releases or troubleshooting respectively.

Domain	IP Address
update2.ohmnilabs.com	52.27.202.142
helpserver.ohmnilabs.com	44.225.159.39

Table 4: Update and Help Servers

---

Ohmni Network Setup

The following section describes topics related to the general setup and configuration requirements to allow operation of your Ohmni Robot. 

General Network Requirements

1. Broadband internet connection. 
2. Minimum bandwidth of 3Mbps upload and 3Mbps download speeds.
3. A connection to the Ohmni Network TURN servers.

• Strongly recommended but not required:
• Bandwidth of 3Mps upload and 3Mbps download speeds.
• Enabled stateful outbound UDP connection to the Ohmni Network TURN servers on port 5349.

WiFi Requirements 

1. Wifi network coverage that supports IEEE802.11 g/n for 2.4GHz or IEEE802.11 a/n/ac at 5.0GHz for anywhere Ohmni is used inside its operating environment.
   
   
2. Ohmni supports most Wifi Authentication modes, including: Open, WPA/WPA-PSK, and WPA2/WPA2-PSK.
• WPA Enterprise (802.1x) authentication with certificates is also supported, but requires installation of a CA certificate on the Ohmni. See FAQ for further details. 

• Strongly recommended but not required:
• 5.0GHz operating frequency to avoid network and airtime interference from other devices in the operating environment.

 

Firewall Requirements

Prior to adjusting a network’s firewall configuration, it is suggested to run the OhmniLabs network test to check whether a network supports Ohmni’s required connections at both Ohmni and User endpoints. For further information on the OhmniLabs network test, please see the FAQ.

Most networks do not require configuration changes to access the OhmniLabs OCI, However, some restrictive configurations may need changed to allow the following connections:

1. Stateful outbound traffic must be enabled on UDP port 5349. Specifically, the connections must be allowed to access the OhmniLabs TURN servers. The respective domains and ports are listed above.
   
   
2. For access to over-the-air updates and remote support, whitelist the OhmniLabs update and help servers.
   
   
   • If your network does not allow regular HTTP/HTTPS (TCP 80/443) internet access, you must whitelist the following domains to use the Ohmni WebApp.
   • api.ohmnilabs.com
   • app.ohmnilabs.com
   • l79rcoxoh7.execute-api.us-west-2.amazonaws.com
   • sentry.io

 

Ohmni Updates

The Ohmni Robot OS is continually serviced and updated by the team at OhmniLabs. Users are able to check their version of the Ohmni Robot remotely through the Ohmni Cloud Solutions dashboard, Ohmni WebApp, or locally from the robot’s screen. Updates for the Ohmni Robot will not automatically occur, and will always require user permission to update to the latest version. 

An update will take 1-3 minutes to complete, and the Ohmni Robot will restart after installation is complete. Settings for the Ohmni Robot, such as robot name, user access, and wifi configuration are maintained after updates, and do not require input. 

For further information on how to update your Ohmni Robot, please visit our helpdesk guide: “How to Check and Update to the Latest Ohmni Version”, or contact our team at [e-mail]. 

4G LTE & 5G Support

Ohmni Robots can support connections to 4G LTE or 5G networks through the use of mobile hotspots. Once a WiFi hotspot is active, you can connect to it like a normal network, and resume regular Ohmni operation, same bandwidth requirements apply. A SIM card cannot be directly used with an Ohmni, as this is not supported. 

Tip: For fully mobile use of your Ohmni Robot, consider an Ohmni USB Expansion Kit that can provide power to a mobile hotspot secured to your Ohmni as it moves around. 

Proxy Servers

Proxy servers are  generally not supported unless special configuration is done to the proxy server to allow Ohmni traffic. However, proxy server information and authentication credentials can be entered from the WiFi menu (Advanced configuration) after connection to the WiFi access point.

---

Ohmni WebApp

The following section describes topics related to the general setup and configuration requirements to allow operation of your Ohmni WebApp. 

General Network Requirements

1. Broadband internet connection. 
2. Minimum bandwidth of 3Mbps upload and 3Mbps download speeds.
3. A connection to the Ohmni Network TURN servers.

• Strongly recommended but not required:
• Bandwidth of 3Mps upload and 3Mbps download speeds.
• Enabled stateful outbound UDP connection to the Ohmni Network TURN servers.

Ohmni WebApp System Requirements

The recommended system requirements for smooth operation of the Ohmni WebApp are as found below. A system that does not meet the requirements will still be able to run the Ohmni WebApp, but may encounter reduced video quality, reduced audio quality, or greater network latency depending on the system. 

1. CPU: An Intel i5 2.4GHz Quad Core CPU equivalent or higher
2. RAM: 4 GB of RAM or higher 
3. OS: Windows 7 and above, or Mac OSX 10.9 and above
4. Web Browser: The latest version of Chrome is most recommended for Ohmni WebApp operation, however other browsers are supported. The most recent information on browser support can be found here.

The Ohmni WebApp can also run on many of the popular commercial tablets and mobile devices. For best results, it is recommended to use a 6th generation or above version of the iPad, the Safari web browser for Apple devices, and the Chrome web browser for any other device. The most recent information on browser support for laptop, desktops, and mobile devices can be found here.

Ohmni WebApp Updates

The Ohmni WebApp is continually serviced and will always run at its latest release.

---

Security and Privacy

Encryption

For all user-sensitive data, labelled as In-call data, WebRTC enforces DTLS-SRTP. DTLS (Datagram Transport Layer Security) used for key exchange and SRTP (Secure Real-time Transport Protocol) used for media transport. Through the SRTP profile, RTP (Real-time Transport Protocol) data streams are provided confidentiality, message authentication, and replay protection for security of the data. In-call data is encrypted using AES-256. Data is encrypted and decrypted at the end points regardless of connection mode, and streaming data is NOT stored in OCI.

All other data is securely transmitted using HTTPS/TLS 1.3.

Figure 3: Ohmni Network Data Flow

 

Privacy Policy

OhmniLabs cannot, and has no method to: monitor, listen-in, watch, or reroute real-time video, audio and control data from any Ohmni Robot at any time.

For more information, please see OhmniLabs’ Privacy Policy. 

 

Remote Network and Access

Upon authorization from the customer, a designated employee of OhmniLabs can establish console access to an Ohmni Robot through a VPN tunnel for diagnostic purposes. 

---

Network Troubleshooting and Support

The OhmniLabs Customer Support and Success team is available and prepared to assist Ohmni deployment at any time during business hours. Reach out to us the following e-mail, and see our online FAQ for guides and troubleshooting tips.:

• [e-mail]
• https://ohmnilabs.zendesk.com/hc
  

Common Issues

Connection timeout

Timeouts when calling usually occur when Ohmni or User cannot establish one of the 3 connection modes. To troubleshoot this, please:

1. See the firewall configuration help article and set up your network to support Ohmni’s required connection to the TURN, update, and service servers. 
2. If you are unsure of your current firewall configuration, please run our network connection tests on both the Ohmni and User network. Both endpoints need to support the connection for the in-call data to stream correctly. To test on the Ohmni network, you can use the Chrome browser built into your Ohmni, or run the connection test using a laptop on the same network.
3. Although less likely, there may be browser issues, such as permission problems that inhibit a connection from being established. Please see our list of recommended browsers, clear your cache, allow browser permission to camera/microphone, and restart your browser to resolve. 

Bad connectivity

Occasionally, a user may experience poor video and audio latency, low resolution images, unresponsive robot control or delayed audio. The causes of these connectivity issues often stem from: 

• Poor WiFi signal strength
• Moving out of range of an AP
• Frequent switching of APs as a robot moves throughout a building
• Saturated uplink with too many users, high usage. 
• Sub-optimal connection mode, i.e. relay mode instead of p2p. 

Unfortunately, troubleshooting for network connectivity is often case dependent and reliant on the user to manage their WiFi configuration. We recommend these steps as best practices for the smoothest Ohmni experience: 

• Restart your internet modem and/or WiFi router.
• Use 5 GHz network instead of 2.4 GHz network. 
• Restart connection, i.e. disconnect and call again. Sometimes the connection may change from relay to p2p after a reconnection.
• Setup firewall to allow p2p streaming. 
• Restart your Ohmni by holding the power button for 7-8 seconds. Although unlikely, there are  sometimes runaway processes that can overuse CPU and/or memory. 

Best Practices

• Turn off load balancing on AP: Load balancing may cause APs to kick devices off the network to balance out usage. For most devices it is ok because they will just reconnect to another AP but for Ohmni when you reconnect to a different AP the streaming experience will be interrupted. 
• Set QoS for Ohmni traffic to maintain 3Mbit up/down: Mostly applies to corporate networks. Home users can just make sure no one is doing network intensive tasks (internet gaming, video streaming etc.)  on the same network. 
• Use 5 GHz instead of 2.4 GHz WiFi frequency: There is usually more interference on 2.4 GHz.

---

FAQ

Q: What is the average bandwidth used in-call by an Ohmni Robot? 

A: 4.5mbps up/ 1mbps down

Q: My network requires certificate authentication for any internet connection. How can I connect Ohmni to my network? 

A: How to Connect Ohmni to an 802-1x Network that requires Certificates

Q: When I run the OhmniLabs network test I see a warning message in the Connectivity Section.

A: If you see a warning message in the Connectivity Section, this is fine as long as ⅔  connection tests are passed. Although it is preferable for a network to allow all 3 modes of connection, Ohmni will operate on ⅔ connection checkmarks.

Q: What browsers are supported with the Ohmni WebApp?

A: Which browsers can I use with the Ohmni web application?

Q: What are the system requirements to run the Ohmni WebApp? 

A: It is recommended to run an Intel i5 Quad Core CPU or faster, with 4GB of RAM or more. 

What are the recommended system requirements for running Ohmni?


Q: Where can I see the update logs for my Ohmni Robot and the Ohmni WebApp?

A: You can find all changelogs of any Ohmni update here: Changelog.

Q: What are the warranty terms for my Ohmni?
A: Standard Ohmni purchases come with a 1-year Warranty duration. Specific terms on warranty can be seen on our website here: Shipping and Warranty Details

Q: There is trouble or a concern with the deployment of my Ohmni, who can help?

A: Please reach out to our OhmniLabs Support Team! We are available to help on any business day of the week, and will respond to any requests in 1-business day. Please reach out to the Ohmnilabs Support Team at [e-mail].