DS-KB6003-WIP API/ISAPI/CGI

[Ron C]

Hello,

does anyone here know of a document, other then the SDKs, that describe the ISAPI and/or CGI for the ds-KB6003 doorbell?

I have seen a few PDFs with some ISAPI/CGI specs, for cameras, and some of the "stuff" in them works on this bell, but of course most is camera/device specific.

For example, some of the motion detection events work, BUT for example it doesn't say anything about how to "subscribe to a event stream, that would work.

There is a notification event where ftp works, one can put a notification snapshot/timestamp on a configurable FTP server, BUT that is for motion detection.

One thing I would like to implement is an actual button press, chime event.

If some one knows of some API docs specific to this doorbell, or that includes the events for this doorbell, please let me know.

thanks,

Ron

 

[StewartM]

Hi Ron, I stand under correction but I'm not aware of any document that specifically addresses ISAPI for the doorbell. The tool I mentioned previously (ONVIF Device Test Tool) would still be your best bet. At the time you were still trying to activate ONVIF - is that still the case?

 

[Ron C]

Hi Ron, I stand under correction but I'm not aware of any document that specifically addresses ISAPI for the doorbell. The tool I mentioned previously (ONVIF Device Test Tool) would still be your best bet. At the time you were still trying to activate ONVIF - is that still the case?
View attachment 44344

Hello Stewart,

Yes I would still like to 'activate' ONVIF. I have a bunch of ONVIF devices, and they can easily be queried for their capabilities, functionality and the format to invoke those.. I think it is easy.

For example, the ONVIF "GetCapabilities" functionality, and payload as described in the ONVIF programmers manual actually works on these devices. Also the URIs and URLs mentioned in the payload, can actually be looked up.

I tried the same with some of the ISAPI queries and XML payloads, I don't think that the isapi.org site is that functional anymore?

I will try the test tool, so "doorcontrol" would be capability I am looking for? The motion control part, it sending notifications by FTP, is actually convenient, especially since I did build some custom stuff tied together with a local website. The doorbell "pushing" a notification by FTP works reasonably well. Wouldbe handy if the chime/button notification has something like that, a push of some sort that can be captured.

I used the ONVIF test tool, it nearly doesn't show as much functionality as it does with a camera, or other ONVIF device.

So basically I am still looking for something ONVIF/ISAPI/CGI that I can use to reconfigure the doorbell significantly.

Also, I wondered, if the doorbell's USB can be used for connecting to the devices' FS From what I heard it runs some sort of *nix (linux or so).

Ron

 

[Ron C]

Hi Ron, I stand under correction but I'm not aware of any document that specifically addresses ISAPI for the doorbell. The tool I mentioned previously (ONVIF Device Test Tool) would still be your best bet. At the time you were still trying to activate ONVIF - is that still the case?
View attachment 44344

BTW: The doorbell has several ports, 80, 443, 8000, 9010 and 49512 I wondered if 49512 is the ONVIF port.. typically HNAP would use a port like that I have no idea what 9010 is doing and 8000 is definitely not your typical http/html port.

 

[Ron C]

BTW: The doorbell has several ports, 80, 443, 8000, 9010 and 49512 I wondered if 49512 is the ONVIF port.. typically HNAP would use a port like that I have no idea what 9010 is doing and 8000 is definitely not your typical http/html port.

BTW: I received this today, the tool finds the camera/doorbell, but I don't think I have the FW 5.5.0 firmware version.

below is what I was sent.

Ron

 

[StewartM]

ONVIF uses HTTP port 80 then accesses streams via RTSP on port 554(typically). The RTSP server listening port can range from 554 through 10554. Hikvision’s server ‘service’ port is on 8000. The Ezviz (one of Hikvision’s other remote view applications) command port is on 9010. Port 49512?? (does the port change on device reboot or remain constant?) Might be an service port for SSDP?

 

[Ron C]

ONVIF uses HTTP port 80 then accesses streams via RTSP on port 554(typically). The RTSP server listening port can range from 554 through 10554. Hikvision’s server ‘service’ port is on 8000. The Ezviz (one of Hikvision’s other remote view applications) command port is on 9010. Port 49512?? (does the port change on device reboot or remain constant?) Might be an service port for SSDP?

That is different. All ONVIF cameras I have run onvif on 8899. I don't know what 49152 does, no it does not change. Some devices I have have a portnumber like that, but that is used for HNAP, an outdated protocol (with a ton of security flaws).

