Categories
Knowledge Support Support exacqVision Server Categories Products

Explaining NTP

Time synchronization is an often overlooked concept in computer networking. The Network Time Protocol, also just shortened to NTP, is a network protocol and standard that allows distributed computers to synchronize their time.

Why is this important? Keeping proper time on computers, particularly when dealing with several computers communicating with each other, is important for things such as logging data and tracing of activity. On an NVR, perhaps the most important aspect is that of file system accuracy. Knowing when files were written or read is important to verify the when the activities in recorded video took place, as well as to perform forensic searches. Computer systems also need to know which version of files are most current for syncing files and performing file recovery. Time is also used by operating systems for many security and management controls, such as when using Active Directory/LDAP.

NTP consists of different tiers, originating from extremely accurate atomic clocks. These tiers are referred to as “stratum,” and measure the distance between systems in each tier and the atomic clocks in the top-most tier, deemed to be officially accurate. As the stratum number increases, the confidence of being synched to the most official time decreases. Primary time servers, such as time.nist.gov, pool.ntp.org, time.windows.com, time.google.com, and many others, are in Stratum 1.

When enabled, an NTP client like the NVR running your ExacqVision Server, begins a request from the NTP server.

Your system then automatically calculates the delay in the network link and uses the offset time (the offset time is based on the time zone setting you choose) and adjusts its own clock to the correct time and date.

If your system time is much different from the NTP source when this begins, it may take 5-10 minutes and several of these exchanges with the NTP source to initially bring the system clock into alignment with the NTP source. Once your system is synchronized it will continue checking for updates about every 10 minutes.

If you are experiencing problems communicating with an NTP source on the internet, you may need to investigate your firewall or antivirus settings. The exchanges made by the NTP protocol utilize UDP on Port 123.

<br>

How to check the Stratum level used on Windows

  1. Open a CMD window to reveal a CLI prompt.
  2. Enter the following command:
    C:\Windows\System32\w32tm.exe /query /status
  1. The stratum level can be seen on the second line of the results. The following example:

<br>

How to check the Stratum level used on Linux (Ubuntu)

  1. Open a Terminal window to reveal a CLI prompt.
  2. Enter the following command:
    ntpq -c rv
  1. The stratum level can be seen on row three of the results, as pictured in the example below:

<br>

Categories
Knowledge Support Support exacqVision Server

Incorrect Timestamps

Issue:

exacqVision Server may cause incorrect frame timestamps for some cameras that are using RtspPI or AxisPI plugins.

Workaround:

None

Version Affected

20.06.4 and earlier

Resolution:

A new Override is available for RtspPI and AxisPI

The Override will prevent the server from auto adjusting timestamps and will trust verbatim what comes from camera.

The server generates and caches a timestamp offset when starting a stream, which is applied to every frame as a time correction. Normally, the camera then continues to perform NTP sync operations with the server for timestamp accuracy.

However, with a busy network, some NTP packets may fail to arrive at the camera, and in some cases the camera’s time may drift beyond a 60 second threshold, which causes server to incorrectly adjust and freeze its cached offset, which will be applied to every frame regardless whether the camera successfully NTP syncs with server.

Most noticeable in multi-sensor cameras and encoders.

The new override is #timestamp=trusted

Version Fixed:

exacqVision Server 20.09.8

Related Link:

DVR ticket ​#d21835

Categories
Knowledge Support Support exacqVision Server Categories Products

Time Settings and Time Zone Information

Background Information

The Windows or Linux (Ubuntu) operating system time of your exacqVision Server host should be set to the local time and time zone where it is located.

It is often desirable to synchronize the system to a central time server, rather than rely on the internal clock of the recording server. There are many freely available time servers available online capable of providing reliable time references, such as:

  • pool.ntp.org
  • time.google.com
  • time.windows.com
  • time.nist.gov

These time servers communicate using the Network Time Protocol (NTP), using network port 123. For more information about network time servers, refer to the article Explaining NTP.

If your system is on an isolated network without access to the internet, or you prefer to provide your own source for time, many SOHO routers provide NTP capabilities, or you may choose to run an NTP service on another device or system of your own. <br><br>

Best Practice Configuration Steps

  1. With the exacqVision Desktop Client connected to your exacqVision Server instance, navigate to the Configure System node on the navigation tree along the left, then select the Date/Time tab from the top of the page.

    <br><br>
  2. The URL or IP address of the time server you choose to use will be entered into the Time Server field after checking the Enable Time Server checkbox. If the Enable Time Server box is left unchecked, the system will rely on its internal clock, which is not as reliable as the NTP sources mentioned above. <br><br>
  3. Your networked IP cameras should be synchronized to the time and date of the exacqVision Server. While it seems counterintuitive, you will log into your cameras to configure their time settings and set them to the GMT-0 time zone. Then enter the IP address or URL of your exacqVision Server as the Time Server in the camera’s settings.

    This will ensure that video sent to the exacqVision Server is recorded with a time code in reference to the Server time. For this reason, it is recommended to use the exacqVision Client’s on-screen display (OSD), to display the time and date overlay on your live video panels. If enabling the OSD within the camera instead, your time and date may display incorrectly because the exacqVision software has not accounted for your local time zone difference from GMT.<br><br>
  4. The IP Camera Time Server field shown at the bottom of the Date/Time tab within the exacqVision Client is not commonly used for most deployments. Enabling the override feature allows an administrator to enter the URL or address of another time server. The exacqVision Server will then inform connected IP cameras to refer to the entered address as it’s “source of truth” for time, rather than using the time shown on the exacqVision Server.

    NOTE: If using this feature, the cameras will require a network path to reach any address entered here, which may not be possible if your cameras reside on an isolated network or VLAN. <br><br>

Client Workstations

Client workstations running the exacqVision Client application should be configured to use the local time and time zone where they are located.

If they are remote users in a different time zone than the exacqVision Server, all times for live and searched video will be displayed in the client’s local time.

All video recorded by exacqVision is timestamped in Coordinated Universal Time, also known as UTC, so there is no ambiguity as to the absolute time when the video was recorded. In the exacqVision Client, the OSD display shows the server time zone as an offset from UTC with the timestamp. If the timezone is not configured for the OSD, the timestamp shown is the Client’s local time.

exacqVision ePlayer

Within the exacqVision ePlayer, the timestamp of the recorded video will display the timezone of the local computer on which it is playing, but will also show the time zone offset.

As an example, if you watch a video on a computer set to Eastern Daylight Time, you could see 9:00am (GMT-4:00), while the same video viewed on a computer set to British Summer Time would show 2:00pm (GMT+1:00). The UTC timestamp is the same in both cases.

Knowledge of the physical location of the recording server, which may be needed for evidentiary purposes, can be correlated to the local time of the machine on which video is being watched and the local time of the server on when it was recorded.<br><br>

exacqVision Edge/Edge+

This article applies to exacqVision Server software. For information on exacqVision Edge/Edge+ time settings, please refer to exacqVision Edge Time Zone Configuration.

<br>