Skip to main content

Network Requirements

It’s essential to configure your collector device properly for seamless communication within your LAN and beyond. Let’s break down the network requirements for the collector device:

  1. Collector Deployment Considerations:

    • The collector device must have a local/internal static IP address, which ensures consistent communication.
    • Provide the local subnet and gateway also to allow traffic flow.

  2. Collector Functionality:

    • The collector reads, decodes, and processes data within the care home.
    • All routing logic occurs within the collector, and it uses a local socket connection to relay alerts to mobile devices.

  3. Over-the-Air Updates and Remote Access:

    • To maintain an ever-evolving product and provide efficient support, over-the-air updates are pushed to the collector device.
    • Our technical team requires secure full remote access to manage and troubleshoot the collector.

  4. Outbound WAN Rules (Collector Connecting to the Internet):

    • In general we recommend allowing all traffic outbound for the collector, however the following ports at minimum must be opened for outbound communication:
      • Port 51820 (TCP/UDP): Used by WireGuard VPN.
      • Port 53: DNS
      • Port 80: API calls to our platform
      • Port 443: API calls to our platform.
      • Port 5050: Downloading Docker updates
  5. Inbound WAN Rules (Internet sources connecting to the collector)
    • We do not require any inbound rules or communication to the unit, it should not be internet accessible. Instead, our unit opens a wireguard tunnel outbound to us and we do all communication over this tunnel.

  6. Internal LAN Rules (Handsets Accessing the Collector):

    • Handsets using the mobile app should have unrestricted access via the LAN to the collector on the following ports:
      • Port 80 (TCP): HTTP for local communication.
      • Port 5557 (TCP): Local app socket communication
      • Port 5559 (TCP): Local app socket communication
      • Port 8083 (TCP): Local app socket communication

There are some ranges used for internal communication within the collector, and for communication to the Wireguard network we operate. You must avoid using the following ranges:

  1. Onsite Config Network:

    • Network Range: 192.168.150.0/24
    • Purpose: Used for onsite configuration. (Engineer Use Only)
    • Ensure that other devices or networks do not overlap with this range.

  2. Wireguard VPN Network: Creates a tunnel between the cloud site and local collector.

    • Network Range: 10.8.0.0/22
    • Purpose: Used for Wireguard VPN connections via the local collector to the cloud servers, transports all nursecall data to cloud and allows management to the local collector and assets with OTA upgrades & system patching.
    • Prevent any IP address conflicts with this range.

  3. Docker Network:

    • Network Range: 172.17.0.0/16
    • Purpose: Used by Docker containers.
    • Be cautious not to use IP addresses within this range elsewhere.

By default all traffic that is not destined for the local network of the collector is routed via the wireguard tunnel. This means if you operate your handsets on a different network range or if you operate multiple ranges you will see some handsets fail to communicate with the collector. In this instance please provide the following information to our support team and we will be able to add the necessary routes to our collector

  • IP Range
  • Subnet Mask
  • Gateway IP (must be within the local subnet the collector communicates using)

Back to top