Quick answer: Choose the add method supported by the exact camera, recorder and firmware. A built-in PoE port provides a possible power/network path, not an automatic compatibility or analytics guarantee. Confirm device identity, compatible power, approved addressing and authorized accounts, then test the required recording, playback and events. External-switch and third-party integrations also need a documented supported path and realistic acceptance checks.
On this page
Before you start: firmware, credentials and a cable test
Prepare a device/channel plan and a controlled bench test before site work. A successful bench add narrows the risk but does not prove the installed cable, night load or final feature set. Keep passwords in an approved protected vault, not a shared drawing or ordinary job note. Check the NVR firmware download resources for the approved release and revision-specific instructions.
- Versions: record exact full SKUs/revisions and firmware and confirm supported pairing. An update or downgrade needs the approved release path, backups, impact and rollback plan; retaining an old file alone does not make rollback safe.
- Accounts: establish authorized unique credentials and supported least-privilege account roles. Record non-secret account references and control access to the protected vault.
- Path and power: test the actual cable and compatible PoE source/device load under the required topology and environment. Wiremap alone is not channel performance or delivered-power certification; use the responsible designer’s local installation requirements.
- Channel mapping: distinguish video channels from physical ports. CS-N105 P4H-AI lists5 channels/4 PoE ports; CS-N220 P16H-AI lists20/16. Confirm the supported mapping rather than fixing channel numbers to ports.
- Capacity: N105 P4H-AI lists100/80 Mbps in/out and N220 P16H-AI160 in (AI on120)/80 out; both list maximum16 MP. Confirm the actual revision’s stream/decode/AI limits and budget all required traffic separately with headroom.
Method 1: Plug-and-play on the NVR PoE ports
Use built-in PoE only where the exact camera/recorder pairing, power, cable path and firmware support it. Check the actual commissioning process, account/address behavior and network policy before connecting a production device; same-brand equipment does not establish automatic enrollment.
- Complete the approved recorder setup, authorized accounts, accurate time and required recording policy. Connect to the approved network only as designed; remote viewing does not justify public exposure.
- Connect the documented compatible camera on the planned PoE path and confirm actual power/link behavior. Address assignment, activation and channel enrollment are model/firmware-specific.
- Read the actual device identity and supported camera-management result. Provide authorized credentials by the supported method without repeated guesses or unnecessary resets.
- Set the agreed view, focus and location name, then verify recording/playback and required events under the actual day/night/load conditions. Online status alone is not acceptance.
CS-I5KS SD-2.8mm lists3072×1728 at30fps,IR30 m,white light10 m,IP67/IK10 and Tripwire/Perimeter/Human & Vehicle Classification in the catalog (physical PDF3). Those camera rows do not guarantee every function through CS-N105 P4H-AI or every firmware. Confirm supported configuration and actual event, recording and playback results. If a channel stays offline, NVR not showing cameras covers the troubleshooting checks.
Method 2: Camera on an external PoE switch (manual IP)
An external switch may suit the approved cable topology, distribution or additional camera count, subject to power, network and recorder resource limits. More channels than built-in ports can require another supported path; it does not prove channel5 or17 is permanently a particular LAN device.
- Connect the camera through the approved compatible switch/source and network design, confirming per-port/shared PoE, cable losses and environment.
- Use the supported device setup/discovery tool and authorized access path. The Search Config Tool guide explains the planning; verify the current exact tool/version on Downloads.
- Apply IT’s stable addressing policy, which may use supported static allocation or DHCP reservation, with the correct subnet/routes/access. A reservation need not be outside its managed scope.
- Add the exact device to an available channel using the documented supported native/driver method and protected account fields. Confirm actual endpoint, permissions and mapping.
- Verify required streams, recording, playback, events and recovery under realistic load. A displayed configuration page does not establish that an AI workflow functions as required.
DHCP renewal does not automatically move a camera, and routed subnets can be valid under an approved design. Keep stable mapping, permitted routes and required services documented; do not force every camera onto the customer LAN or bypass segmentation to make discovery work. Choosing the right CASE NVR covers recorder and external-switch planning.
Method 3: Third-party camera over ONVIF (Profile S/T)
For retained third-party cameras, use an integration explicitly supported by both device and recorder versions; ONVIF may be one route. Check the exact conformance record, mandatory/conditional functions and actual events/recordings. S/T/G/M are profile scopes, not blanket support across CASE or third-party products. Do not promise a feature from a brand-level compatibility statement.
- Confirm required functions and the actual supported service, endpoint, secure authentication and minimum account rights. Enable or change a service only through the approved configuration plan.
- Establish accurate coherent time and verify any method-specific timestamp requirements. One literal NTP host/display zone is not universally necessary.
- Confirm approved stable addressing, topology, isolation and least-privilege service/media flows, including the actual behavior of built-in camera ports.
- Add the exact device using the documented method and protected credentials. Test actual main/sub or other required streams with mutually supported codec, rate, resolution and transport.
- Verify recording, playback, required events/PTZ/audio and export/recovery. Do not lower agreed image requirements or remove encryption simply to make a test pass.
If the channel still refuses, the ONVIF camera not connecting to NVR checklist walks through profile, credentials and time sync, and ONVIF Profile S, T, G and M explained covers what each profile does not promise.
Which method for which camera?
| Decision | Built-in PoE path | External-switch path | Third-party integration |
|---|---|---|---|
| Compatibility | Exact camera/recorder/firmware pairing | Exact supported native/driver pairing | Exact supported driver/ONVIF or other documented method |
| Power and addressing | Actual port and camera-network policy | Approved switch and stable address/routing plan | Confirm actual power/path and permitted endpoints |
| Accounts and time | Authorized supported account and accurate time | Authorized supported account and accurate time | Supported secure method and any timestamp requirements |
| Features and acceptance | Verify actual required functions and recordings | Verify actual required functions and recordings | Verify supported functions individually; no blanket AI or playback promise |
What you give up with ONVIF: AI features and VCA Search
A supported native integration may expose functions that another integration does not, but neither a native add nor ONVIF label proves every feature. Separate live media, camera events/metadata, recorder-side AI/search, controls and edge playback. Confirm exact device/client behavior and record the acceptance result before quoting the required workflow.
- Camera-side analytics: verify the actual supported rules, event/metadata path and recorder mapping. CS-I5KS SD-2.8mm’s printed AI list is not an end-to-end guarantee.
- Recorder AI and VCA Search: confirm supported channels, firmware, rules, capacities and software workflow separately from the camera’s capabilities. Native enrollment alone is not proof.
- Deterrence, audio and recordings: verify actual model controls, transport/account rights, authorized audio use and edge-recording retrieval. Applicable ONVIF functions may be conditional; test the required behavior rather than promising or rejecting it categorically.
Choose a mixed-site design from the customer’s required functions, supported integrations and tested limits. Document retained equipment, compatibility gaps and migration options. Do not replace usable equipment or mandate one protocol solely from a generic brand rule. Select a network video recorder for that documented plan.
Common errors and fixes
| Observed problem | Controlled next check |
|---|---|
| Not found | Actual power/link, identity, approved discovery/service path and supported method |
| Authentication error | Actual account/rights/method, lockout and any time requirements; no repeated guesses |
| Online but no usable video | URI/media path, certificates, codec/transport, resource load and logs; not automatic bitrate reduction |
| Alternating channels | Corroborate device/address/mapping evidence; symptoms alone do not prove duplicate IP |
| Video works but a required event/control does not | Exact exposed functions, client mapping/permissions and configuration; not automatically expected or universally available |
What to tell your customer
We will use the supported method for each exact camera and recorder version, then test the recordings, playback and controls/events your project needs. We will document retained equipment and any limitations before the handover. A working video tile or native enrollment is not a promise of the complete feature set.
FAQ
Can I add a CASE camera over ONVIF instead of plug-and-play?
Use the method supported for the exact camera/recorder versions and required functions. A supported native path may offer useful controls, but neither native nor ONVIF is a universal choice or analytics guarantee. Confirm the documented integration and actual recording/event result before committing.
Why does the NVR have more channels than PoE ports?
Video-channel capacity and built-in PoE ports are separate. CS-N105 P4H-AI lists5/4 and CS-N220 P16H-AI20/16. Additional cameras may arrive through a supported external network/power path, but confirm the actual mapping and resource limits rather than assigning a universal protocol or fixed port to each channel number.
Which ONVIF port and user should I enter on the NVR?
Use the exact supported endpoint, scheme/port and authorized account with the minimum required rights. A separate ONVIF account is implementation-specific, and accurate time matters according to the actual authentication method. Keep encryption/isolation in place and do not assume one display zone or NTP host is the only valid design. The NVR hardening checklist provides the wider account and access checks.
Will AI features from a third-party camera show up on a CASE NVR?
Confirm exact camera event/metadata support, recorder mapping and actual AI/search limits for the versions and channels involved. A profile name or native enrollment alone does not guarantee the result, and ONVIF does not imply all analytics are absent. Test and obtain written support details for the required functions.
References
- Anabon: exact model and revision documents
- Anabon Technical Support
- ONVIF: profiles and conditional functions
- ONVIF: exact conformant products and firmware
- IETF RFC2131: DHCP behavior
