-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D-Link DCS-8635LH not working #284
Comments
Just to add to the report, ODM connects and displays video but ODM only handles Profile S and the Media1 APIs and ignores Media2 and H265. |
@RogerHardiman I didn't see the specs in ONVIF for Digest Authentication. This is the same SOAP protocol, I'm still at this point: #185 🙁
|
Hi Andrew. On the D-Link I think it is probably a bug that they are not doing WS-Security on the Media2 API. I have emailed D-Link to ask if I can loan a camera or get remote access to one. For #185 you can jump on to some of my cameras. But another good test is the RPOS project. That is an ONVIF server that runs on Linux (and Windows and macOS) and is good enough to be used in some commercial projects. |
I was asked to debug this ONVIF library not connecting to a D-Link DCS-8635LH camera.
It is a new model that implements Media20 and H265.
The ONVIF library connects to the camera and does some initial ONVIF message exchanges like GetSystemDateAndTime and GetServices calls.
Then it tries to do GetVideoSources and GetProfiles.
The GetProfiles seems to return a HTTP Status Code of "500" and replies with XML of
I can see that the GetVideoSources request goes via Media1 (Media10) and the GetProfiles request goes via Media2 (Media20).
This library sends authentication via WS-Security.
So I'm logging this in case any one else has had issues recently with D-Link CCTV cameras and this software library.
My hunch... D-Link have not implemented WS-Security in their Media2 API and I need to use Digest Authentication but that is an untested guess.
Log from the Constructor first connecting to the camera is...
The text was updated successfully, but these errors were encountered: