ds-kb6003-wip firmware

Ron C

Ron C

Young grasshopper
Jun 20, 2019
49
3
Los Alamos, NM, USA
Hello,

I have a Hikvision ds-kb6003-wip (Uniden U-bell), I belive hardware wise they are identical (I was told).

What is the latest firmware? Also, is there a way to force the doorbell to install the firmware? (from SD card) ?

I have version 1.4.62 180515 but found version V1.4.62_180809 also. (what is teh newest best version anyway).

The web interface is somewhat messed up, the webcontrols don't work (even in a windows machine). and in firefox (on linux) nothing much at all except some configuration screens.

any ideas?

thanks,

Ron
 
V1.4.62_180809 is the latest.
Use Internet Explorer 11. You will need Hikvision's WebComponents.exe plugin installed. Right click on the file and select 'Run as administrator' with all browsers closed. That will correct the issues with the webGUI.
 
StewartM said:
V1.4.62_180809 is the latest.
Use Internet Explorer 11. You will need Hikvision's WebComponents.exe plugin installed. Right click on the file and select 'Run as administrator' with all browsers closed. That will correct the issues with the webGUI.
Click to expand...

Hello Stewart,

thanks for your quick reply;

I have an old windows 7 laptop, that I tried to do that with. and... firefox indeed doesn't seem to work. I'll try IE (I don't know what version that is though). I mostly have Linux machines that I work with here. I am trying to get "direct access" to the doorbell I can capture an image, and can get a stream out of it. I would like to get access to the events too.

Any ideas there?

Ron
 
StewartM said:
My understanding is NPAPI plugins are no longer supported in FF and Chrome due to security risks. You could update your Windows 7 laptop to IE11 and load the plugin. Some users have reported Pale Moon works. http://linux.palemoon.org/ or MoonchildProductions/Pale-Moon
Click to expand...


That is correct, most browser vacated NPAPI plugins, because of security issues. I actually do have IE11 on that windows 7 machine. I did install the webcomponents installed, however I can see any video nor stills, or audio. There are a few things I am probably not getting.

In one of the pages in the web interface, there is an ftp setting, which I set up to use a local unix server/machine, and it seems (my interpretation) that the doorbell does something "ftp-ish" with events?
Would actually be great if I could an event-notification like that. catching a "press doorbell button" even would be great, getting some sort of motion detection out of it would be awesome.

I am not using a smart phone app to control the phone, I want to avoid using one tobegin with.

Do you know if anyone ever tried to change the firmware?

thanks,

Ron
 
StewartM said:
I have no experience with the ds-kb6003-wip. Hikvision does have tools to update the firmware though. The Batch Configuration Tool will probably do it.
I've never tried with a HIK doorbell but what happens if you amend and paste the following into your browser? I suspect it will return an error as CGI is not supported.
http://admin:xxxxx@192.168.1.xx/ISAPI/System/capabilities
Click to expand...


Yes ISAPI does work, (that is not CGI I think though). Also what is interesting is that there are more ports on that camera.
The camera is branded Uniden U-Bell (the hardware shows it is Hikvision)
This is what nmap shows:
Starting Nmap 7.70 ( Nmap: the Network Mapper - Free Security Scanner ) at 2019-06-29 13:17 MDT
Nmap scan report for 192.168.2.xx
Host is up (0.0095s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
554/tcp open rtsp
8000/tcp open http-alt
9010/tcp open sdr
49152/tcp open unknown
MAC Address: 18:68:CB:F1:40:87 (Hangzhou Hikvision Digital Technology)

Nmap done: 1 IP address (1 host up) scanned in 4.28 seconds

Of course 80 and 443 are for http, there seems to be more living on those ports then just the web interface. 554 is for rtsp, I can connect to it and get a stream out.

then there's 8000, I have seen that in previous firmware versions and also 49152.

I upgraded to firmware version 180729 a few hours ago, and port 9010 appeared.

Since Unided and Hikvision claim it is an ONVIF compatible device, I wonder on what port it is running.

I did poke around a bit with the rest-client browser plugin, to see what it did but haven't really seen any ONVIF stuff really yet.

Ron
 
Ron C said:
Yes ISAPI does work, (that is not CGI I think though). Also what is interesting is that there are more ports on that camera.
The camera is branded Uniden U-Bell (the hardware shows it is Hikvision)
This is what nmap shows:
Starting Nmap 7.70 ( Nmap: the Network Mapper - Free Security Scanner ) at 2019-06-29 13:17 MDT
Nmap scan report for 192.168.2.xx
Host is up (0.0095s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
554/tcp open rtsp
8000/tcp open http-alt
9010/tcp open sdr
49152/tcp open unknown
MAC Address: 18:68:CB:F1:40:87 (Hangzhou Hikvision Digital Technology)

Nmap done: 1 IP address (1 host up) scanned in 4.28 seconds

Of course 80 and 443 are for http, there seems to be more living on those ports then just the web interface. 554 is for rtsp, I can connect to it and get a stream out.

then there's 8000, I have seen that in previous firmware versions and also 49152.

I upgraded to firmware version 180729 a few hours ago, and port 9010 appeared.

Since Unided and Hikvision claim it is an ONVIF compatible device, I wonder on what port it is running.

I did poke around a bit with the rest-client browser plugin, to see what it did but haven't really seen any ONVIF stuff really yet.

Ron
Click to expand...


this is what that ISAPI command reports back: (I would like to see/find a list of ISAPI 'commands' as well as CGI commands.) I can see a bunch of them in some javascripts in the webinterface

<DeviceCap version="2.0"><SysCap><isSupportDst>true</isSupportDst><NetworkCap version="2.0"><isSupportWireless>true</isSupportWireless><isSupportPPPoE>false</isSupportPPPoE><isSupportBond>false</isSupportBond><isSupport802_1x>false</isSupport802_1x><isSupportNtp>true</isSupportNtp><isSupportFtp>true</isSupportFtp><isSupportUpnp>false</isSupportUpnp><isSupportPNP>false</isSupportPNP><isSupportDdns>false</isSupportDdns><isSupportHttps>true</isSupportHttps></NetworkCap><IOCap version="2.0"><IOInputPortNums>1</IOInputPortNums><IOOutputPortNums>1</IOOutputPortNums></IOCap><SerialCap version="2.0"><rs485PortNums>0</rs485PortNums><rs422PortNums>0</rs422PortNums><rs232PortNums>0</rs232PortNums><supportRS232Config>false</supportRS232Config></SerialCap><VideoCap version="2.0"><videoInputPortNums>1</videoInputPortNums><videoOutputPortNums>1</videoOutputPortNums></VideoCap><AudioCap version="2.0"><audioInputNums>1</audioInputNums><audioOutputNums>1</audioOutputNums></AudioCap></SysCap><voicetalkNums>1</voicetalkNums><isSupportSnapshot>false</isSupportSnapshot><SecurityCap version="2.0"><supportUserNums>1</supportUserNums><userBondIpNums>1</userBondIpNums><userBondMacNums>1</userBondMacNums><issupIllegalLoginLock>true</issupIllegalLoginLock><securityVersion opt="1"/><keyIterateNum>100</keyIterateNum></SecurityCap><EventCap version="2.0"><isSupportNicBroken>true</isSupportNicBroken><isSupportIpConflict>true</isSupportIpConflict><isSupportIllAccess>true</isSupportIllAccess></EventCap></DeviceCap>
 
StewartM said:
With the rest client you can enable ONVIF:
PUT http://admin:xxxx@192.168.1.xx/ISAPI/System/Network/Integrate
Body:
<Integrate>
<ONVIF><enable>true</enable><certificateType /></ONVIF>
</Integrate>

You will need a user account for ONVIF to work:
PUT http://admin:xxxx@192.168.1.xx/ISAPI/Security/ONVIF/users
Body:
<UserList>
<User>
<id>1</id>
<userName>admin</userName>
<password>xxxxxx</password>
<userType>administrator</userType>
</User>
</UserList>
Click to expand...


Those don't seem to work on the doorbell... I found a hikvision document, that mentions some URLs that work on the device. I tried them, they are not literally the same, but one can guess some of them. here is what I found. (I didn't try the factory resets though)

GET:
http://192.168.2.x/ISAPI/System/deviceInfo
http://192.168.2.x/ISAPI/System/time
http://192.168.2.x/ISAPI/System/IO/inputs
http://192.168.2.x/ISAPI/System/IO/outputs
http://192.168.2.x/ISAPI/System/Video/inputs/channels
http://192.168.2.x/ISAPI/Streaming/channels
http://192.168.2.x/ISAPI/Streaming/channels/101
http://192.168.2.x/ISAPI/Streaming/channels/101/capabilities
http://192.168.2.x/ISAPI/System/time/ntpServers
http://192.168.2.x/ISAPI/System/Network/interfaces/1/ipAddress


PUT:
http://192.168.2.x/ISAPI/System/reboot

there is also this one:
GET: http://192.168.2.x/ISAPI/Event/notification/alertStream

which creates responses like:
<EventNotificationAlert version="1.0" xmlns="urn:psialliance-org">
<ipAddress>192.168.2.x</ipAddress>
<portNo>80</portNo>
<protocol>HTTP</protocol>
<macAddress>18:68:cb:00:00:00</macAddress>
<dateTime>2019-06-29T17:08:49-07:00</dateTime>
<activePostCount>1</activePostCount>
<eventType>other</eventType>
<eventDescription>Heartbeat</eventDescription>
<eventState>inactive</eventState>
<Extensions version="1.0" xmlns="urn:psialliance-org">
<serialNumber>DB10120171somethingsomething</serialNumber>
</Extensions>
</EventNotificationAlert>

however, they always show "heartbeat", but never see anything that looks like the doorbell button was pressed.
 
Try set the certificate to digest/basic? What is the response when you try?
PUT /ISAPI/System/Network/Integrate
Body:
<Integrate>
<ONVIF><enable>true</enable><certificateType>digest/basic</certificateType></ONVIF>
</Integrate>
 
StewartM said:
Try set the certificate to digest/basic? What is the response when you try?
PUT /ISAPI/System/Network/Integrate
Body:
<Integrate>
<ONVIF><enable>true</enable><certificateType>digest/basic</certificateType></ONVIF>
</Integrate>
Click to expand...
the authentication I used is digest/basic, what I get is: "Can't locate the url"

thanks for the document, I'll read through it

Ron
 
Perhaps now the common gateway interface needs to be enabled.
PUT /ISAPI/System/Network/Integrate
<Integrate><CGI><enable>true</enable><certificateType>digest/basic</certificateType></CGI></Integrate>

Then try enabled ONVIF.
 
StewartM said:
Perhaps now the common gateway interface needs to be enabled.
PUT /ISAPI/System/Network/Integrate
<Integrate><CGI><enable>true</enable><certificateType>digest/basic</certificateType></CGI></Integrate>

Then try enabled ONVIF.
Click to expand...


It says it doesn't know that url either.

It's not as much that I really want to use the ONVIF capability, I thought it would be a good way to figure out how to "subscribe" to events (motion, doorbell button) without having to use a phone.

Ron
 
Ron C said:
It says it doesn't know that url either.

It's not as much that I really want to use the ONVIF capability, I thought it would be a good way to figure out how to "subscribe" to events (motion, doorbell button) without having to use a phone.

Ron
Click to expand...


So what I read, when doing a search, that "http://<ip address>/ISAPI/Event/notification/alertStream" is supposed to produce a stream of data? However, I only get one chunk of data, and that's it?
Also, the return pretty much is the same every time.

This is what I get:

<EventNotificationAlert version="1.0" xmlns="urn:psialliance-org">
<ipAddress>192.168.x.y</ipAddress>
<portNo>80</portNo>
<protocol>HTTP</protocol>
<macAddress>18:68:cb:xx:xx:xx</macAddress>
<dateTime>2019-06-30T19:44:57-07:00</dateTime>
<activePostCount>1</activePostCount>
<eventType>other</eventType>
<eventDescription>Heartbeat</eventDescription>
<eventState>inactive</eventState>
<Extensions version="1.0" xmlns="urn:psialliance-org">
<serialNumber>DB10120171010WRxxxxxxxxxCLU</serialNumber>
</Extensions>
</EventNotificationAlert>

It always seems to be a heartbeat that gets returned.

Does anyone know how to setup an event stream?

thanks,

Ron
 
StewartM said:
Have a look at the attached from page 26 onward (triggers and notificationmethod.) It's for ANPR mainly but it might provide some leads.
Click to expand...

Hello Stewart,

that looks promising, I am going to play with that a bit. I did notice that there are a lot of differences between different hikvision cameras. Also, I installed an NVR cleint (nvr4200 ?) and that seems to work better configuring
the doorbell camera. With that windows app the ftp configuration actually 'stuck' Now the doorbell uploads a snapshot to my own ftp server in case of a motion event. It even let me set the "area" to be tested. something the web interface wouldn't let me do.

thanks!

Ron
 
You must log in or register to reply here.
Top Bottom