Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Digest auth #588
Well, it's a no go on my end. I tried Foscam, Grandstream, and USG cameras.
Error messages range from No RTSP sources, null RTSP response, or error 501 not implemented. For kicks I tried every single available option from the drop downs on both port 80 and 554.
Just noticed and fixed a mysql problem that was truncating the log. I'm back. And I'll post a more complete log entry shortly now that I have it.
From what I've seen, most of the newer Foscams seem to all support the following:
Seems they want to do the rtsp over the same port as http, which is 88 by default.
Ok, so I see your last post about mjpeg streams, but I'm using a h.264 stream.
Wireshark makes it pretty clear what is happening.
Using a source type of ffmpeg, zoneminder sends to the camera:
This causes the camera to do some sort of handshake by responding with what appears to be supported features:
Inspecting the packets further, zoneminder then sends credentials to the camera via digest authentication.
I don't know enough about RTSP to say anything other than this must be normal as the video stream works.
Using a source type of Remote with RTSP/Unicast, zoneminder sends:
which stops everything.
So, to put it in my own words, zoneminder appears to be cheating by just sending the wildcard * to the camera rather than sending the complete URL. I don't understand the purpose of why the camera wants its own URL parroted back to it, but that appears to be what is required in this case to get the camera to work.
Made some progress.
This made significant progress! I am now seeing the same kind of handshake I saw using the ffmpeg method. However, it appears I did not fix the mysql problem because as you can see from the last line, something is still causing the logger to say it can no longer write to mysql, which causes everything to stop. However, there no errors whatsoever in the mysql log.
UPDATE: Running another debug session where I didn't get the mysql error, the session stops with this line before zmc exits with status 255: