Categories
Knowledge Support Support exacqVision Server Categories Products

Override to Prevent UTC Time Zone Configuration of Vivotek Cameras by the Server

Issue:

Adding a camera, disabling or re-enabling the camera, power cycling the camera, restarting the exacqVision server service, or rebooting the exacqVision Server, causes the server to set the camera’s time zone, for all cameras that allow it, to Coordinated Universal Time (also known as Universal Time Coordinated, UTC, UTC+0, UTC+00:00, “Z time”, or “Zulu Time”).  This is preferred for global video recording and playback time synchronization because UTC does not observe Daylight Savings Time (DST) changes.  This camera configuration change is therefore normal, desired, and expected behavior for video management as a whole.  However, if the expectation is that the camera’s on-screen display (OSD) must display the local time for video clip exportation in MPEG-4 (MP4) format, changing the camera’s time zone or turning off the camera’s OSD negatively impacts this use-case.

An override switch is now available for cameras that make use of the Vivotek IP camera plugin (VivotekPI).

The override will prevent the server from setting the time zone on the camera to UTC+0 as would normally occur. This will only affect the camera’s internal timekeeping and its corresponding on-screen display (OSD).  The exacqVision Server’s OSD will remain unaffected and be subject to its own internal clock time zone setting.

Override commands:

To prevent the server from setting the camera’s time zone and Daylight Savings Time (DST), use:    

ipaddress#timezone=camera

Example: 192.168.1.168#timezone=camera

To allow the server to set the camera’s timezone to UTC+0 (same as default):

ipaddress#timezone=utc

Example: 192.168.1.168#timezone=utc

How to use:

For a camera to be added to the exacq Server, append the #timezone=camera override command to the Hostname/IP address field of the exacqVision Client > Add IP Cameras > IP Camera Information section.  On an already connected camera, add the override to the existing camera Hostname/IP address entry, set the camera timezone through the camera’s webpage interface, and allow the camera to reconnect.

Explicitly adding the #timezone=utc override command to the Hostname/IP address field of the exacqVision Client > Add IP Cameras > IP Camera Information section or simply removing the override command from an existing camera Hostname/IP address entry will immediately cause the camera to reconnect and be set to UTC+0 by the server.

Workaround:

None available.

Version Fixed:

Development build 21.09.2900400.0.

Expected Future Release build 21.12.0.

Categories
Knowledge Support Support exacqVision Client Categories Products

Vivotek factory default codec is set to SVC

Some Vivotek camera factory defaulted codec is SVC (Scalable Video coding) which is an extension of H264 that we do not support. When the camera is in this mode, the plugin fails to stream video and stays in the “connecting” state. Also were not be able to change the codec setting from the client. The only work around is to go to the camera’s web page change the codec to H264/jpeg and reconnect the camera from our client. This affects model IP8162.

<br>

Detail on SCV video here https://en.wikipedia.org/wiki/Scalable_Video_Coding.

Categories
Knowledge Support Support exacqVision Server

Vivotek Cameras Fail to Connect “Connection error (403)”

Description 

Some Vivotek cameras require Basic Authentication.  This should be indicated in the Notes section of the cameras test record.  The camera will not connect if digest authentication is selected.

Product 

  • Vivotek IP Cameras
  • exacqVision Server

Steps to Reproduce 

  • Add a Vivotek Camera

Expected Results 

  • Camera connects

Actual Results 

  • The camera does not connect and a connection error “Connection error (403)” is returned
Sample from exacqVision Server Logs

Solution

  • Disable the camera in the exacqVision Client
  • Access the camera configuration page via a web browser
  • Navigate to Network > Streaming Protocols > Authentication
  • Change Authentication from digest to basic for both HTTP and RTSP protocols
  • Navigate to Security > Miscellaneous
  • Uncheck  the Enable Cross-Site Request Forgery (CSRF) protection option
  • Save the changes
  • Reboot the camera
  • Access the camera configuration page via a web browser
  • Navigate to Network > Streaming Protocols > Authentication
  • Verify the authentication mode is set to basic
  • Navigate to Security > Miscellaneous
  • Verify CSRF is not enabled
  • Enable the camera in the exacqVision Client

Important: The camera seems to require a reboot to fully apply the change in authentication mode.

Categories
Knowledge Support Support exacqVision Server Categories

IP Plugin Overrides

The standard form for exacqVision camera addresses is as follows:

