Read the camera configuration before constructing an address
The cited firmware manual describes an access name for each of streams 1 through 4. That name is part of the address, not a description you can freely change in the viewer. If an installer renamed a stream, an address copied from a different installation may authenticate successfully but still request a resource that does not exist.
Record the exact model, installed firmware, RTSP port, available encoder names and selected video compression. A recorder manual may instead describe channels and main/substream numbers. Do not apply that recorder syntax to a standalone camera simply because both devices carry the ACTi name.
Connect the documented encoder to SmartRTSP
- Locate the camera address in the router or the installer’s device inventory. Put the SmartRTSP device on a network that can reach that address.
- Sign in to the camera web configuration with an authorized local account and open the RTSP or streaming settings described in that model’s manual.
- Copy the configured RTSP port and the access name for the desired encoder. Check that the encoder is enabled and note whether it sends H.264, H.265 or another format.
- Create or select a viewing account permitted to receive the stream. Enter the actual local credentials in SmartRTSP; do not substitute a cloud account or another camera’s password.
- Add the documented address through manual camera entry. Confirm a moving live picture, then test reconnection and any additional stream you intend to use.
rtsp://<camera-ip>:<configured-rtsp-port>/<configured-access-name>Choose a stream that fits the display
A high-resolution primary encoder may be useful for a full-screen view, while a smaller enabled encoder can reduce decoding and network work in a camera grid. Verify that those encoders actually exist on this model before building addresses for them.
Change one camera setting at a time and keep a note of the previous configuration. Other recording systems may already depend on the encoder you are editing. A codec or resolution adjustment can affect those systems even when the RTSP access name stays the same.
Separate authentication, transport and feature problems
| Symptom | Next check |
|---|---|
| Unauthorized response | Verify the local camera account, password and stream permissions. |
| Address accepted but no video | Recheck the exact access name, enabled encoder and compression format. |
| Intermittent picture | Try a lower-bandwidth enabled stream and check the local connection. |
| Video works but another function does not | Check that function separately; an RTSP picture does not establish ONVIF, PTZ or two-way audio support. |
Check each feature independently
Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.
Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.
Frequently Asked Questions
Is liveview.1 a universal ACTi stream name?
No. It is an example in the cited manual. Use the name currently configured for the encoder on your camera.
Can I use an ACTi NVR channel address for the camera?
Not automatically. Camera access names and recorder channel syntax describe different endpoints. Use the manual for the device whose IP address you are connecting to.
Has this guide certified my ACTi model?
No. Documentation was checked on 2026-10-18. Confirm the exact model, firmware, video format and required functions on your own local setup.
Official sources and scope
Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.