The standard syntax to specify a user name and/or password is:
"rtsp://:@
So you could try ./openRTSP -o rtsp://admin@192.168.0.103
>>> Dave Buchanan 12/18/15 8:51 AM >>>
>
>
>>
>> Hi people
>>
>> First of all thank you for providing the software, which I think is exactly
>> what I am look
>>> ./openRTSP rtsp://192.168.0.103/username=admin
[…]
>>> Received a complete DESCRIBE response:
>>> 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 mist
>
>
>>
>> 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
>>I have an application that has its own event loop when manipulating/reading
>>sockets
So it sounds like you would like to use your event loop with the live555
library. I have some experience here. I was able to get libuv event loop and
live555 work together. You should be able to do the sa
> I have an application that has its own event loop when manipulating/reading
> sockets, however, I'd like to use live555 to do the rtsp negotiation process
> with the cameras.
Unfortunately, I’m not quite sure what you mean when you say that your
application “has its own event loop when manipu
Hi Ross,
Thanks for your quickly replay again.
Yes, according to your suggestion.
fDurationInMicroseconds = 256*100/ 16000 = 16000
The 16000 is same with what I mention early.
So, I am very confusing about the audio vibration.
Thanks a lot.
regards, eric, 12/17
__
Dear List,
I have some absolute newbie questions.
I have an application that has its own event loop when
manipulating/reading sockets, however, I'd like to use live555 to do the
rtsp negotiation process with the cameras.
I also need my own step-to-step control over the rtsp negotiation
proces
> Each time, we will put 1024 bytes to ulaw encode and it produce 512 bytes
> ulaw data out.
> Then we copy 512 bytes to fTo and put 512 to fFrameSize.
> For fDurationInMicroseconds, we set 16000.
> I think it should be right. But I don’t know why 16K, stereo audio is not
> working.
Note that, f
Hi Ross,
Thanks for your quickly reply.
Each time, we will put 1024 bytes to ulaw encode and it produce 512 bytes ulaw
data out.
Then we copy 512 bytes to fTo and put 512 to fFrameSize.
For fDurationInMicroseconds, we set 16000.
I think it should be right. But I don’t know why 16K, stereo audio
Remember also to pass the correct “numChannels” parameter to your call to
“SimpleRTPSink::createNew()” (presumably in your “createNewRTPSink()”
implementation). For mono, it will be 1 (its default value); for stereo, it
will be 2.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
__
10 matches
Mail list logo
