CCTV Compatibility Checklist: IP Cameras, NVRs, ONVIF and RTSP Explained

This CCTV compatibility checklist helps you collect the facts needed before connecting existing cameras to AI video analytics. The terminology can sound complicated, but the practical questions are straightforward: where does the video come from, can an authorised system access it, is the picture suitable and can the network carry it securely?

Complete the checklist with your installer, IT provider or site administrator. Do not change recorder settings or share passwords casually. A clean inventory saves time, protects the current recording setup and makes any proposed upgrade easier to price accurately.

1. Identify every camera type

Record the manufacturer, exact model, firmware version, location and connection type for each camera family. An IP camera creates digital video and connects to a network, often through Ethernet or Wi-Fi. PoE, or Power over Ethernet, allows a compatible switch or injector to provide data and power on one cable. PoE is convenient, but it does not by itself confirm stream compatibility.

Analogue cameras send a signal to a DVR, which digitises and records it. Their ability to participate in a modern integration usually depends on what the DVR can output. Consumer cloud cameras may be digital yet remain closed to third-party systems, so never assume that “wireless” or “app connected” means an accessible local stream.

2. Understand the recorder

An NVR, or network video recorder, receives video from IP cameras. A DVR typically handles analogue inputs, although hybrid recorders can accept more than one type. Record the model, channel count, current camera connections, storage arrangement and software version. Confirm whether the manufacturer still supports the unit.

Ask whether the recorder can provide individual camera streams to an authorised external platform. Some cameras sit on a private network behind the NVR and cannot be reached directly; in that case, the recorder's available interfaces become important. Export and backup current settings before any authorised configuration work.

3. Check ONVIF support

ONVIF is an industry framework that helps compatible physical-security products work together. Depending on the profiles implemented by both devices, it can support discovery, media configuration and other functions. A product displaying an ONVIF claim is not a guarantee that every feature will interoperate. Confirm the specific model, firmware and supported profile, then test the intended workflow.

Enable only the services needed and create a dedicated integration account where the system permits it. Keep credentials out of spreadsheets or email chains. If ONVIF is unavailable, a usable direct stream may still exist, so continue to the next check.

4. Check RTSP video streams

RTSP is commonly used to request and control a live network video stream. Cameras and recorders may offer a main stream plus lower-bandwidth substreams. Record the supported codecs, resolutions, frame rates and bitrate modes. H.264 and H.265 are common, but support must be confirmed at both ends of the integration.

Test stability over time, not just whether a player opens the stream once. Avoid exposing an RTSP address directly to the public internet. Use secure network design, access controls and approved connectivity. Surnexo's camera compatibility page provides a useful starting point for the model-level review.

5. Review scene quality

For every priority view, capture examples in daytime, at night and during typical movement. Check focus, lighting, subject size, angle, weather exposure and obstructions. Write down the exact event the view should support. A technically accessible stream may still be unsuitable if a person appears too small or bright headlights overwhelm the image.

6. Record network and security details

• Camera and recorder network segments, without publishing sensitive addresses.
• Available upload and internal network capacity during busy periods.
• Firewall, remote-access and account-management responsibilities.
• Supported firmware status and a process for applying updates.
• Who can view, administer and export video.
• Retention, privacy and incident-handling requirements.

The number of streams, codec, resolution, bitrate and analysis location all affect network demand. A site-based processing design behaves differently from one that sends selected streams elsewhere. Measure and plan instead of using a generic bandwidth assumption.

7. Validate with a small test

Choose representative cameras, connect them without disrupting existing recording and validate a clearly defined event. Monitor stream uptime, alert relevance and staff response. Document any changes to camera settings or network rules. The Surnexo how-it-works guide shows how discovery, connection and alert use form one practical workflow.

Your handover pack

Finish with an inventory, site map, camera purpose, sample footage, approved contacts and a list of constraints. Mark unknown items rather than guessing. This pack allows a provider to distinguish cameras that are ready, cameras that need adjustment and equipment that may require selective replacement.

Once your checklist is ready, request a demo and ask for a quote for the priority areas. A grounded compatibility review will help you protect useful equipment, avoid surprise integration work and create a supportable path to AI-assisted monitoring.