RSTP DVR VideoURL

Other Devices & Integrations Door Locks & Sensors
1

Hello,

I’m trying to setup my DVR, and no success after a couple of hours…

This URL works fine on Quicktime: rtsp://192.168.1.135:32554/user=xxxx&password=yyyy&channel=5&stream=0.sdp?real_stream–rtp-caching=100

At vera (Generic IP Camera), I have set this:

ip: 192.168.1.135:32554
VideoURLs: rtsp,0,mjpeg,m,640,480,qaiw:user=xxxx&password=yyyy&channel=5&stream=0.sdp?real_stream–rtp-caching=100

URL,DirectStreamingURL, username, password: all blank.

When I click on ‘View’ of camera device, I get a box with ‘Starting Streaming’, but nothing happens after that…

Thanks
Ricardo

2

Bump… No one?

3

I don’t believe Vera supports RTSP cameras at this time.

One solution I can suggest is, when you have a spare Windows PC, to get the Blue Iris software and use the Blue Iris plugin (micasaverde App store) to link that to Vera. BI supports a large number of cameras and does have RTSP and ONVIF support. I am in the process of transferring all my IP camera’s from Vera to BI and link them using the BI plugin as that’s been very stable for me the last few weeks since I installed it.

4

Thanks for the reply. Are you really sure RTSP isn`t supported? I found so many posts, like this one http://forum.micasaverde.com/index.php/topic,25201.msg178070.html#msg178070 , so I assumed RTSP is supported (I have UI5).

Thanks anyway
Ricardo

5

@rvendrame
A lot of these cameras have secondary channels that support jpeg or mjpeg or similar. If you can find this channel you can use it on the Vera. As far as RTSP goes on the Vera I think the decoding overhead would be to much for the processor.

Caveat: I am no expert on this just played with a 3mp ONVIF camera recently where I managed to find the secondary snapshot channel.

Cheers

John

6

@john,

Thanks. Any hint to find the secondary channel? I got the RTSP URI from the DVR web page, and that is all I could get. I tried wireshark tracing over vMeye app, but all traffic is pure TCP so it is a bit difficult to my knowledge…

Thanks again

7

No idea really as they are all different, mine is http:///cgi-bin/snapshot.cgi?stream=0, can’t remember the brand but it is based on the TI DaVinci DM368 DSP.

By the way I thing my statement about second stream is wrong this is something else again.

Edit:If the camera is ONVIF compliant than you can find the info via queries to the camera.

8

[quote=“rvendrame, post:6, topic:181944”]@john,

Thanks. Any hint to find the secondary channel? I got the RTSP URI from the DVR web page, and that is all I could get. I tried wireshark tracing over vMeye app, but all traffic is pure TCP so it is a bit difficult to my knowledge…

Thanks again[/quote]

Your best bet would be the manufacturer of your DVR. They should be able to provide you with all available URI’s and teh specs for each.

9

If you have a ONVIF compatible security camera the following may help: -

Create file named getProfiles.xml with the following: -

<?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:trt="http://www.onvif.org/ver10/media/wsdl"> <soap:Body> <trt:GetProfiles/> </soap:Body> </soap:Envelope>

  1. Run the following curl command: -
curl http://<INSERTIPADDRESSHERE>/onvif/device_service --data @getProfiles.xml |xmllint --pretty 1 -

This should list all the profiles on that camera. Choose the profile that you are interested in, for me it is MainStream: -

<trt:Profiles fixed="false" token="MainStream">
  1. Create file named getSnapshotUri.xml with the following: -

<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:tt="http://www.onvif.org/ver10/schema"> <soap:Body> <trt:GetSnapshotUri> <trt:ProfileToken>MainStream</trt:ProfileToken> </trt:GetSnapshotUri> </soap:Body> </soap:Envelope>

Where ProfileToken = token from previous response.

  1. Run the following curl command: -
curl http://<INSERTIPADDRESSHERE>/onvif/device_service --data @getSnapshotUri.xml |xmllint --pretty 1 -

Hopefully you will get something like this: -

<SOAP-ENV:Body> <trt:GetSnapshotUriResponse> <trt:MediaUri> <tt:Uri>http://192.168.0.205:80/cgi-bin/snapshot.cgi?stream=0</tt:Uri> <tt:InvalidAfterConnect>false</tt:InvalidAfterConnect> <tt:InvalidAfterReboot>false</tt:InvalidAfterReboot> <tt:Timeout>PT0H12M0S</tt:Timeout> </trt:MediaUri> </trt:GetSnapshotUriResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

If you want to file the RTSP stream: -
Create file named getStreamURI.xml with the following, using same token or token from another profile: -

<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:tt="http://www.onvif.org/ver10/schema"> <soap:Body> <trt:GetStreamUri> <trt:StreamSetup> <tt:Stream>RTP-Unicast</tt:Stream> <tt:Transport> <tt:Protocol>UDP</tt:Protocol> </Transport> </trt:StreamSetup> <trt:ProfileToken>MainStream</trt:ProfileToken> </trt:GetStreamUri> </soap:Body> </soap:Envelope>

Then run the following curl command:-

[code]curl http:///onvif/device_service --data @getStreamURI.xml |xmllint --pretty 1 -

[/code]

This was done under linux so not sure if the same will work under windows. Hopefully this helps somebody.

10

zoot1612,

Thanks but I don’t think my device id ONIF. I get an “(23) Failed writing body” at the first curl. For the second curl, I get an HTML file back, but it says “404 File Not Found”

Thanks anyway