Closed chomooho closed 6 years ago
New version use gsoap based onvif, could you help capture package by wireshark let us compare
Sorry, I don’t use Wireshark. I can give you VidStor console message.
I captured packets by Wireshark.
From the wireshark package, the client fin the tcp connect because the server does not give the ACK, and the client need optimize some parameter for this, which camera model or can you map the camera to internet let us do some remote connect debugging?
I have try to fix, please update the code & try again. https://github.com/veyesys/rapidvms/commit/cd035015e63b636a99817cf80d0d223ab6ae3080
After changing the onvif timeout values, 3 cameras are working. 192.168.1.48, 192.168.1.78, 192.168.1.74 are working. But one camera is still not connected with onvif. This camera is /192.168.1.97:80/onvif/device_service. The camera model is Samsung SND-6084R. The followings are the console messages and captured packets by Wireshark.
Does the time of camera is same with the pc rapidvms run on ?
After setting the time of camera, the camera status is changed to green color from gray. But the live view is not appeared as follows: The followings are captured packets by Wireshark.
But in rapidvms-r2.0.7, /192.168.1.97:80/onvif/device_service is connected. In order to reduce the captured packet file size for Web upload, I connect only one camera.
The following file is captured packets by Wireshark in rapidvms-r2.0.7. 2.07onvif170828-1435 (2).zip
In rapidvms-r2.0.7, adding cameras with ONVIF (port 2000) is working.
But in rapidvms-r4.2, adding cameras with ONVIF (port 2000) is not working.
I used the same test environment for two versions. Please check the errors.