{host}{?parameter_1=value_1}…{?parameter_n=value_n}{#override_1=value_1}…{#override_n=value_n}

  • The host is required and must be in the format of an IPv4 address or FQDN (dot separated domain location).
  • The 1 or more name=value parameters are separated by ? and are optional. These are passed to the device.
  • The 1 or more name=value overrides are separated by # marks and are optional, but always last. These are passed to the plugin to modify plugin behavior.

<br><br>

Overrides

PluginOptionUsage
ACTitransport=httpHTTP stream support for legacy platforms and user data
ACTitransport=rtspRTSP stream with separate metadata socket for motion/input trigger/video loss/etc.
Axiszoom=configBy default zoom only cameras support.
Axiszoom=operationForce zoom only operation and controls as part of PTZ and live view.
Axisblocksize=offOn by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues.
Axistransport= {udp,tcp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Axistunnelport={1025-65535}Override for tunnel port when not the same as CGI port. Use as a workaround for only having 1 port input box/XML attribute.
Axistimestamp={server,trusted}Override timestamp to server time(server) for problem cameras or to camera adjusted by RTSP/RTCP per RFC(trusted)
Arecontnone
Dahuatransport= {udp,tcp,rtsph}Transport overrides for use with Secure Streaming
Dahuatimestamp = serverStamp with server time.
Dahuatimezone=cameraAllow camera to retain timezone when connected to exacq (do not push GMT as we normally do).
Dahuatimezone=utcpush GMT to device, this is also default if not provided.
Hikvisiontimestamp=rtpForce to camera timestamp without waiting for RTCP sync.
Hikvisiontransport={tcp,udp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Hikvisiongetparameter_override=trueNeeded for HQHI-SATA encoder to prevent stream interruption.
Hikvisionosd_override=offAllow camera time OSD to be displayed (when enabled on camera)
Hikvisiontimezone=cameraAllow camera to retain timezone when connected to exacq (do not push GMT as we normally do).
Hikvisiontimezone=serverPush GMT timezone to camera (because Illustra standard does NOT do this as default)
Hikvision1 timestamp=serverStamp with server time.
Hikvision1 timestamp=rtcpStamp with server time until sync with RTCP server report.
Hikvision1 support=legacySupport original CGI interface.
Hikvision1 support=isapiSupport ISAPI interface.
Illustra3transport=udpStream RTSP session with UDP protocol.
Illustra3zoom=operationForce zoom only operation and controls as part of PTZ and live view.
IllustraFlexnone
Illustranone
Ioimagenone
Ipxnone
IQEyenone
Onviftransport=udp1 TCP socket for RTSP and up to 6 UDP sockets for video, audio, and application data and their RTCP streams.
Onviftransport=rtsp1 TCP socket for RTSP with all other streams interleaved in it.
Onviftransport=httpDefault 2 TCP sockets for RTSP over HTTP over TCP. ( 1 long POST and 1 long GET )
OnvifProfile=xConnect to a specific profile number.
Onvifnat=1Support nNAT translation to WAN address.
Onviftimestamp=serverStamp with server time.
Onvifbank=xSelect 4 channel encoder banks.
Onvifhttp=1.0For Samsung SPE-100/400 that requires http1.0 for live555.
Onvifsupport=profile-sForce Profile-S implementation for cameras that do not fully support Profile-T.
Onvifevents=pull or streamSelect metadata event mode when the manufacturer option is ALL.
Onvifuse_caps={on,off}Use deprecated GetCapabilities for when GetServices is poorly implemented.
Onviftunnel_alive = auto,get_parameter,set_parameter,options,noneKeep alive mechanism during RTPS-over-HTTP, defaults to auto.
Panasonictransport=udpStream RTSP session with UDP protocol.
Panasonictimestamp=serverStamp with server time.
Pelcotransport=udpStream RTSP session with UDP protocol.
RTSPtransport=udpStream RTSP session with UDP protocol.
RTSPtransport={tcp,udp,rtsp,rtsph,rtsphs}All Transport overrides.
RTSPtimestamp=serverStamp with server time.
RTSPtimestamp=rtcpStamp with server time until sync with RTCP server report.
RTSPtimestamp=trustedStamp with cameras time adjusted by RTSP/RTCP per RFC.
RTSPstream=xSelect specific stream number.
RTSPtrack=xSelect specific track number.
RTSPtunnelport={1025-65535}Tunneling port replacing the :portnum on URL.
RTSPembed_port=*Forced RTSP URL format in tunnel.
RTSPhttp=1.0,1.1Forced RTSP URL version number.
RTSPbc_audio=supportedBackchannel audio out.
RTSPbc_samplerate=xxxxBackchannel sampling rate.
RTSPbc_samplesize=xxxxBackchannel sampling size.
RTSPbc_mode=tsBackchannel timestamp mode(duration(default)/timestamp using RTCP adjustment).
Samsungtransport={tcp,udp,rtsp,rtsph,rtsphs}Transport overrides for use with Secure Streaming
Samsungtunnelport={1025-65535}Tunneling port if different than one used for CGI.
Samsunghttp=1.0,1.1Fix for some older devices.
Samsungembed_port=*Fix Internal URL inside tunnel if needed.
Sanyonone
Sonytimestamp=serverStamp with server time.
StarDotnone
UDPnone
Vivoteksupport=legacyUse legacy API and support.
Vivoteksupport=onefwUse OneFW API and live555 stream.

1 The use of these overrides requires the use of IPv4 dotted address, FQDNs cannot be used.
<br><br>

Override Definitions

OverrideDescription
transportStream session with the specified protocol { TCP | UDP }.
timestampStamp frames with server or camera time.
timezone{ UTC | camera | server } Determine if camera timezone is set to UTC+0, left as camera or set to that of server.
zoomOverride configuration or operation zoom function.
blocksizeOn by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues.
profileConnect to profile number N; N is a number from 1 to the number of profiles supported by the camera.
natSupport NAT translation to WAN address.
bankSelect 4 channel encoder banks. N is 1 – number of banks, usually in set { 1 | 2 | 3 | 4}.
supportOverride support API. For example, used by Vivotek to support either legacy or oneFw.
streamSelect a specific stream ID for devices supporting multiple streams.
trackSelect a specific track for devices supporting multiple media tracks.
tunnelportWorkaround for our XML and GUI only giving us one box for port. Used if tunnel port is different than CGI and does not come from CGI.
embed_portValue does not matter. Forces RTSP URL inside tunnel to put port in the URI if it is default. A small selection of cameras need ip:554 even when in a tunnel over 80

<br>

Categories
Documentation Quick Start Guides exacqVision Server Categories Products

exacqVision Edge/Vivotek Quick Start Guide

exacqVision-Edge-for-Vivotek.pdf
Categories
Knowledge Support Support Categories exacqVision Integrations

Vivotek Xarina Edge Server Unlicensed

Symptom:

Client displays bad license on Edge Server.

<br>

Problem:

Updating or new install of Edge Server to 9.2 on Vivotek Xarina devices shows the Edge Server as unlicensed. MAC address displayed as ’02-AB-CD-AB-CD-EF’, which is invalid. 

<br>

Solution:

Update to Edge version 9.4. 

If license is expired and does not allow use of 9.4, downgrade to Edge 9.0. 

<br>

Vivotek-Xarina-Edge-Server-Unlicensed.pdf
Categories
Knowledge Support Support Categories Products exacqVision Integrations

VADP Upload Fail on Vivotek Cameras

After formatting an SD card for a Vivotek camera, the VADP upload can fail with the following error:

Create “/mnt/auto/CF/vadp” failed
Upload module failed
Upload VADP package failed

<br>

This is caused by the camera’s inability to create the default folder on the SD card.

If this occurs, complete the following steps:

  1. Remove the SD card and install it into another machine.
  2. Navigate to the SD card’s root.
  3. Create a directory with the name “vadp.”
  4. Reinstall the SD card into the camera and continue with the installation.

<br>

VADP-Upload-Fail-on-Vivotek-Cameras-1.pdf
Categories
Knowledge Support Support Categories Products exacqVision Integrations

Vivotek VS8801 Encoder Enabling 2nd NIC for exacqVision

Title

Vivotek VS8801 Encoder Enabling 2nd NIC for exacqVision

Description

This encoder requires the use of two IP addresses to view all 8 channels of video.  The first NIC allows access to channels 1-4 and the second NIC allows access to channels 5-8.  The following are instructions for enabling the 2nd NIC on the Vivotek VS8801 encoder.

Product

Vivotek VS8801 Encoder
exacqVision Server

Solution

  • Enable the 2nd NIC by accessing the the following URL 
  • http://<ipaddress>/cgi-bin/admin/setparam.cgi?network_openip2=1
  • Where <ipaddress> is the actual IP address of the encoder.
  • The web page should echo the command setting to confirm that it has been successfully set
  • Open the encoders web page
  • Navigate to network configuration and ensure that the second NIC is now available
  • Configure the 2nd NIC
  • The encoder can now be added in exacqVision using the first IP address for channels 1-4 and the 2nd IP address for channels 5-8.