The short answer
Start with verified local access at each site, then evaluate authorized private routes. Keep network design separate from AeoCam cloud viewing, which is not currently offered.
Work through the checks
Identify the camera by model, hardware revision, firmware and MAC address. Keep this inventory separate from passwords; two devices with similar names may expose different protocols.
Test one camera and one stream before opening a larger camera wall. Keep the camera settings unchanged while you establish whether the first live image is stable.
For a routed private connection, verify the VPN route to the camera subnet and its access rules. A private route is separate from any AeoCam cloud service; public port forwarding is not required for this check.
Match the requested channel or lens to the manufacturer’s numbering. A valid stream from the wrong channel can look like success while showing another camera.
What to verify
Show a visible changing clock or a supervised movement in the camera scene, then compare it with the live image. Use the same source and layout for each latency comparison.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.