u/Typical_Bake_3461

Hi everyone,

I’ve been working on a lightweight Hikvision ISUP-based monitoring system focused on one thing: remote access.

A lot of Hikvision projects are deployed in parking lots, communities, factories, stores, and unmanned sites. The common problem is always the same:

• the cameras/NVR are on-site
• the operator is somewhere else
• remote access is messy, unstable, or depends too much on local network setup

So I built a small ISUP system mainly for off-site monitoring and management.

What it does:

• remote live view for Hikvision IPC/NVR devices over ISUP
• remote playback and video download by time range
• device online/offline management
• multi-device access from different locations
• alarm/event integration
• channel-based handling for NVR devices
• private deployment on your own server

The main idea is simple:
instead of treating every project like a local LAN project, this is built around cross-region / remote access from the start.

Typical use cases:

• parking lot project where the owner wants to view cameras from another city
• chain stores where multiple sites need centralized remote access
• factory/warehouse where the technical team is not physically on-site
• projects where the customer wants private deployment instead of public cloud dependence

Why I chose ISUP:

• better for remote device registration
• better for projects with multiple distributed sites
• easier to build a private server-side workflow for access, playback and integration
• more suitable when the customer wants “our own platform” instead of only using vendor software

I’m still improving it, especially around:

• better capability detection for different NVR/camera models
• smoother remote playback workflow
• cleaner deployment package for private projects

If anyone here is also working with Hikvision ISUP, remote monitoring, or NVR integration, I’d love to exchange ideas.
I’m especially interested in real-world deployment feedback from distributed/off-site projects.

I built an access control management system based on Hikvision ISUP 5.0, mainly for managing remote access control devices across different locations.

It is suitable for offices, factories, warehouses, campuses, retail stores, and other sites where devices are deployed in different networks or cities. Devices can actively connect to the platform through ISUP, so each device does not need its own public IP.

Currently supported:

• Remote device registration via ISUP
• Online/offline device status
• User management and deployment
• Face enrollment
• Card and fingerprint management
• Remote door opening
• Access event receiving
• Face/card access records
• Visitor temporary authorization
• Access policy deployment
• Door/access control configuration
• Web admin dashboard
• Raw ISAPI passthrough for debugging

This is not just a simple SDK demo. It combines ISUP device registration, event callbacks, face image service, ISAPI operations, and a web management interface into one practical system.

It can also be customized for different project needs, such as:

• Integration with existing employee systems
• Batch import of users and face images
• Attendance reports
• Visitor appointment workflow
• Multi-site centralized management
• Access control and camera integration
• OA/HR/ERP integration
• Custom web dashboard
• Private deployment

If you are working on remote access control, Hikvision face terminals, ISUP integration, or related secondary development, feel free to connect.

Note: This is an independently developed access control system, not official Hikvision software.

Hi everyone,

I’m building SightForte, a private-deployment VMS/NVR system for small businesses and local camera sites.

The idea is simple: many small customers want a modern browser-based camera system, but they don’t necessarily want their video pushed into a cloud SaaS platform. SightForte runs on a local server or mini PC, connects to ONVIF-compatible IP cameras, and keeps live view, recordings, events, and storage management inside the customer’s own LAN.

Current focus:

• ONVIF camera discovery and onboarding
• Browser-based live view
• Local NVR recording and playback timeline
• AI alarm events such as line crossing, intrusion, loitering, and motion areas
• Storage retention and weekly recording schedules
• User roles and audit logs
• Free edition for small testing deployments

One area I’m especially interested in is custom AI models.

Instead of forcing one generic model across every camera, the Pro workflow is designed so customers can use different models for different cameras. For example, one camera could use an entrance/security model, another could use a warehouse model, and another could use a pet/person detection model. I also plan to offer custom model training as a service for customers who have specific detection needs.

I’m mainly targeting small sites such as retail stores, offices, warehouses, clinics, schools, and installers who need something more flexible than a basic NVR box, but less complicated than enterprise VMS software.

I’d love feedback from people who manage IP cameras or small security systems:

• What would make you trust a private VMS/NVR product?
• Is custom AI model support actually useful for your use case?
• What features matter most before you would try this in a real site?
• Do you prefer local-only deployment, or do you still expect some cloud features?
• Website: https://sightforte.com

Thanks. I’m still shaping the product, so practical criticism is very welcome.

Been doing Hikvision integration work for a while and figured I'd dump some of the stuff that tripped me up early on. Maybe it saves someone a weekend.

1. ISAPI uses HTTP Digest auth, not Basic. First request comes back 401 with a WWW-Authenticate: Digest header — you compute the response and retry. If your HTTP client doesn't handle digest automatically (Python requests needs HTTPDigestAuth, for example), you'll be stuck on 401 forever wondering why your password is "wrong."

2. Event subscription — pick the right pattern.

• Alert stream (long-poll): GET /ISAPI/Event/notification/alertStream. The device keeps the connection open and pushes multipart/mixed chunks. Parse the boundaries, pull XML (and sometimes JPEGs) out of each part. Don't close the socket between events — that's not how it works.
• HTTP listener (push): Configure the device to POST events to your server (Network → Advanced → HTTP Listening, or via ISAPI). Easier to scale than one held-open socket per device. Body is multipart/form-data with an XML part and optional image parts.

Don't poll /ISAPI/Event/triggers expecting live events — that endpoint is for configuration.

3. SDK vs ISAPI — know what you're trading.

• HCNetSDK: more features, especially smart events, two-way audio, some PTZ. But the official builds are x86/x86_64, Windows or Linux only. ARM and macOS aren't officially supported (some folks get aarch64 working unofficially, mileage varies). Deployment is painful.
• ISAPI: plain HTTP, works anywhere, easy to containerize. Missing some smart-event detail and a few advanced features.

If you don't need the SDK, don't use the SDK.

4. RTSP URL format people get wrong:

• rtsp://user:pass@ip:554/Streaming/Channels/101 — main stream, channel 1
• 102 is sub-stream, 201 is channel 2 main, etc.
• URL-encode the password if it contains special characters. An @ in a password will silently break the URL parser.

5. Smart events have to be enabled per channel. Line crossing, intrusion detection, region entrance, etc. won't fire just because the camera supports them. Enable per channel in device config (or PUT the right XML to /ISAPI/Smart/...), draw the detection regions, then they'll show up in the alert stream.

6. Firmware behavior varies a lot. Same model, two firmware versions, two different ISAPI quirks. Always test against the actual firmware that'll be in production. Official docs are mostly accurate but lag real device behavior, especially on newer smart features.

7. Encoding gotcha. Newer firmware is UTF-8 throughout. Older devices sometimes return GB2312 in XML, especially channel names with non-ASCII characters. If you see mojibake, that's where to look.

Happy to answer questions in the comments if anyone's stuck on something specific — this is the kind of work I do day to day, so I've probably hit most of the sharp edges.