[Live-devel] openRTSP on an h.264 8 channel H264DVR 1.0

Discussion:

Dave Buchanan

2015-12-18 06:03:24 UTC

Hi people
First of all thank you for providing the software, which I think is exactly what I am looking for
I have the DVR in a remote location and I wish to take an image every minute or so and upload it to a server, this way if the remote location is compromised we have the latest images available
I am currently running on mac osx and I have 8 channel DVR
I have compiled the code as instructed using the macosx config
Unfortunately I have fallen at the first hurdle, I have searched hi and low for answers alas the only ones I have found do not deal with the 451 issue
For your information I am a software developer with years of C experience and a little of C++ happy running things on Linux etc
I think I am missing something very obvious
please help
Mane thanks in advance Dave
below are my results for the simplest of commands
I then tried the -o option
./openRTSP -o rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin>
Opening connection to 192.168.0.103, port 554...
...remote connection opened
Sending request: OPTIONS rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin> RTSP/1.0
CSeq: 2
User-Agent: ./openRTSP (LIVE555 Streaming Media v2015.11.09)
Received 121 new bytes of response data.
RTSP/1.0 200 OK
Server: H264DVR 1.0
cseq: 2
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, GET_PARAMETER, PLAY, PAUSE
RTSP "OPTIONS" request returned: OPTIONS, DESCRIBE, SETUP, TEARDOWN, GET_PARAMETER, PLAY, PAUSE
Daves-Mac-mini:testProgs dave$
-----------
./openRTSP rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin>
Opening connection to 192.168.0.103, port 554...
...remote connection opened
Sending request: OPTIONS rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin> RTSP/1.0
CSeq: 2
User-Agent: ./openRTSP (LIVE555 Streaming Media v2015.11.09)
Received 121 new bytes of response data.
RTSP/1.0 200 OK
Server: H264DVR 1.0
cseq: 2
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, GET_PARAMETER, PLAY, PAUSE
Sending request: DESCRIBE rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin> RTSP/1.0
CSeq: 3
User-Agent: ./openRTSP (LIVE555 Streaming Media v2015.11.09)
Accept: application/sdp
Received 52 new bytes of response data.
RTSP/1.0 451 ERROR
Server: H264DVR 1.0
cseq: 3
Failed to get a SDP description for the URL "rtsp://192.168.0.103/username=admin <rtsp://192.168.0.103/username=admin>": 451 ERROR

Ross Finlayson

2015-12-18 07:10:19 UTC

Permalink

./openRTSP rtsp://192.168.0.103/username=admin

[…]

RTSP/1.0 451 ERROR
Server: H264DVR 1.0
cseq: 3

The error “451” (returned by the server) means “Bad Parameter”. This suggests that adding “username=admin” to the URL may have been a mistake.

Instead, I suggest trying
./openRTSP -u admin <password> rtsp://192.168.0.103/
where <password> is the password that you need for user “admin”. (If there’s no password, then use “” instead.)

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/

Ralf Globisch

2015-12-18 07:25:04 UTC

Permalink

--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.

Please consider the environment before printing this email.

./openRTSP -o rtsp://192.168.0.103

Ross Finlayson

2015-12-19 09:42:35 UTC

Permalink

It depends on the server. Including “<username>:<password>@“ in the RTSP URL is a bad idea (because it causes the username and password to be sent over the net ‘in the clear’. But some servers require this. Other, more sensible servers implement authorization using ‘Digest Authentication’ - which does not pass the username and password over the net.

Giving the “-u <username> <password>” option to “openRTSP” gives the RTSP client the information that it needs to do Digest Authentication, if the server requests it.

So, if you’re not sure what the server requires, then you should use the "-u <username> <password>” option, but perhaps also try including the username (and password if necessary) in the URL.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/