Hikvision ANPR HTTP Listening
Older Hikvision firmware often uses the term HTTP Listening where newer cameras may show Alarm Server. The underlying purpose is the same: send event information to another server.
Hikvision documentation for older network-camera firmware describes HTTP Listening under Configuration → Network → Advanced Settings → Listening. The camera is given a destination IP or hostname, a URL and a port, then sends alarm information to that endpoint.
Typical HTTP Listening fields
Some traffic-camera families expose the same concept under a different part of the interface. Hikvision's traffic-camera material also uses HTTP Listening and can include picture-type and Alarm Server Mode options.
HTTP Listening and Alarm Server are not competing features
They are largely different names for the camera's ability to push event information to a destination server. The exact screen, field labels and supported protocols vary by model and firmware generation.
How to verify the capability technically
For supported Hikvision firmware, Ruby ANPR's compatibility approach can query the camera's ISAPI HTTP-host capability endpoint:
A capability response containing a value equivalent to:
indicates that the camera reports support for an HTTP event destination. Firmware XML can vary, so automated detection should be tolerant rather than expecting one exact document shape.
Pictures and ANPR metadata
Traffic-camera interfaces may allow you to choose which images are included with the event. Depending on the model, this can include the full scene, the cropped plate image and a closer vehicle image. Ruby ANPR can retain up to three evidence images when the camera sends them.
What to do after saving the destination
- Use the camera's Test function if available.
- Confirm the request reaches your web server.
- Check that Ruby ANPR displays the synthetic test event.
- Perform one known real-vehicle pass.
- Confirm registration, images, confidence and direction.
If your interface only supports HTTP
Some older cameras or firmware builds may expose HTTP rather than HTTPS. Ruby ANPR's preferred production configuration is HTTPS, but exact transport support depends on the camera. Before exposing any endpoint publicly, assess the security implications of the protocol and firmware you are using.
If the model is not in the compatibility list
Do not assume it is incompatible. If it is a genuine Hikvision ANPR / traffic camera, check the HTTP host notification capability and firmware options first. Ruby ANPR separates models into confirmed, capability-detected compatible and unverified rather than blocking every unknown model.