Most institutions will already meet these requirements by default.
However, in more restricted network environments, your IT department may need to review and confirm the following settings to ensure OMS functions correctly.
⚙️ Overview
OMS connects securely to several online services for:
Launching and running VR and on-screen scenarios
Delivering content updates
Sending simulation feedback
Supporting features such as voice control and multiplayer sessions
🛜 Internet Speed and Bandwidth
For a guaranteed experience, OMS requires a minimum:
Upload speed: 5mbps
Download speed: 5mbps
🔒 Ports
Web Services
OMS uses standard web ports for accessing the OMS Hub and online services.
Port | Protocol | Purpose |
80, 443 | TCP | Required for all OMS web applications and services. Used for authentication, feedback submission, and content delivery. |
These ports are typically open by default on most networks.
Multiplayer
For multiplayer scenarios, OMS uses Photon Engine to manage real-time connections between users.
Port(s) | Protocol | Purpose |
5055, 5056, 5058, 27000, 27001, 27002 | UDP | Used for multiplayer communications and live instructor sessions. |
For further technical detail on these ports, see Photon's documentation.
If your institution restricts outbound traffic on ports 80 or 443 and you want to use multiplayer features, you will also need to whitelist: ns.exitgames.com
Note: OMS uses a legacy version of the Photon Engine. Documentation for current versions may differ slightly from the implementation OMS uses.
We use fixed IP addresses for multiplayer, so your institution can whitelist these directly. All multiplayer communication takes place over UDP.
Type | IP | DNS | Purpose |
Name Servers | 20.54.217.218 | ns.photonindustries.io | Acts as the primary point of entry for clients connecting to the network, handling initial authentication and providing a directory of available regional Master Servers. |
Master/Game Servers | 216.120.180.102 | CLUSTER-05AE38571ECD72724D6EBE64B669C20F.photonindustries.io | Connects multiple players in real time, synchronizing their actions and managing multiplayer sessions across devices and platforms. |
VR Client (versions earlier than OMS11)
The VR Client checks for internet connectivity by pinging the Google DNS servers at 8.8.8.8 using the ICMP protocol.
🌍 Domains
The following domains (and all their subdomains) should be allowed for OMS to operate correctly.
We actively work to ensure our domains are not blocked by major providers, so explicit whitelisting may not be necessary depending on your firewall vendor. Explicit whitelisting is only needed if your institution blocks unfamiliar or unapproved domains.
Domain | Includes | Purpose | Applies To |
| www1.oms-app.com | Primary OMS web application and login portal for learners and instructors. Required for authentication, scenario launch, and feedback submission. | All OMS Clients (speech requires MB11+) |
| natural-language-processor.oxfordmedicalsimulation.tech | Entry point into the ML models required for voice control scenarios. | MB7–MB10.0 (from MB10.1 onwards, voice control traffic goes through the speech API — see |
| production-services.oms-create.com | Used for OMS Create (Scenario Authoring Platform) and related content delivery services. | MB8+ |
| production-speech.oxfordmedicalsimulation.tech | Hosts services required by the OMS Client, including voice control. | MB10.1+ |
generate_204 endpoints | The VR client sends a GET web request to these sites, in a round robin, as a way of verifying internet reachability. These pages have no content by design. | MB11+ |
OMS domains and subdomains are hosted via Cloudflare, which provides content delivery and DDoS protection.
OMS cannot provide fixed IP addresses for these domains.
📇 IP Address Information
OMS services are hosted behind Cloudflare's global network. Because Cloudflare manages routing and security, OMS cannot provide static IP addresses for any of its domains.
As with most modern APIs and web services, our infrastructure is cloud-based and designed to be dynamic and flexible, for reasons of scalability, cost-efficiency, security, and simplified network management. For this reason, we recommend whitelisting by domain rather than by IP address.
If your IT department requires IP-based whitelisting, please refer to the official Cloudflare IP ranges:
These IPs may change periodically, and we cannot guarantee that any specific address will remain valid.
IP Addresses
OMS recommends whitelisting the above domains rather than IP addresses, which are subject to change outside of OMS control.
If you wish to whitelist the IPs for oms-app.com rather than the domain, you must whitelist the Cloudflare IP range, which can be found here: IP Ranges | Cloudflare.
All emails — including invitation, activation, and password reset emails — sent via the OMS Hub (Web App) come from support@oxfordmedicalsimulation.com
That email address should be added to any email security systems, along with our email sending IP address of 159.183.5.76.
We use Twilio SendGrid for sending emails from the OMS Hub.
Note: The previous sending IP address, 149.72.25.54, is no longer in use and can be removed from any email security systems.
Quic Protocol
If your institution blocks Quic traffic, your firewall may attempt to decrypt that traffic for inspection as part of its monitoring. In at least one case, this has meant an institution needed to add OMS network traffic to their no-decrypt list.