Transfr and Quest Headset Spec Sheet
Transfr Specifications
Ports
443
80
Headset Must be able to communicate with:
https://backend.transfrvr.com
https://func.transfrvr.com
https://functions.transfrvr.com/
https://vr-api.transfrvr.com/
https://xr-assets.transfrvr.com/
https://mqtt-proxy-server.tx-xr.com
https://shared-message-broker-prod.tx-xr.com
http://transfrvr-asset-bundles.s3.us-east-2.amazonaws.com/
http://o505023.ingest.sentry.io/
https://d2mejnog76nh2i.cloudfront.net
To Access the Transfr Dashboard and Transfr Trek on a Device with Web Browser, must be able to communicate with:
transfrinc.com or
https://trek.transfrinc.com
https://dashboard.transfrinc.com
https://supportcenter.transfrinc.com
transfrvr.com or
https://dashboard-api.transfrvr.com
https://insights-api.transfrvr.com
tx-xr.com or
https://ce-student-experience.tx-xr.com
https://ooh-service.tx-xr.com/
https://core-auth.tx-xr.com/
ManageXR Endpoint List
ManageXR uses the internet to communicate with its servers and keep devices in sync with configurations set by ManageXR organization admins. When connected to a network that uses a firewall, ManageXR’s web traffic will be routed through your firewall, and must allow this traffic to ensure that ManageXR can operate as intended.
Allow - List Rule | Port | Protocol | Why |
|---|---|---|---|
us-central1-mighty-platform-prod.cloudfunctions.net | 443 | TCP (HTTPS) | Communication with the ManageXR API |
mighty-platform-prod.appspot.com | 443 | TCP (HTTPS) | Communication with the ManageXR API |
us-central1-mighty-platform-prod.cloudfunctions.net | 443 | TCP (HTTPS) | Communication with the ManageXR API |
managexrapi.com | 443 | TCP (HTTPS) | Communication with the ManageXR API |
*.managexr.com | 443 | TCP (HTTPS) | Communication with the ManageXR API |
*.googleapis.com | 443 | TCP (HTTPS / WebSockets) | Communication with the Google Cloud Platform APIs used by ManageXR |
*.crashlytics.com | 80, 443 | TCP (HTTP / HTTPS) | ManageXR error reporting We use port 80 for error reporting from our admin app via a tool called Firebase Crashlytics. It's important for us to be able to diagnose issues with devices. If this is a security concern, districts may keep it closed as it is not mission critical, and closing it won't interfere with day-to-day use of the platform or devices. |
openrelay.metered.ca | 80, 443 | UDP, TCP (HTTP / HTTPS) | Used for Realtime Device Streaming |
MAC Addresses of Headsets
MAC Addresses are available upon request, please contact Technical Support.
MAC Addresses of Headsets
Bandwidth:
For regular training usage of the Transfr applications, standard Wi-Fi bandwidth similar to that needed to send or receive Word document files is all that is required for the headsets for login authentication and uploading of data (standard training sessions use about 50 mb total). A 20 mb/second connection, or stronger, is recommended.
Incremental Transfr software updates require higher bandwidth as they may exceed 1-8 GB download size. However, Transfr will always schedule updates at the convenience of each customer.
WPA Compatibility For Wi-Fi Connectivity
Network configuration itself is not within Meta support boundaries. However, the Quest 2 headsets are able to connect to WPA/WPA2/WPA3-Enterprise networks. You can manually connect the headset to a wireless network that requires WPA-Enterprise credentials.You can select the security type and choose the WPA/WPA2/WPA3-Enterprise option. Withthis option selected, you now have access to the following fields:
EAP Method: PEAP, TLS, TTLS, PWD
Phase 2 Authentication: MSCHAPV2, GTC
CA Certificate: Use System Certificates, Do Not Validate
With Use System Certificates Selected, you can enter
Domain Identity
Anonymous Identity
Password
Transfr Provided - Quest 2 Specifications
Product Dimensions: 191.5 mm x 102 mm x 142.5 mm (strap folded in), 191.5 mm x102 mm x 295.5 mm (strap fully opened up)
Product Weight: 503g
Tracking: Supports 6 degrees of freedom head and hand tracking through integrated Oculus Insight technology
Storage: 256GB
Storage: 256GBDisplay Panel: Fast-switch LCD
Display Resolution: 1832×1920 per eye
Display Refresh: 72Hz at launch; 90Hz support to come
SoC: Qualcomm® Snapdragon™ XR2 Platform
Audio: Integrated speakers and microphone; also compatible with 3.5mm headphones
RAM: 6GB
Battery Life: You can expect between 2-3 hours of use with Transfr simulations on the Quest 2 headset. At any point, you can check the battery status of your headset on the navigation bar inside the headset. The battery status is located just below the clock on the left side of the navigation bar. This will also show you the battery status of the hand controllers.
Charge Time: With the provided USB-C power adapter, Quest 2 will charge to a full battery in about 2.5 hours
IPD: Adjustable IPD (interpupillary distance) with three settings for 58, 63, and 68mm
Playspace: Stationary or Roomscale supported. Roomscale requires a minimum of 6.5 feet x 6.5 feet of obstruction-free floor space
Controllers:
Dimensions: 9 x 12 cm(per controller, includes tracking ring)
Weight: 126 g (per controller, no battery installed)
Requires 2 AA batteries (included in the box; 1 for each controller)
Transfr Provided - Quest 2 Specifications
Wi-Fi b/g/n/ac(5)/ax(6)
60 GHz Wi-
Fi ay module (currently not in use)
Bluetooth 5.0 LE
Type-C USB port, with USB Host support
3.5mm audio jack.