There can be connectivity problems between the individual parts of the Video API whenever there are process boundaries. The overview diagram shows the different components of the Video API together with a VMS and a consumer.
For communication the following is required:
- All machines (VMS, Recording Server, Video API Server, etc.) are time-synchronized via NTP or a similar approach.
- Firewall rules are in place so that the external Video API port is reachable.
- All VMS ports need to be reachable from the Video API server (see the Guide of the VMS, for Siveillance Video refer to the Admin Manual).
- The user account for Video API needs sufficient permissions in the VMS (for Siveillance Video this is done via Roles).
- Log files usually point towards if and where the connection problem is. Also always make sure to check for a proxy (including NO_PROXY bypass settings).