The short answer
A persistent 401 points to authentication, but an initial challenge can be normal. Verify the local protocol account, encoded credentials and lockout state before repeated retries.
Work through the checks
Use the camera’s local protocol account. A cloud app email address is not necessarily a valid RTSP or ONVIF login. Grant only the viewing or control permissions actually needed.
Enter credentials in separate app fields when available. For a URL that must contain credentials, encode reserved characters only in the user/password components; never encode the complete RTSP URL.
Stop repeated failed logins and check the camera’s account lockout policy. Verify the local account in the manufacturer interface before trying again with one client.
Check the model manual for an ONVIF service switch and any separate ONVIF account. Use the configured service port; do not assume it equals the RTSP port.
What to verify
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.
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.