Hi,
You will most probably save time by using at last a windows VM to use the ActiveX control for the camera.
If you like adventures, the camera is probably onvif capable, so you might be able to retrieve its capabilities with SOAP requests.
for my camera the service entrypoint is:
http://192.168.0.31/onvif/device_serviceSo, you can create the following script: CallOnvif.sh
curl -s http://"$1"/onvif/device_service --data '<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"'"$2"'><soap:Body>'"$3"'</soap:Body></soap:Envelope>'|xmllint --pretty 1 -
Then, discover profiles like this:
./CallOnvif.sh 192.168.0.31 ' xmlns:trt="http://www.onvif.org/ver10/media/wsdl"' '<trt:GetProfiles/>'
And finally get the snapshot URI, like this (place profile name in call, instead of "profile0_1"):
./CallOnvif.sh 192.168.0.31 ' xmlns:trt="http://www.onvif.org/ver10/media/wsdl"' '<trt:GetSnapshotUri><trt:ProfileToken>profile0_1</trt:ProfileToken></trt:GetSnapshotUri>'
For instance, for my camera:
http://192.168.0.31:80/cgi-bin/anv/images_cgi?channel=0&user=root&pwd=zob