Technical Information

Technical Information for eDispatches Equipment

General

  • Linux-based

  • No keyboard, mouse or monitor needed

  • Automatic recovery following power failure/restoration

  • Dimensions and weight

    • 9.17” x 8.17” x 2.52”, approx 3 lb. (detector)

    • 6 ½” x 5 ¼” x 1 ¾”, approx 1 lb. (scanner)

Requirements

  • 115V power (2 outlets)

  • High-speed internet (1 port) - Ethernet only / no WiFi (due to reliability concerns)

  • Clear radio reception for scanner (direct audio connection to dispatch console or base radio may be possible via 3.5mm stereo jack)


Bandwidth Usage

  • Routine Check-ins: Approx. 2KB transferred every 10 minutes

  • Sending Alerts: Less than 500KB per alert (transfer of recorded audio)

  • Streaming Audio: 20 - 30 kbps (continuous)


IP Address Assignment

  • DHCP preferred

  • Static IP is possible, prior to shipment the customer must provide:

  • IP address (typically 192.168.x.x, 10.x.x.x or 172.x.x.x)

    • Netmask

    • Default gateway

    • DNS addresses

    • NTP server address (if local ntp server exists)


Protocol Usage
The equipment must be able to use the standard provisions of the following protocols to make OUTBOUND connections as a CLIENT:

  • ssh (destination port 22, TCP)

  • http (destination port 80, TCP & UDP)

  • https (destination port 443, TCP)

  • ntp (destination port 123, UDP)

The equipment must be able to use the above protocols to initiate outbound connections to remote servers and receive the return traffic from those servers.  The equipment runs an ssh daemon listening on it’s own local port 22 for potential troubleshooting from the LAN, but it does not need port 22 opened or forwarded at the firewall.  No additional protocols / ports need to be enabled, opened or forwarded on the firewall.

Destination IP Addresses (subject to change without notice)




 

Attachments

Technical___Networking_Details_for_eDispatches_Equipment_-_Google_Docs.pdf Technical___Networking_Details_for_eDispatches_Equipment_-_Google_Docs.pdf

Did you find this article helpful?