Skip to content
English
  • There are no suggestions because the search field is empty.

Alocity AiVR Network Requirements

How to Ensure Your Device is Connected and Operating Efficiently

To ensure that your Alocity AiVR system operates smoothly and delivers reliable video performance, it’s important to meet the following network and camera setup requirements. This guide outlines what you need to prepare for optimal functionality.

1. Network Connection
The AiVR must be connected to the network using a wired gigabit Ethernet connection.

  • DHCP is required. Do not configure a static IP on the AiVR: it has no local screen or keyboard, so an address that doesn’t work leaves it offline until it’s recovered on site.
  • To keep the same address, create a DHCP reservation for the AiVR’s MAC address. The DHCP server must provide a working gateway and DNS.
  • The AiVR must be on the same network or VLAN as all of its IP cameras. Camera discovery only works within one VLAN unless multicast is routed.
  • Avoid isolated VLANs or guest networks unless properly routed.

2. Firewall Settings
All cloud connections are outbound and started by the AiVR. No inbound connections, port forwarding or public IP are needed. Allow the following outbound ports on both local and upstream firewalls.

IMPORTANT: Do not apply SSL/TLS inspection or DNS filtering to the AiVR’s traffic. Its cloud connections use certificate-based authentication.

Internet (Outbound from AiVR):

  • TCP Port 443 – Cloud video storage (backup and playback), remote access, software and AI model updates, error reporting
  • TCP Port 8883 – Secure connection to the Alocity cloud (device management, status and commands via MQTT over TLS)
  • TCP Port 8554 – Remote live view streaming to the Alocity cloud video server
  • UDP Port 3478, TCP Port 80 – Remote playback relay (STUN/TURN)
  • TCP Port 5349 – Remote playback relay (TURN over TLS)
  • UDP Port 123 – Time synchronization (NTP; required for secure TLS connections)
  • UDP / TCP Port 53 – Domain name resolution (DNS)
  • UDP Ports 1024–65535 (Optional) – Direct remote playback connections (relay is used if blocked)

Local Network:

  • TCP Port 554 (or camera’s RTSP port) – Video streams from cameras (AiVR → cameras)
  • TCP Port 80 (or camera’s ONVIF port, e.g., 8000 / 8080) – Camera setup and control (AiVR → cameras)
  • UDP Port 3702 to Multicast 239.255.255.250 – Camera discovery via WS-Discovery
  • ICMP (Ping) – Camera reachability checks (AiVR → cameras)
  • UDP Ports 67 / 68 – Automatic IP address assignment (AiVR ↔ DHCP server)
  • TCP Port 445 (Optional) – Network storage / SMB (AiVR → NAS)
  • TCP Port 5000 (Optional) – Direct local video playback (Local users → AiVR)
  • TCP Port 8888 (Optional) – Direct local live view (Local users → AiVR)

Never expose the AiVR’s local ports to the internet. Other ports open on the AiVR (8554, 9996, 9997, 1935, 8890, 8000–8001) are internal and don’t need to be reachable from other machines.


3. Camera Requirements

  • Fixed IP address on every camera (DHCP reservation or static IP on the camera). If a camera’s address changes, notify Alocity support.
  • RTSP enabled, and ONVIF enabled with an ONVIF user account
  • Camera clock set by NTP, and firmware up to date

4. Recommended Internet Speed for AiVR
The AiVR continuously backs up video to the cloud while supporting remote viewing of 6 to 200 camera streams, depending on model.

  • Upload Speed: at least the sum of all camera average bitrates plus 20%. For example, 10 cameras at 4 Mbps need about 48 Mbps.
  • Download Speed: light; occasional software updates of several hundred MB to a few GB
  • Recommended Jitter: Less than 30 ms
  • Recommended Latency: Under 50 ms

With less upload, video still records locally but cloud backup falls behind. Higher bandwidth may be required for higher camera counts, higher resolutions or multi-site deployments.


5. Network Testing Recommendations

  • Measure Jitter: Ensure jitter remains under 30 ms to avoid video instability
  • Inspect Wiring: Use high-quality Cat5e or Cat6 cabling, and check for physical damage or weak terminations
  • Verify DNS: Run nslookup on a public name from the AiVR’s VLAN before leaving site
  • Test Remote Live View: If remote live view fails while local view works, outbound TCP 8554 is blocked or TLS inspection is on
  • Direct Connection Testing: During troubleshooting, temporarily connect the AiVR directly to the main router to validate connection quality

Following these network and camera requirements will ensure consistent, high-quality video capture and cloud communication for your Alocity AiVR.