Hello,
I was very excited to find your library and the build process under windows was flawless. I am certain that the lib works well based on other comments . Unfortunately, I have not been able to get the test program to find any cameras. I'm using windows 10 and I compiled with VS2017. I use the Onvif Device Manager and it finds quite a few cameras on my network. What could be the issue? I will be moving on to Unix to test the lib soon. Just though I'd run my windows experiences by you... I've attached a screenshot in case it's of any use.
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 way.
Hopefully you have been able to resolve the issue on your own, my apologies for the late reply, I hadn't check the message board for a while.
Best Regards,
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your reply, no worries on the timing... I have all firewalls disabled, in fact I created a small network that only included a router, my computer and 1 onvif camera and still nothing. This is not an urgent issue, I'll dig into the code further and see if I can isolate the problem.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 overcome this issue by insuring that the computer and camera are synchronized.
Another issue with Amcrest is that they will sometimes respond to the discovery broadcast with a 169. IP address as the first address, which is invalid. This is from cameras that have wireless and wired connections available. Rebooting the camera will put the valid IP address first in the discovery response. libonvif only checks for the first address.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Just wanted to let you know that I solved the issue. I have 2 network connections on my computer, wired and wireless, both of which get an ip address and the test program was selecting the wifi interface which a different subnet than the cameras are on. Once I turned my wifi off, all the cameras were found and everything worked well. Sorry for the confusion
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I was very excited to find your library and the build process under windows was flawless. I am certain that the lib works well based on other comments . Unfortunately, I have not been able to get the test program to find any cameras. I'm using windows 10 and I compiled with VS2017. I use the Onvif Device Manager and it finds quite a few cameras on my network. What could be the issue? I will be moving on to Unix to test the lib soon. Just though I'd run my windows experiences by you... I've attached a screenshot in case it's of any use.
Thank
LH
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 way.
Hopefully you have been able to resolve the issue on your own, my apologies for the late reply, I hadn't check the message board for a while.
Best Regards,
Stephen
Thanks for your reply, no worries on the timing... I have all firewalls disabled, in fact I created a small network that only included a router, my computer and 1 onvif camera and still nothing. This is not an urgent issue, I'll dig into the code further and see if I can isolate the problem.
Thanks
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 overcome this issue by insuring that the computer and camera are synchronized.
Another issue with Amcrest is that they will sometimes respond to the discovery broadcast with a 169. IP address as the first address, which is invalid. This is from cameras that have wireless and wired connections available. Rebooting the camera will put the valid IP address first in the discovery response. libonvif only checks for the first address.
Hello,
Just wanted to let you know that I solved the issue. I have 2 network connections on my computer, wired and wireless, both of which get an ip address and the test program was selecting the wifi interface which a different subnet than the cameras are on. Once I turned my wifi off, all the cameras were found and everything worked well. Sorry for the confusion