For typical usage our robots require an internet connection. This page describes how the robot uses internet connections, to help with configuring strict firewalls. A typical network without strict firewalls should require no special setup.
When possible we suggest you use domain names rather than IP addresses in your firewall configuration, we do not garauntee we won't change these IP addresses at short notice. The latest updated IP addresses, as of July 17, 2023, are mentioned here to help you in case of any difficulty while setting up.
TCP Connection to update.robot-thespian.co.uk
(62.3.104.54) on PORT 2022: Mandatory for enabling command line level access for Engineered Arts (EA) support and facilitating the robot’s software package downloads. This is not mandatory for day to day operations.
TCP Connection to tritiumrobot.cloud
(18.134.18.162 & 13.41.35.109) on PORT 443: Required for customer and EA's access to the web-based remote admin interface and WebRTC connection negotiation. If your firewall obstructs outgoing connections, please allow the above.
UDP Connection to one or more of time1.google.com
, time2.google.com
, time3.google.com
, time4.google.com
: for accurate time which is required for authentication.
The ideal network situation is for the robot and a PC running the User Interface to be on the same LAN. In this situation the robot can use it's connection to tritiumrobot.cloud to broker a direct encrypted connection over LAN. This will use a random "high port", and is the lowest latency, and most reliable connection option. In other situations a direct connection may be established using a technique called NAT Traversal. If NAT Traversal then fails, the final fallback is a TURN proxy server - the highest latency and least reliable connection type.
It should be noted that for effective customer support we require a connection to the robot. A connection from Engineered Arts support staff to the robot will likely require one or more of the following, even if your local connection works without NAT traversal.
UDP and TCP Connections to/from stun.engineeredarts.co.uk
(162.13.119.185) on PORT 3478: For WebRTC NAT traversal, when the robot is not on the same LAN as the PC running the User Interface.
UDP and TCP Connections to/from turn.engineeredarts.co.uk
(162.13.119.185) on PORT 3478 and 5349: Needed for WebRTC connection proxying, when NAT traversal fails and the robot is not on the same LAN as the PC running the User Interface.
To deliver efficient and timely support, EA requires reliable access to the robot. Our support services might be compromised without this. It is therefore recommended to allow access for all of the network ports mentioned on this page.
The robotic user interface employs WebRTC connections, which perform optimally when a range of ports are open for direct connections. At present, we do not assign any specific port range, hence any inbound UDP port within the range 1024-65535 may be randomly selected.
Higher bandwidth access translates into improved robotic function. It also facilitates quicker remote management, animator transfers, and enhances the telepresence feature's usability and speed.
Telepresence, our most bandwidth-demanding feature, uses WebRTC to stream audio bidirectionally, stream video from robot to operator, and commands from operator to robot.
As per testing conducted at our offices (dated May 16, 2017), the telepresence feature functions acceptably at minimum bandwidth requirements of 4Mbit/s download and 8Mbit/s upload. Greater speeds would, of course, yield better results.