Accessing rtsp of Cameras Managed by NVR

[atclaus]

I had a local company install an LTS NVR and cameras. Works well. Cameras are connected to the NVR for PoE and to act as the switch. NVR is connected to my router via LAN port and assigned a static IP by the router.

Is it possible to access the RTSP feeds from a computer connected to my router? My real goal is to use Rpisurv.

I have tried a variety of rtsp commands and none of them work. So then I tried pinging the camera IP addresses to see if I could even talk with them, and my pings fail. Should I be able to ping my cameras?

NVR configuration says that I can access cameras at 192.168.107.2:65001, :65002 etc so I tried a variety of rtsp with those ports but to no avail.

NVR: LTN8816K-P16 16 channel NVR
Cameras: CMIP3042 4.1MP turret

Router: 192.168.107.1
NVR on router: 192.168.107.2 (static)
NVR internal: 192.168.1.1
camera1 per NVR: 192.168.1.2
camera2 per NVR: 192.168.1.3 and so on

Thank you!

 

[alastairstevenson]

Is it possible to access the RTSP feeds from a computer connected to my router?

Certainly for Hikvision NVRs, and therefore presumably for yours.
On the older firmware (3.0.8 or so) Hikvision NVRs supported the ONVIF NVT facility, so could be queried by ONVIF Device Manager, but this facility is no longer active. But worth checking on your NVR.

Quite a few posts on the topic for Hikvision, example:
Hikvision DS-7616NI-SE/P QNAP TS-251 and Asus RT-AC68U router. NVR theft.

I have tried a variety of rtsp commands and none of them work. So then I tried pinging the camera IP addresses to see if I could even talk with them, and my pings fail. Should I be able to ping my cameras?

Your cameras are on the separate network that NVR PoE ports use, by default that is not accessible from the LAN.
However -

NVR configuration says that I can access cameras at 192.168.107.2:65001, :65002

this implies that your NVR has a 'Virtual Host' facility, in which case a couple of configuration tweaks would allow direct access to the cameras at their actual 192.168.1.x address
The changes to experiment with would be:
Using the Virtual Host access, change a camera default gateway to match the NVR PoE interface IP address of 192.168.1.1
Change the corresponding NVR channel to 'Manual' instead of 'Plug&Play' to stop the NVR changing it back.
Add a 'static route' to your router, something like :
"For network 192.168.1.0/24 (ie subnet mask 255.255.255.0) route packets via the NVR LAN interface IP address of 192.168.107.2"

Then to test, ping the camera at it's actual IP address of 192.168.1.2, point the browser at it, try the camera RTSP stream with VLC etc.

 

[fvhjof]

I think buying NVR with POE ports is a mistake. You can save some $ and buy NVR without POE output and buy POE switch for cameras. Each camera will have its own IP in your network and you can easily access it. Also you don't have to plug cameras to NVR which gives you the opportunity to put NVR near your TV and use it as HDMI output.

 

[skybeorn]

You need to access the Recorder RTSP stream not the cameras. The cameras are in a different subnet. Your RTSP should look like this:
rtsp://NVRuser:NVRPWD@RecorderIP:RTSPPORT/Streaming/Channels/102

so it would like this
Main Stream: (Channel 1 Main)
rtsp://admin: password@192.168.1.200:554/Streaming/Channels/101
Sub Stream: (Channel 6 Substream)
rtsp://admin: password@192.168.1.200:554/Streaming/Channels/602

 

[zero-degrees]

I think buying NVR with POE ports is a mistake. You can save some $ and buy NVR without POE output and buy POE switch for cameras. Each camera will have its own IP in your network and you can easily access it. Also you don't have to plug cameras to NVR which gives you the opportunity to put NVR near your TV and use it as HDMI output.

That sir, is an opinion. POE NVR's work great for a lot of people. This setup allows for easy plug and play configuration and also easily isolates your video traffic from your network. A lot of times people purchase stand alone NVR's and connect cameras into their networks but do not understand VLANs or how to segment video traffic. These users have limited network abilities and then get upset when they have problems with smooth video. But they are the ones running video through a gateway and a few switches that also do 100 other tasks in the users home and do not have QOS configurations either.

ALL HIKVision and LTS hardware allow direct access to each camera via the virtual host which also allows setup and configuration or changes on the fly. Further more, placing an NVR close to your TV is a poor idea in a lot of cases as anyone entering a home to rob it will basically be standing on top of it when they pickup your flat screen and DVD player. There are a number of ways to get your NVR video to your TV's in your home without having your NVR sitting by it.

In the end this is a Ford vs Chevy conversation just like HIK or Dahua. However, I would say a lot of people that go the non intigrated route still setup their network poorly.

 

[alastairstevenson]

You need to access the Recorder RTSP stream not the cameras. The cameras are in a different subnet.

True - but the cameras are still easily able to be accessed, as per the method above.

 

[skybeorn]

True - but the cameras are still easily able to be accessed, as per the method above.

Followed your directions, but maybe I am missing something here?

Set the camera to Manual instead of plug and play.

Made sure Default gateway on the camera was the recorders integrated switch default gateway(192.168.254.1).

Put the static route as described into my Asus RT-AC5300.

I can ping the camera IP, but have no functionality in VLC, no access via browser, and no access via ivms.

 

[alastairstevenson]

Well, your settings certainly look OK.
And you can ping the target address, suggesting the routing and access is working.

