Event servers
For cameras other than Axis, the methods will differ from what is shown here, but the concept should be the same.

[ camnet event servers, sample tcp setup ]
After setting up the event server to point to CAMNET server's TCP port, set the event(s) that are to send notifications to CAMNET server's TCP event server. Create event types, as needed.

For the browser's [ Test ] to succeed, the TCP event server must be running at CAMNET server. It will be running only if there is now, or has been since CAMNET server started, an active camera that uses EBNT_TCP for Event by network type. The System, Connections panel, Camera list shows the running event servers, such as The value after :c is the number of connections the HTTP event server has accepted.

[ camnet event servers, sample tcp setup ]

For Message, the following are recognized. If nothing is recognized, MD window 1 (same as MD_0) is used.

      MD_0 to MD_9   : motion window, starting at 0  (motion window 1 to 8 in logs) [MD_8 and MD_9 report same as MD_7]
      MD_            : motion window 1 [same as MD_0]
      AUD_           : audio  (A in logs) [it must include the trailing underscore]
      PIR_           : PIR/sensor  (P in logs)
      EXT1_          : extension event1  (little-x in logs)
      EXT2_          : extension event2  (big-X in logs)          [do not use %5F for the underscore]
      I0_            : digital input 0
      I1_            : digital input 1
      I2_            : digital input 2
      I3_            : digital input 3   (big-X in logs; it shares the same notification bit as EXT2_)
AXIS_V4 cameras are set up slightly different, but the concepts shown here are similar.