Skip to main content

Networking and Firewall Whitelisting Requirements

This article describes the networking requirements for the VR Client and our OMS Services to customers.

D
Written by Dave Gardner
Updated today

This article describes the network and firewall configuration requirements needed to run Oxford Medical Simulation (OMS) software and services successfully.

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

🔒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.

Depending on your institution’s firewall setup, you may 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.


🕹️ VR Client Connectivity

The OMS VR Client checks for an active internet connection before loading scenarios.

Address

Protocol

Purpose

8.8.8.8

ICMP (Ping)

Used by the OMS Client to verify network connectivity.

Some networks block ICMP traffic. If this is restricted, OMS may display a “no internet” warning in VR even if connectivity is available.


🌍 Domains

The following domains (and all their subdomains) should be allowed for OMS to operate correctly.

Explicit whitelisting is only needed if your institution blocks unfamiliar or unapproved domains.

Domain

Purpose

Applies To

*.oms-app.com
www1.oms-app.com
www2.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

*.oms-bot.com
natural-language-processor.oxfordmedicalsimulation.tech

Required for voice control and natural language interactions in early versions of Hand and Voice scenarios.

MB7–MB10.0

*.oxfordmedicalsimulation.tech
production-speech.oxfordmedicalsimulation.tech
production-device-usage.oxfordmedicalsimulation.tech

Hosts services required by the OMS Client, including the updated speech and voice control systems.

MB10.1+

*.oms-create.com
production-services.oms-create.com
production-sap-gateway.oxfordmedicalsimulation.tech
auth.oms-create.com

Used for OMS Create (Scenario Authoring Platform) and related content delivery services.

MB8+

Used for anyone downloading the OMS Windows and Mac files for computer-based used

All OMS Clients

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.

If your IT department requires IP-based whitelisting, please refer to the official Cloudflare IP ranges:
🔗 Cloudflare IP Ranges

These IPs may change periodically. OMS cannot guarantee that specific addresses will remain valid.

IP Addresses

OMS recommends whitelisting the above domains rather than IP Addresses (which are subject to change outside of OMS control).

We cannot guarantee that the IP Address will stay within this range.

If you wish to whitelist the IPs for the oms-app.com rather than the domain then you must whitelist the Cloudflare IP which can be found here: IP Ranges | Cloudflare.

Mail

All emails - including invitation, activation and password reset - via the OMS Hub (Web App) come from support@oxfordmedicalsimulation.com

That email address should be added to any email security systems, as well as our email client sending IP address of 149.72.25.54

As we migrate to our new infrastructure we will still use Send Grid but the IP will be 159.183.5.76.

We use Twilio Send Grid for sending emails from the OMS Hub.

Did this answer your question?