The method has worked fine for quite a few others.
What model of NVR are you using, and what version of firmware?
Way back, before 'Virtual Host' was an available feature on the NVR, to get access to PoE-connected cameras I enabled the Linux kernel 'IP_forward' facility within the NVR, using a shell access to configure it. It was necessary to change the camera's HTTP port away from 80 as the NVR was 'swallowing' port 80 traffic. But when Virtual Host became available, neither of those changes was needed any more.

By any chance do you have / use nmap?
Maybe try a simple 'nmap <camera_IP_address> to see what results.

Alternatively, as an experiment, at a Windows command prompt, try a telnet access to the camera ports, eg
telnet <camera_IP_address> 80
and 554 and 8000
and see if any of them connect.
Example on my 7816N-E2/8P NVR (the Hikvision camera on 254.12 HTTP port is still away from 80 from when I changed them ages ago).

alastair@PC-I5 ~ $ nmap 192.168.254.12

Starting Nmap 7.01 ( https://nmap.org ) at 2017-06-06 20:15 BST
Nmap scan report for 192.168.254.12
Host is up (0.0012s latency).
Not shown: 991 closed ports
PORT     STATE    SERVICE
22/tcp   open     ssh
23/tcp   filtered telnet
90/tcp   open     dnsix
443/tcp  open     https
554/tcp  open     rtsp
7001/tcp open     afs3-callback
8000/tcp open     http-alt
8200/tcp open     trivnet1
9010/tcp open     sdr

Nmap done: 1 IP address (1 host up) scanned in 1.36 seconds
alastair@PC-I5 ~ $ nmap 192.168.254.16

Starting Nmap 7.01 ( https://nmap.org ) at 2017-06-06 20:53 BST
Nmap scan report for 192.168.254.16
Host is up (0.013s latency).
Not shown: 995 closed ports
PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
554/tcp  open  rtsp
787/tcp  open  qsc
8000/tcp open  http-alt

Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds
alastair@PC-I5 ~ $ nmap 192.168.254.18

Starting Nmap 7.01 ( https://nmap.org ) at 2017-06-06 20:53 BST
Nmap scan report for 192.168.254.18
Host is up (0.011s latency).
Not shown: 994 closed ports
PORT     STATE SERVICE
80/tcp   open  http
406/tcp  open  imsp
443/tcp  open  https
554/tcp  open  rtsp
787/tcp  open  qsc
8000/tcp open  http-alt

Nmap done: 1 IP address (1 host up) scanned in 0.20 seconds
alastair@PC-I5 ~ $

 

[atclaus]

You need to access the Recorder RTSP stream not the cameras. The cameras are in a different subnet. Your RTSP should look like this:
rtsp://NVRuser:NVRPWD@RecorderIP:RTSPPORT/Streaming/Channels/102

so it would like this
Main Stream: (Channel 1 Main)
rtsp://admin: password@192.168.1.200:554/Streaming/Channels/101
Sub Stream: (Channel 6 Substream)
rtsp://admin: password@192.168.1.200:554/Streaming/Channels/602

Thanks skybeorn. That worked. The LT Security uses 8554 port but I was also missing the last 01/02. Thanks!

Add a 'static route' to your router, something like :
"For network 192.168.1.0/24 (ie subnet mask 255.255.255.0) route packets via the NVR LAN interface IP address of 192.168.107.2"

Thanks alastairstevenson. My router has a very basic interface (Amplifi - great for large area reception, but a dud on control). Will have to talk with their tech support to see if I can get that to work.

 

[atclaus]

Just contacted router support. Amazingly got an immediate response. Do not support static routes so cannot try that functionality out. But I got it working so I am happy! Thanks everyone

 

[skybeorn]

NVR Model: DS-7604NI-K1/4P
FW version: 3.4.92 B170220

Starting Nmap 7.40 ( https://nmap.org ) at 2017-06-07 11:23 Eastern Daylight Time
Nmap scan report for 192.168.254.5
Host is up (0.0091s latency).
Not shown: 994 closed ports
PORT      STATE    SERVICE
22/tcp    filtered ssh
80/tcp    open     http
554/tcp   open     rtsp
8000/tcp  open     http-alt
8200/tcp  open     trivnet1
49152/tcp open     unknown
Nmap done: 1 IP address (1 host up) scanned in 14.80 seconds

No luck on telnet.

 

[alastairstevenson]

Will the nmap looks like a normal Hikvision set of ports.
That looks like it should work.

 

[skybeorn]

Will the nmap looks like a normal Hikvision set of ports.
That looks like it should work.

Was able to get the stream on a Linux box via VLC, so it must be something windows related that's blocking it. (web page up too)

 

[TJ01]

If you have an Apple TV you can view the multiple feeds through the rtsp settings mentioned above through the app webcam hq. I have the four cameras onscreen.
E.g. 192.168.0.10:554/streaming/channels/102
101 would be the main feed for camera 1
102 would be the sub stream for camera one.
The sub stream works best for showing the 4 cameras.

 

[3base]

Was able to get the stream on a Linux box via VLC, so it must be something windows related that's blocking it. (web page up too)

hey all,
skybeorn, u running a VPN client on the windows box?
if so, disable it, and try again?

 

[skybeorn]

hey all,
skybeorn, u running a VPN client on the windows box?
if so, disable it, and try again?

Not running a VPN client or anything. Not sure what it was.