millukii/opencctv

Proyecto para crear una alternativa al software de Hikivision consumiendo ISAPI. Golang

OPENCCTV

---

GO consuming HIKIVISION ISAPI.

📝 Table of Contents

• About
• Getting Started
• Deployment
• Usage
• Built Using
• TODO
• Contributing
• Authors
• Acknowledgments

🧐 About

Extend functionality over cctv hikivision devices.

🏁 Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

• Golang v13

Give examples

Installing

brew install golang

Give the example

And repeat

until finished

End with an example of getting some data out of the system or using it for a little demo.

🔧 Running the tests

go test -v ./.../...

🎈 Usage

Add notes about how to use the system.

🚀 Deployment

Add additional notes about how to deploy this on a live system.

⛏️ Built Using

• [Golang]

✍️ Authors

• @kylelobo - Idea & Initial work

See also the list of contributors who participated in this project.

🎉 Acknowledgements

• Hat tip to anyone whose code was used
• Inspiration
• References

ISAPI

The OPEN Intelligent Security Application Programming Interface (ISAPI) is a text protocol in RESTful style based on HTTP for communicating between security devices/servers (e.g., cameras, DVR, NVR, etc.) and client software/system. It defines the communication standard between device/server and client software/system via the Internet Protocol (IP)

HTTP Methods

• POST: Create resources. This method is only available for adding resource that does not exist before.
• GET: Retrieve resources. This method cannot change the system status, only return data as the response to the requester.
• PUT: Update resources. This method is usually for update the resource that already exists, but it can also be used to create the resource if the specific resource does not exist.
• DELETE: Delete resources.

URL FORMAT

• ://[:port][abs_path [?query]]

Message Format

• For ISAPI protocol, the request and response messages generated among the interaction between devices and platform are data in XML format or JSON format.
• For configuration Content-Type in the JSON format message is "application/json; charset='UTF-8'"
• For data Content-Type in the JSON format message is "application/octet-stream"

Time Format

• The time format in the ISAPI protocol adopts ISO8601 standard (see details in http:// www.w3.org/TR/NOTE-datetime-970915 ), that is, YYY-MM-DDThh:mm:ss.sTZD (e.g., 2017-08-16T20:17:06+08:00).

Error Processing

• During the integration applications of ISAPI protocol, when the error of URL based on HTTP occurred, the ResponseStatus message (in XML or JSON format) which contains error code will be returned.

Authentication

• The authentication must based on HTTP Authentication: Basic and Digest Access Authentication, see https://tools.ietf.org/html/rfc2617 for details.
• The request session must contain authentication information, otherwise, device will return 401 error code.

Digest

• The message digest, which contains user name, password, specific nonce value, HTTP or RTSP operation methods, and request URL, is generated by the MD5 algorithm, see the calculation rules below. qop=Undefined Digest=MD5(MD5(A1)::MD5(A2)) qop="auth:" Digest=MD5(MD5(A1):::::MD5(A2)) qop="auth-int:" Digest=MD5(MD5(A1):::::MD5(A2))