An integrated tracking system has multiple cameras
The manufacturer describes Intelligent Tracking System 2.0 using an IPC2855-Fi5N bullet camera and an IPC445-i033-N PTZ camera. The bullet camera provides a scene view while the system can coordinate PTZ tracking. These are distinct video sources, not interchangeable stream names for one lens.
That specification lists RTSP and ONVIF profiles for the described equipment. It does not establish support for every KEDACOM conferencing endpoint, encoder or recorder. Select the manual that matches the full IPC model and installed firmware before configuring local viewing.
Obtain a URI rather than guessing a brand-wide path
The cited public specification confirms protocols but does not provide a universal KEDACOM RTSP address. This page therefore does not invent a path or port. Use the camera manual, its configured network-video settings, or the stream URI returned by supported ONVIF discovery.
If a recorder manages the camera on a private camera network, the recorder address and channel may be the reachable source instead. A camera IP shown inside the recorder is not necessarily reachable from the device running SmartRTSP. Identify the intended endpoint before changing credentials or network routes.
Prepare the individual camera stream
- Record the complete IPC or recorder model, firmware and whether the desired view is the fixed camera or tracking PTZ camera.
- Download the matching user manual from KEDACOM and confirm the local RTSP or ONVIF capability.
- Connect through the documented local network interface and configure a unique device account with viewing permission.
- Check stream enablement, the actual service ports and the selected video profile in the device configuration.
- Use a documented URI or discover a supported ONVIF profile and retain the URI that the device returns.
- Add the reachable source in SmartRTSP and verify that it shows the expected lens, image orientation and sustained video.
Check encoding and tracking as separate functions
The example system specification distinguishes high-resolution main video from a smaller secondary stream and lists H.264 and H.265 encoding. Use the profiles actually offered by your device. A secondary profile can reduce viewing bandwidth, but its image may not be suitable for identifying distant details.
Linked tracking, alarm rules and PTZ coordination belong to the integrated system. Receiving one RTSP feed does not reproduce those functions in a viewer. For a failed connection, check endpoint reachability, account permissions and the exact returned URI before modifying tracking configuration. Avoid exposing the camera management interface or streaming ports publicly for a local viewing test.
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
What is the universal KEDACOM RTSP URL?
No universal URL is established by the sources used here. Obtain the URI for the exact camera, recorder channel and firmware.
Will the fixed camera feed show the PTZ tracking view?
Not necessarily. The example tracking system has separate fixed and PTZ cameras. Select the source that contains the view you need.
Does an ONVIF specification prove all viewer functions work?
No. Discovery, video profiles, authentication, PTZ and alarms are separate compatibility checks. This guide has not independently tested the physical devices.
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.