01304 827609 info@use-ip.co.uk Find us

Door Entry DS -KV6113 WPE1 Plugged in to NVR PoE not Communicating with app when Button Press

bizentech

Member
Messages
12
Points
3
Hello all, I have my DS-KV6113 Doorbell connected behind my NVR (so it can also record to NVR) but i cannot get the doorbell to ring. It always says "calling failed". I have my push notifications enabled on the app, but i have a feeling it has something to do with communicating out of the POE. Like a tunnel. I also tried connecting it to wifi as well, like a Dual NIC, but cannot seem to connect via QR code scan.

Any help would be appreciated.

Bottom line is, I would love to have my Doorbell physically connected and powered by the NVR, but cannot receive the doorbell. Really do not want to put it on a switch and configure it differently. Thank you
 
Hi @bizentech

As far as we are aware it is not possible to directly connect the intercom to your NVR PoE ports because the Hik-Connect app and/or indoor stations need direct access to the intercom via a dedicated IP address, if you add the intercom to the app via the NVR all the app sees is the NVR.

You will need to connect the intercom to a separate PoE injector/switch and then add the intercom directly to Hik-Connect, you can still record to the NVR by adding the intercom over the local network to the NVR using its IP address.
 
Hi @bizentech

As far as we are aware it is not possible to directly connect the intercom to your NVR PoE ports because the Hik-Connect app and/or indoor stations need direct access to the intercom via a dedicated IP address, if you add the intercom to the app via the NVR all the app sees is the NVR.

You will need to connect the intercom to a separate PoE injector/switch and then add the intercom directly to Hik-Connect, you can still record to the NVR by adding the intercom over the local network to the NVR using its IP address.

thats (not) correct.

for security reasons the POE-ports are not reachable through your own network i.e. can not use an internet connection.

you can use the "virtual host" setting on the nvr. if you turn it on, you can create a static route from your network to the hikvision network.
older hik nvrs (with older firmwares) can use the dhcp server of the router for everything if you want. i think they decide to disable this feature on newer firmwares, even if you have virtual host setting on. if you create a static route, each camera is connected directly to the internet (if you tell them which gateway they have to use,.. there is no gateway setting by default on cameras if they where added plug&play) .

it is just important that you put the gateway of the POE NVR Switch on the doorbell.. should be 192.168.254.1 (typical for hikvision nvr). the doorbell needs to know which gateway it have to use for routing the traffic to the internet and the router have to know to which gateway is has to route from the internet... everything is possible... many using it when they want an ftp upload or email from ONE specific camera...

maybe a better /easier solution:
connect a poe switch between the nvr and your network, plug the doorbell to the poe switch. a 4 port poe switch costs only 30-35 pound/dollar/euro..

conclusion:

- enable virtual host in nvr
- give the doorbell a manual Ip of the hikvision poe network
ip: 192.168.254.200 (for example, have to be not used)
subnet: 255.255.255.0
gateway: 192.168.254.1
- create a static route in your router
Network 192.168.254.0/24 (subnet 255.255.255.0) use <IP OF THE NVR FROM YOUR NETWORK .. example 192.168.1.48> as gateway
- connect the doorbell to a poe port

with this settings you can reach every single camera (and the doorbell) from YOUR network by their ORIGINAL ip which where given from the NVR POE SWITCH ! also the doorbell can talk to the p2p cloud of hikvision directly. for security reasons you should block internet for the cameras in the router ;)
 
Last edited:
So, for example:

virtual host on

NVR assigned static IP: 192.168.1.200
Gateway:192.168.1.1/24

DB assigned static IP: 192.168.254.2
PoE gateway: 192.168.254.1/24

Home router: 192.168.1.1/24

so, static route has to between 192.168.1.1 and 192.168.254.1?
Can I just do a static route between 192.168.1.1 and 192.168.241.2 (the Doorbell?) or not because it is not a gateway?

I understand what you’re explaining but I don’t know how to set it up. If it takes more than 15 minutes, I’ll just put a small PoE switch to the doorbell
 
You just have to

- enable virtual host on NVR
- make a static route between 192.168.254.0/24 and 192.168.1.200 (gateway) in router
- assign settings on doorbell:
ip: 192.168.254.2 (not sure if this ip is not taken by a camera already, check first)
netmask: 255.255.255.0
gateway: 192.168.254.1
DNS: use public dns, as secoundary , like 8.8.8.8 , primary should be set automatic .. but i am not sure if 192.168.254.1 forwards dns ,,, you have to try

...

the traffic should float
192.168.254.2 (doorbell ) -> 192.168.254.1 (gw) -> (192.168.1.200) -> 192.168.1.1 (gw) -> internet
internet -> ... 192.168.1.200 (knows where 192.168.254.2 is) -> .....


it should take 1 min to add a static route ... try it, or just buy a cheapo 4port poe switch ;)

try on cmd ... ping 192.168.254.2 (doorbell) from your network... after settings set

ps. /24 ... or 255.255.255.0 (depends on router model ... some wants .0/24 and some just 0 and netmask 255.255.255.0 )
 
Last edited:
Back
Top