Will Camera Brand X Work on NVR Brand Y? ONVIF Compatibility Matrix for Indian CCTV Brands
As of 14 Oct 2026, ONVIF's conformant-products database lists all 78 Hikvision client entries dated since Oct 2023 as Profile S and T, but none of Uniview's 266 client entries as Profile T. Profile T obliges a client to decode H.265 and receive motion events. T on both sides puts a pair in scope; it does not prove it works.
Last checked: 14 Oct 2026.
This page covers camera brand × NVR brand pairs. The ONVIF/RTSP matrix tool covers one camera model at a time and has no NVR side; here its camera data is crossed with seven NVR brands' client listings.
Verified against
- ONVIF conformant products database, all client listings of Aditya Infotech (CP Plus), Prama India, Matrix Comsec, Samriddhi Automations (Sparsh), Hikvision, Dahua and Uniview, via its search API, 14 Oct 2026. Rows: /static/data/cctv-camera-nvr-compatibility-matrix-onvif.csv.
- Camera side: 196 STQC-certified models matched to exact ONVIF listings (same data as the ONVIF/RTSP matrix tool, checked 7 Oct 2026).
- ONVIF conformance process; Profile S v1.3; Profile T v1.0; Profile M; Profile S end of support, 9 Oct 2025.
- Hikvision ONVIF add-camera how-to and NVR manual V4.1.70 (2018, distributor-hosted); CP Plus NVR manual (PDF of Jul 2026); Matrix ONVIF add-camera guide V1R1 (2020); Prama third-party camera guide (Jun 2024); Uniview third-party camera guide.
What each NVR brand passed as an ONVIF client
An NVR that adds other brands' cameras acts as an ONVIF client. Its client listing names the profiles it passed in ONVIF's Client Test Tool; it is not a test against any particular camera brand.
| NVR brand (ONVIF company) | Client listings (all / since 14 Oct 2023) | Client profiles in the newest listings | Newest test date | Source |
|---|---|---|---|---|
| Hikvision | 1,717 / 78 | All 78 recent: S + T; 7 also M (e.g. iDS-7732NXI-M4/X) | 10 Oct 2026 | ONVIF DB |
| Prama | 25 / 2 | S + T (PT-NRAS2E16-K8, PT-NRAS2E32-K8); 23 of 25 ever are S + T | 5 Aug 2026 | ONVIF DB |
| CP Plus (Aditya Infotech) | 42 / 2 | G + S, no T (CP-UNR-408T2J-BI, -416T2J-BI); seven 2021–22 were G + S + T | 4 Jan 2026 | ONVIF DB |
| Matrix SATATYA | 39 / 22 | G + S + T on six "P2" NVRs (Aug 2025 – Jun 2026); 12 NVRs dated May 2024 are S only | 23 Jun 2026 | ONVIF DB |
| Sparsh (Samriddhi) | 24 / 9 | S or G + S, no T since 2023. 14 listings of 2020–21 were G + S + T | 2 Sep 2026 | ONVIF DB |
| Uniview | 266 / 61 | S only; 0 of 266 client listings include T | 23 Sep 2025 | ONVIF DB |
| Dahua | 13 / 4 | NVR clients: only DH-NVR32XX–60XX, S, 14 Mar 2013. Since 2023: 3 DSS software (G + M + S + T), 1 CyberCity VMS (G + S) | 9 Apr 2026 | ONVIF DB |
Dahua's 1,148 "Recorder" listings are device conformance, not proof the recorder accepts other cameras. A Dahua NVR client listing newer than 2013 was not found in the ONVIF database (checked 14 Oct 2026).
Camera brand × NVR brand: what conformance covers on both sides
Rows are STQC-certified camera models (196 in our dataset). Each cell counts the models whose own ONVIF listing reaches the level shown, against that NVR brand's newest client listings. S + T means each side separately passed Profile T, so H.265 decoding and motion events are in scope. No cell means the pair was tested together or is guaranteed to work.
| Camera brand (STQC models) | Hikvision NVR/VMS, since 2023 (client S+T) | Prama NVR, 2026 (client S+T) | Matrix P2 NVR (client G+S+T; Matrix asks camera S+G) | CP Plus NVR, 2026 (client G+S, no T) | Sparsh NVR, 2023–26 (client S or G+S) | Uniview NVR (client S) |
|---|---|---|---|---|---|---|
| CP Plus (45) | S+T: 34 | S+T: 34 | S+G+T: 20; S+T without G: 14 | native protocol | S: 34 | S: 34 |
| Prama (58) | S+T: 56 | native protocol | S+G+T: 43; S+T without G: 13 | S: 56 | S: 56 | S: 56 |
| Matrix (36) | S+T: 26 | S+T: 26 | native protocol | S: 26 | S: 26 | S: 26 |
| Sparsh (43) | S+T: 35 | S+T: 35 | S+G+T: 35 | S: 35 | native protocol | S: 35 |
| Honeywell (9) | S+T: 7 | S+T: 7 | S+G+T: 7 | S: 7 | S: 7 | S: 7 |
"Native protocol": same-brand pairs can use the vendor protocol instead of ONVIF. Not in the grid: Vicon (3 models, all S + G + T + M listed) and EQUUS (2 models, 1 listed, S only). Models without an exact listing (11 CP Plus, 10 Matrix, 8 Sparsh, 2 Prama, 2 Honeywell, 1 EQUUS) may still stream over ONVIF or RTSP; that is a datasheet claim, not a conformance listing.
What "S" vs "S + T" means for H.265, events, PTZ and AI
| Feature | Profile S client (video baseline) | Profile T client | Source |
|---|---|---|---|
| Live video over RTSP | Yes | Yes | Profile S §7, T §7.9 |
| H.265 from the camera | Not in Profile S v1.3 (MJPEG mandatory, H.264 "if supported") | "Client shall be able to receive a stream and decode H.265"; a T device needs only one of H.264 or H.265 | Profile T §7.9 |
| Motion alarm and tamper events | Generic event handling, conditional for clients; "motion" and "tamper" do not appear in Profile S v1.3 | Motion Alarm events mandatory for client and device (§7.20); tampering events mandatory for the device, "if supported" for the client (§7.17) | Profile T v1.0 |
| PTZ, analytics, two-way audio | Optional | "May be supported" by the client | Profile T §6 |
| Analytics metadata (line crossing, objects) | No | No; needs a Profile M client, which ONVIF says can be an NVR | Profile M |
| Brand smart codecs (H.265+, H.264+) | Not in any ONVIF profile | Not in any ONVIF profile | Hikvision NVR manual lists "H.265+/H.265/H.264+" for its own range |
Per ONVIF's 9 Oct 2025 release, the June 2026 test tools (valid nine months) are the last allowing a Profile S claim, so T is the level to ask for (profiles explained).
What conformance guarantees and what it does not
Per ONVIF's conformance process, each listing means one product, at one firmware, passed ONVIF's Device or Client Test Tool for the claimed profiles and its maker filed a Declaration of Conformance.
- It does cover: each side's mandatory features for its listed profiles. For an S + T pair: RTSP video, H.265 decoding on the client, Motion Alarm events on both sides.
- It does not cover: that the two products were ever connected to each other; firmware other than the listed one; that the camera actually offers H.265 (a Profile T device may offer only H.264); tamper events on the client (conditional); PTZ, analytics, audio, smart events; brand smart codecs.
Where brands differ
- Hikvision adds ONVIF cameras on the camera's HTTP port, 80 by default, not SDK port 8000 (Hikvision how-to). Linear scan and one-touch park need the Hikvision protocol (V4.1.70 manual). Prama documents Custom Adding via ONVIF, no port printed.
- CP Plus asks for HTTP 80 and RTSP 554 when Manufacturer is ONVIF; its private protocol uses TCP 25001. Its manual lists "Unsupported ONVIF version" as a cause of "cannot add".
- Matrix is strictest: camera ONVIF 2.0+ with Profiles S and G. Only 134 of the 196 certified models are listed with both S and G.
- Uniview wants the camera's date and time equal to the NVR's, and some cameras' separate ONVIF user.
Add-by-IP steps: NVR not detecting IP camera.
What breaks in a factory
- Mixed fleets after partial replacement. New cameras on an older NVR inherit its client level. A Uniview or 2026 CP Plus listing covers video, not H.265 or events.
- H.265 Auto Switch and old NVRs. A camera flipped to H.265 can go blank on an S-only recorder; CP Plus lists "Unsupported encoding" for blank live view.
- Reflashing. Conformance is per firmware; a unit reflashed after a surge may differ from the listed build.
- Analytics downstream. Keep smart codecs off on the stream an AI box reads (sub-stream settings).
When to call the installer / what to ask the vendor
Ask the NVR vendor for its ONVIF client listing (model and firmware) and whether it shows Profile T and M. Ask the camera vendor for the exact model's Declaration of Conformance. In tenders, ask for "ONVIF Profile T, device and client, listed on onvif.org".
Mama reads a plant's existing cameras over RTSP or ONVIF to report machine idle time to the owner (askthemama.com). Leave an email or phone in the form below.
FAQ
Can I mix ONVIF cameras of different brands on a Hikvision NVR? Asked on ipcamtalk. Hikvision's V4.1.70 manual lists ONVIF cameras as connectable. Its client listings since Oct 2023 all include Profile T, so H.265 and motion events are in conformance scope if the camera is T-listed too, not guaranteed.
Will a CP Plus camera work on a Hikvision or Prama NVR? By the ONVIF database, 34 of 45 STQC-certified CP Plus models are S + T listed, and recent Hikvision and Prama NVRs are S + T clients, each tested separately; no source cited tested the pair. Hikvision says to add on the camera's HTTP port (80 by default).
Why do ONVIF cameras record on my NVR but never trigger motion? A recurring ipcamtalk question. Profile T makes Motion Alarm events mandatory for both clients and devices; Profile S does not mention them. If either side is S-only, conformance does not check motion events at all.