Issue
Some ONVIF cameras report motion by means of a “pull-point” connection separate from the streaming video connection. If the camera unexpectedly closes the motion status connection, the server will retry the connection in order to reacquire motion status. When this happens, the corresponding server log messages will resemble:4/27/2020 02:59:38.464 AM onvifnvcPI Error http://172.19.232.75:80/onvif/subscribe_service: pull point socket exception.4/27/2020 02:59:38.464 AM onvifnvcPI Verbose http://172.19.232.75:80/onvif/subscribe_service: Timeout triggered.4/27/2020 02:59:38.464 AM onvifnvcPI Verbose http://172.19.232.75:80/onvif/subscribe_service: Pull point is now UNINITIALIZED4/27/2020 02:59:38.464 AM onvifnvcPI Verbose 172.19.232.75: Pull point needs to be initialized
When we finally abandon retries, we omit the “Pull point needs to be initialized” log message.
However, if a camera repeatedly closes the motion status connection due to firmware defects or other unknown issues, this can cause excessive server log error messages. In exacqVision Server 5.4.0, this retry behavior was limited to 6 attempts, in order to reduce logging.
Unfortunately, some ONVIF cameras are known to periodically timeout the motion connection, with the expectation that servers should periodically re-establish a “fresh” motion status connection. In such case, the server appears to show live video but no motion flag, and in turn, motion recording will cease.
Depending on the particular ONVIF camera, this symptom can occur after minutes, hours, or longer.
<br>
Workaround
Use continuous recording or upgrade.
<br>
Resolution
Fixed in exacqVision Server version 20.03.119
<br>
Version Affected
exacqVision Server lower than 20.03.119
<br>
Version Fixed
exacqVision Server 20.03.119
<br>