Recent content by Mickey Lane

I got this working. I cleaned up the code and used the entire rtsp URL when calculating the response MD5. Most of the sparse docs show just the relative part of the URL, not the absolute. I hope this isn't a camera by camera thing.

RTSP/1.0 401 Unauthorized CSeq: 3 Date: Wed, Sep 20 2017 17:29:01 GMT WWW-Authenticate: Digest realm="LIVE555 Streaming Media", nonce="98b33ca33f37f8738d6a2bce0b03ebf8"

Can I wake this topic up again with a different problem that deals with the same subject? I send an OPTIONS rtsp message to one camera and get the supported options back. I send it to another camera and get a 'unauthorized' and information for digest authentication. I've got most of it sorted...

Lesson learned. Thanks to all of you

Problem resolved thanks to several people and tools.. It turns out that Reolink cameras demand \r\n on the end of a line and SV3C works with only \n. Both return \r\n. SmartSniff bad (#2) and good (#4)

I set up Wireshark and muddled my way through capturing good and bad. I was having difficulty exporting just the parts I wanted so I just did a screen grab of the interesting parts of the display. Yeah, I know.. Anyway, here is 'good' (VLC) and 'bad' (my code). Aside from the ACK value of 73...

You probably didn't read this part: "The 'unauthorized' bit at the end is another thing I know how to deal with. I'm not getting that far yet." I'm not getting past "OPTIONS rtsp://192.168.1.147:554/h264Preview_01_main RTSP/1.0"

Here's the first bit of the VLC log. This is for the Reolink RLC-410 camera. The 'unauthorized' bit at the end is another thing I know how to deal with. I'm not getting that far yet. [01ec2604] logger interface: using logger. [01ec2604] logger interface debug: opening logfile `log.txt' Opening...

The 1st transaction is always with the RTSP port and I've verified that everyone is using 554. It's not using UDP or the URL would rtscu://...

That's a good suggestion on the Wireshark. Haven't used that for years. I'm familiar with the extra line breaks at the end of the messages (same as HTTP). I've tried with several variations. No diff.

I'm writing some code to set up cameras via RTSC. Both of the cameras I have are pretty crappy software wise: Reolink and SV3C. I can get VLC to log the access to both of the cameras OK and I duplicate the OPTIONS transaction exactly as VLC does it. With my code, the SV3C works, the Reolink just...

Same results. Most of the camera's 'features' don't work. VLC will talk to it nicely with "rtsp://192.168.1.150:554/11" but I don't particularly want the SV3C PC software on my system so I didn't try it more than once. Firefox won't show the video. Chrome will (at least on my Android cell). IE...

The branch was only visible when I had the camera on the ladder. No vegetation is visible in its current location.

I mounted the varifocal camera on a stepladder so I could mess with it and the Xeoma software I'm trying. The pics with the golf cart (day + night) are from that setup. The pics looking down on the street (day + fogged night) are from the mounted camera. It's my guess that the white metal beam...