Valarea
Search…
⌃K

Network Requirements

Please consult your IT department before installing Valarea Rooms as certain blocks may need to be lifted. We also recommend using a wired LAN connection
Network Security
Generally, Valarea Room has the same network requirements as any PC running video conferencing applications like Microsoft Teams, Zoom, Cisco Webex, Google Meet. Specific to Valarea Room, the categories listed as "required" for the video conferencing systems must be open on your firewall. Valarea Room also needs access to Windows Update and Microsoft Intune (if you use Microsoft Intune to manage your devices). For the full list of IPs and URLs required for Valarea Room, see:
We highly recommend that you configure the Valarea Room PC to automatically keep up to date with the latest Windows updates, including security updates. Set an operating system update policy to install all pending updates every day starting at 2:00 am using a pre-set local policy.
Valarea Room devices do not need to connect to an internal LAN. Consider placing the Valarea Room in a secure network segment with direct Internet access. If your internal LAN is compromised, the vector's opportunities to attack the Valarea Room will be reduced.
We strongly recommend that you connect your Valarea Room devices to a wired network. The use of wireless networks on Valarea Room devices isn't recommended. Some connectivity features, such as Wi-Fi Sense, are disabled by default.
Bluetooth Proximity for Personal Calendar, Cloud Drives, Valarea Cast (via 4G)
The Proximity Join feature for the personal calendar / personal cloud storages (e.g. OneDrive) is based on Bluetooth. The use of Bluetooth technology on Valarea Room devices is currently limited to advertising beacons and required proximal connections. The ADV_NONCONN_INT protocol data unit (PDU) type is used in the advertising beacon. This type of PDU is for non-connectable devices that advertise information about the listening device. There is no pairing of Bluetooth devices as part of these features. Further details on Bluetooth protocols are available on the Bluetooth SIG website.

Allowlisting and Firewall Configuration

For remote connections, Valarea Room and Valarea clients must be able to access the Internet through these ports:

Internet Services and Ports

HTTP: 80 (TCP)
HTTPS: 443 (TCP)
DNS: 53 TCP/UDP out to DNS (internal or external)
NTP: 123 UDP out to NTP (internal or external)

FQDNs to be Allowed

Valarea / Re Mago services

admin.valarea.com
app.valarea.com
arcrop.valarea.com
chat1.valarea.com
meet1.valarea.com
oauth-apple.valarea.com
oauth-google.valarea.com
oauth-msft.valarea.com
oauth-webex.valarea.com
oauth-zoom.valarea.com
pmc.valarea.com
prd-rms.valarea.com
rms.valarea.com
r.valarea.com
globalchat1.azurewebsites.net
rgo.li
api.remago.com
license.remago.com
webrtc.valarea.com (see "Optional Built-in WebRTC VC System" below for ports)

3rd-party services

graph.microsoft.com
inputtols.google.com
googleapis.com
autodraw.com
dropbox.com
activation.airserver.com
eu.docusign.net
account.docusign.com

Internal Port Requirements for Valarea Wireless Touch Controller

Valarea Room Discovery service: 8035 UDP
Valarea Room Communication service: 8034 TCP
Wireless Display Protocols
Network settings to enable support for Miracast™, GoogleCast™ and Apple Airplay™

Optional Built-in WebRTC VC System:

Host: webrtc.valarea.com
General: 80, 443, 5349 TCP
Stun: 3478 UDP
Media Traffic: 10000 UDP

Bandwidth Requirements

Minimum bandwidth: 2 Mbps.
When using third-party video conferencing applications, more bandwidth will be required. Users should refer to the guidelines recommended by each application developer.