Corporate network firewalls may need additional configuration to allow for XMReality traffic.
For XMReality to work, connectivity is needed between the device making a call and both XMReality servers and the call recipient. Many corporate IT environments allow for all outgoing network traffic, in which case no additional configuration is required. But if the IT environment blocks certain network traffic types, additional configuration of the network firewalls may be required.
To ensure that XMReality performs well, it is important to validate that XMReality calls can use UDP traffic. TCP based connectivity is a fallback solution supported, but it comes with a reduced quality of experience with lower video and audio quality as well as additional latency.
Network traffic required
|Any||UDP||1024-65535||Direct video and audio call connections||Highly recommended.|
|TCP||443||XMReality web applications and server connectivity||Mandatory|
|TCP||443||STUN and TURN connectivity to relay calls blocked by NAT or firewalls||Mandatory|
|UDP||3478||TURN connectivity to relay calls blocked by NAT or firewalls||Highly recommended|
|[Conference server]||UDP||1024-65535||Video and audio connectivity for multi-party calls||Highly recommended for multi-party calls|
|TCP||3478, 20000-65535||Mandatory for multi-party calls|
In addition to the above, XMReality also uses standard push notifications from Apple and Google.