Help with Costco Night Owl (Hikvision) NVR access via Chrome or Firefox

[Flintstone61]

 

[Flintstone61]

So yeah mainstreams and substreams both working now
rtsp:/USERASS@192.168.1.5/Streaming/channels/301 = Mainstream
rtsp:/USERASS@192.168.1.5/Streaming/channels/302 = Substream

 

[mat200]

:P

 

[htcheng]

Glad it helped you out! It should be illegal for manufacturers to disable perfectly working functions and shut down your "right to fix" - I'm not sure how I figured it out in the end other than by trial and error - thought I'd save some folks having to go through that pain.

 

[htcheng]

Now the bigger thing is to shut down remote access and other security holes that exist in Hikvision software- there's a reason the US Government banned them from being used in US installations...

 

[Flintstone61]

I wonder if that would work on my Nightowl HDA10-16

 

[Pavan ranganath]

For DVR-H2T80B-41-HIK with firmware, DVR4-H2T80B-20181208 had to open the RTSP port

Check the capabilities -
http://<IP_ADDRESS>/ISAPI/Security/adminAccesses/capabilities

You can see which ports are open on the DVR

If RTSP is available then enable using the PUT method

Then you can access the stream using the RTSP protocol

 

[jersh]

For DVR-H2T80B-41-HIK with firmware, DVR4-H2T80B-20181208 had to open the RTSP port

Check the capabilities -
http://<IP_ADDRESS>/ISAPI/Security/adminAccesses/capabilities

You can see which ports are open on the DVR

If RTSP is available then enable using the PUT method

Then you can access the stream using the RTSP protocol

Thanks for this, I was able to read the config and see that RTSP is disabled, but I am having trouble with the PUT command to update the config, I simply copied the entire XML and changed false to true for RTSP enable, however I am getting a 403 response.

<?xml version="1.0" encoding="UTF-8" ?>
<ResponseStatus version="1.0" xmlns="urn:psialliance-org">
    <requestURL>/ISAPI/Security/adminAccesses/capabilities</requestURL>
    <statusCode>4</statusCode>
    <statusString>Invalid Operation</statusString>
    <subStatusCode>methodNotAllowed</subStatusCode>
</ResponseStatus>

Any help would be greatly appreciated!

 

[Pavan ranganath]

Thanks for this, I was able to read the config and see that RTSP is disabled, but I am having trouble with the PUT command to update the config, I simply copied the entire XML and changed false to true for RTSP enable, however I am getting a 403 response.

<?xml version="1.0" encoding="UTF-8" ?>
<ResponseStatus version="1.0" xmlns="urn:psialliance-org">
    <requestURL>/ISAPI/Security/adminAccesses/capabilities</requestURL>
    <statusCode>4</statusCode>
    <statusString>Invalid Operation</statusString>
    <subStatusCode>methodNotAllowed</subStatusCode>
</ResponseStatus>

Any help would be greatly appreciated!

You cannot request update to the capabilities using PUT for URI "/ISAPI/Security/adminAccesses/capabilities"

Try this and you should be able to enable the RTSP

You can get the <ID> of RTSP in "/ISAPI/Security/adminAccesses/capabilities" URI.

 

[jersh]

You cannot request update to the capabilities using PUT for URI "/ISAPI/Security/adminAccesses/capabilities"

Try this and you should be able to enable the RTSP

You can get the <ID> of RTSP in "/ISAPI/Security/adminAccesses/capabilities" URI.

View attachment 182177

Thank you so much, with that I was able to start streaming RTSP.

I used Talend API Tester
PUT http://<IP>/ISAPI/Security/adminAccesses/3

body:

<AdminAccessProtocol version="1.0" xmlns="

http://www.std-cgi.com/ver20/XMLSchema

">
<id>3</id>
<enabled>true</enabled>
<protocol>RTSP</protocol>
<portNo>554</portNo>
</AdminAccessProtocol>

Hope that helps someone else