The Connections panel shows active connections between CAMNET server and cameras, and active connections between CAMNET server and clients. It also shows any active event servers running at CAMNET server.
The CAMNET server that is queried is the active (based on the LAN/WAN setting) server specified in the Server name panel.
If a camera does not directly supply event meta-data (motion detect, etc.) in the video stream (EBNT_FAMID) you can often configure the camera to send either an HTTP signal, a TCP signal, or an FTP upload (the upload contents are not used) to signal the event. CAMNET server uses this signal to index and mark the event for quick and direct recording access in the future, or if recording by event only, to start recording. This event record is maintained in the recording file. Additionally, CAMNET server can process Onvif event data. CAMNET supports hybrid Onvif use, where, for example, a camera can be set up as a specific make/mode (e.g., a Hikvision) and still use Onvif for event processing (see Cam setup, Info panel, the Event by network type field value: EBNT_ONVIF).
The HTTP event server (es_http) is always active. It is used to handle not only incoming event signals from cameras, but to also handle incoming HTTP triggers (you can use a standard HTTP GET to trigger a particular camera, or to trigger all cameras).Access to the HTTP event server does not require an already-registered IP address. A camera has a registered IP address so long as it is connected to the CAMNET server. If the HTTP event originates from a source that has not registered (i.e., not a connected camera), its IP address is further checked using the server ACL, and processed or rejected based on that.
The TCP, FTP, and Onvif event servers are active only if a camera that uses one of those for event processing was previously started by the CAMNET server. Their signals (TCP, FTP, and Onvif) are processed by the event servers only if the camera is still connected to CAMNET server.