Configuring Firewall Rules on Remote Network for Direct SureView applications

This article provides basic steps to configure a commercial off-the-shelf (COTS) router for remote access to multiple SightSensors.  The example provided is one of several possible strategies. This is the simplest way for clarity. 

It is assumed that you are using WebConfig to configure your SightSensors.


Monitoring companies may be required to install SightSensors in locations where there is limited network infrastructure or there are un-managed network switches. In these cases the router on site can be configured to allow video, alarms and web-based access to the equipment.

Application Notes

  • SightSensor is an IP appliance
  • RTSP video is presented on port 554 for all SightSensors. This port is not configurable on the SightSensor and if there are multiple sensors installed at a particular site each sensor must have the RTSP port forwarded from another available port
  • Each SightSensor has a web interface that can be accessed using a browser and port 80. If multiple SightSensors are installed and remote access is required these SightSensors  must also have port 80 forwarded from another available port
  • Alarm integration with SureView requires the SightSensor to provide an alarm with pre/post video attached on a specified port. This port is configurable within the SureView server with the default being 9006. The port must be open from the physical site where the SightSensor is installed (outbound) to the Immix server site (inbound)

In the example below there are two SightSensors onsite connected to a cellular modem. The ports used for WebConfig, RTSP video, and alarms were forwarded from outside to each unit, using available unused ports.