I have been using the ONVIF style commands that I saw in some docs, I was surprised to see it actually works on port 80. Also, it is "not really" ONVIF I think. It doesn't listen to the basic ONVIF queries, and there is no real "command set discovery" that I see working. Typically you can ask an ONVIF piece of equipment about everything it knows how to do.
On the hikvison doorbell that seems to be more hidden

Ron

 

[Ron C]

Hi Ron, I stand under correction but I'm not aware of any document that specifically addresses ISAPI for the doorbell. The tool I mentioned previously (ONVIF Device Test Tool) would still be your best bet. At the time you were still trying to activate ONVIF - is that still the case?
View attachment 44344

I have been playing with that ONVIF tool, I seem to keep getting HTTP 401 errors, which is an authentication issue. Does this ONVIF tool work with the doorbell? If so, what am I doing wrong?

Ron

 

[StewartM]

WEB Authentication in the Security Authentication settings might be the issue. By default it's set to digest. Try set it to digest/basic.
PUT http://admin:xxxx@192.168.1.xx/ISAPI/Security/webCertificate
Body:
<WebCertificate xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
<CertificateType>digest/basic</CertificateType>
</WebCertificate>




f that doesn't work it might be the CGI + ONVIF + user that need attention.
First activate CGI and ONVIF:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/System/Network/Integrate
Body:
<Integrate>
<CGI><enable>true</enable><certificateType>digest/basic</certificateType></CGI>
<ONVIF><enable>true</enable><certificateType /></ONVIF>
</Integrate>

Then add a user:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/Security/ONVIF/users
Body:
<UserList>
<User>
<id>1</id>
<userName>admin</userName>
<password>xxxxx</password>
<userType>administrator</userType>
</User>
</UserList>

Which configures the device as seen below. Keep us posted.

 

[Ron C]

WEB Authentication in the Security Authentication settings might be the issue. By default it's set to digest. Try set it to digest/basic.
PUT http://admin:xxxx@192.168.1.xx/ISAPI/Security/webCertificate
Body:
<WebCertificate xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
<CertificateType>digest/basic</CertificateType>
</WebCertificate>

View attachment 44469


f that doesn't work it might be the CGI + ONVIF + user that need attention.
First activate CGI and ONVIF:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/System/Network/Integrate
Body:
<Integrate>
<CGI><enable>true</enable><certificateType>digest/basic</certificateType></CGI>
<ONVIF><enable>true</enable><certificateType /></ONVIF>
</Integrate>

Then add a user:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/Security/ONVIF/users
Body:
<UserList>
<User>
<id>1</id>
<userName>admin</userName>
<password>xxxxx</password>
<userType>administrator</userType>
</User>
</UserList>

Which configures the device as seen below. Keep us posted.
View attachment 44475

The first link doesn't seem to exist, the REST-client says: http://admin:xxxx@192.168.1.xx/ISAPI/Security/webCertificate

I think these doorbells might be a lot more different then their cameras.

I do think that basic/digest authentication works, that is what I use to get an RTSP stream and snapshots out of it.

Ron

 

[Ron C]

WEB Authentication in the Security Authentication settings might be the issue. By default it's set to digest. Try set it to digest/basic.
PUT http://admin:xxxx@192.168.1.xx/ISAPI/Security/webCertificate
Body:
<WebCertificate xmlns="http://www.hikvision.com/ver20/XMLSchema" version="2.0">
<CertificateType>digest/basic</CertificateType>
</WebCertificate>

View attachment 44469


f that doesn't work it might be the CGI + ONVIF + user that need attention.
First activate CGI and ONVIF:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/System/Network/Integrate
Body:
<Integrate>
<CGI><enable>true</enable><certificateType>digest/basic</certificateType></CGI>
<ONVIF><enable>true</enable><certificateType /></ONVIF>
</Integrate>

Then add a user:
PUT http://admin:xxxxx@192.168.1.xx/ISAPI/Security/ONVIF/users
Body:
<UserList>
<User>
<id>1</id>
<userName>admin</userName>
<password>xxxxx</password>
<userType>administrator</userType>
</User>
</UserList>

Which configures the device as seen below. Keep us posted.
View attachment 44475

btw: I noticed that the doorbell has a usb connector, just above the reset button. any idea what can be done with that one?

Ron