Stephen Rhodes

Hello, Working with Onvif can be a frustrating experience as the standard is not well followed by camera makers. Just out of curiosity, I tested all of my cameras to see the response to the reboot command. Dahua - Success Hikvision - Success Amcrest - Success Axis - Success Foscam - Success Reolink - Success Lorex - Success HiKam - Success Trendnet - Success Utalert - Failure You could randomly select any Onvif parameter and find in this set of cameras at least one that does not properly implement...

Thank you for reaching out, sorry for your troubles. I can pretty much guarantee that this is an issue with the camera. Most cameras have improper implementation of onvif, so it not surprising that some functions don't work properly. As an aside, there is a more developed version of the program on github at https://github.com/sr99622/libonvif that includes a command line program and a GUI program for working with cameras. Best Regards, Stephen

Taking another look at your screenshot I notice that you are using Amcrest cameras. There are a couple of things that Ovif Device Manager does better with these cameras. One is the time setting regarding Daylight Savings Time. If the camera and the computer have different settings for DST, Amcrest will not respond. I think Onvif Device Manager has a routine that will test the camera with a modified time stamp to check for misalignment between the computer and the camera with regards to DST. You can...

Hi LH, Thank you so much for your message, I'm sorry to hear of the trouble. My best guess would be that there is some Windows firewall issue that is preventing libonvif from communicating over the network. It may not be immediately obvious as the library uses lower level UDP protocols which may be firewalled separately from standard TCP traffic. Libonvif uses messages which are virtually identical to Onvif Device Manager in most situations, so they should be able to communicate in much the same...

Hi Kevin, Thank you so much for your kind words, I'm glad you found the library to be useful. If I remember correctly, the fillRTSP command populates the data structure with the necessary tokens so that you can use other commands such as VideoEncoderConfiguration without further initialization. There is an existing copy of the code for libonvif on github if you would like to fork from there. My apologies for the late reply, I hadn't checked the comments for a while. If you need more help, feel free...

Hi Nathan, Thank you so much for your comment. It looks like you are pretty close, so you have probably figured this out already, my apologies for the late response. I think what you are looking for is the ./configure CPPFLAGS="-I/usr/include/libxml2" setting for the build. You can also get a lot of information from the ./configure --help command which will give you information about the settings needed for the program.

Hi Bruce, Thank you so much for your message, my apologies for the late reply. I have not implemented the event subscriber in the library. It certainly would be possible to add it, as I had gone through the exercise during the development process. The command to subscribe is the same format as for the other ONVIF commands. There are a number of issues with using this feature however, which dissuaded me from incorporating it into the release version. I found that many cameras do not have this feature....

Hi Bruce, Thank you so much for your message, my apologies for the late reply. I have not implemented the event subscriber in the library. It certainly would be possible to add it, as I had gone through the exercise during the development process. The command to subscribe is the same format as for the other ONVIF commands. There are a number of issues with using this feature however, which dissuaded me from incorporating it into the release version. I found that many cameras do not have this feature....