The Access panel describes how CAMNET server is to access the camera. The Camera stream URI is used for Live view streams sent to the client and for recording. The Camera snapshot URI is used for the camView shot (the small view next to each cambox button, along the sides of the Camnet Service Manager client).
Only one connection to the camera is made by CAMNET server, even if recording and live viewing (or viewing the in-progress recording) at the same time, no matter how many clients are watching.
The available Comm modes varies based on Camera make/model. Some cameras have only one Comm mode available, while other have several. Some specially-supported make/models have a Comm mode that is only available to that make/model. If you don't know which Comm mode to use, go with the first one listed to start.
After selecting the Comm mode, the URIs can be selected. Not all URIs necessarily make sense for a given comm mode. Where confusion may occur, each URI is prefixed by its intended Comm mode use. For example, there can be multiple comm modes for RTSP streams:COMM_RTSP_OVER_HTTP COMM_RTSP_OVER_TCP COMM_RTSP_OVER_UDPeach of those could specify any of the following Camera stream URI (this is an Axis/AXIS_V5 camera):[RTSP]/axis-media/media.amp?videocodec=h264 [RTSP]/axis-media/media.amp?videocodec=mpeg4 [RTSP]/axis-media/media.amp?videocodec=jpeg [RTSP]/mpeg4/media.ampalso listed with these URIs is[JPEG]/axis-cgi/mjpg/video.cgiwhich is not applicable to the COMM_RTSP_OVER_* comm modes, even though it is listed with the others URIs. It is instead intended forCOMM_JPEG_STREAMThe [RTSP] and [JPEG] prefixes are not used by CAMNET server; the [prefixes] are removed before use. For some URIs, for example, presets, the [prefix] is used to name the button at the client for that preset. The [prefix] can be edited, or removed.
For Audio, if you want audio then set this to yes. If you don't want audio, set this to no. For RTSP cameras, setting this to no instructs the camera to not send audio at all. For some cameras, the audio is still sent, but CAMNET server will throw it away.Video: Video remains no until you Test-Join the camera, where it is automatically changed to yes; Test-Join is the last panel of Cam setup.
Audio: Be aware of odd, RTSP cameras that report audio being available but then never send audio. This causes the video system (Windows Media Foundation) to become unresponsive while it waits for audio to arrive, which never does. CAMNET server detects this eventually, but it can take several seconds; depending on the frame rate (FPS) this can be longer than you would want to wait. One camera known to report audio being available (via its SDP report) is Dahua/DAHUA_IPC1 (that includes rebrands such as Q-See, Swann, and others). For a Dahua/DAHUA_IPC1 camera that you know does not support audio output, be sure to set Audio to no.
For cameras on the local network, which should almost-always be the case, it's recommended to use basic as the Camera authentication setting. Remote clients never directly access the camera, instead remote clients go through CAMNET server for streaming, and for controlling the camera. Also, HTTPS (SSL from CAMNET server to the camera) is not necessary -- the camera is local to CAMNET server so there is no one that can intercept the data.
CAMNET server and its clients connect over an SSL channel (TLS 1.x) by default. This connection is further encrypted, just in case some bad guy has broken your SSL, with a one-time encryption key exchanged using the Secure Remote Password (SRP) prototcol. With SRP there is no possibility of a man-in-the-middle attack even with a self-signed certificate. This is performed for each client log on to the CAMNET server, which happens very often when interacting with CAMNET server. However, if you connect from the client to CAMNET server at 127.0.0.1, an SSL channel is not used, and no further encryption is done to the data transmitted; if your own machine is not secure those measures would not help. You may connect using a LAN address other than the local loop, but generally, to reduce CPU needs when the crypto is simply not necessary -- when CAMNET server and the client are on the same machine -- 127.0.0.1 would be better.