Categories
Exacq Legacy Camera Support Knowledge Support Support exacqVision Server Categories Products exacqVision Integrations

The Device Type I need isn’t listed

Details

When adding an IP device to your ExacqVision Server, each device will be associated with a Device Type that selects the underlying plugin used for communication.

The article, What IP cameras are supported by ExacqVision?, will tell you more about how to use the IP Camera Integration database to find the proper Device Type.<br><br>

Problem

You are unable to find the required Device Type when attempting to add the device. <br><br>

Cause

When using an existing ExacqVision install, possible reasons are:

  1. The plugin was not selected to be included in the initial installation.<br><br>
  2. The first version of the plugin was released after your initial server installation version.<br><br>

In the first example, running the installer manually, a dialogue window appears providing users with the option to select or deselect each individual plugin to be included with the server installation. Most users are fine using the default selections. There are some plugins not selected by default because they may be older or used only in rare instances.

When performing automated updates using the Check for Updates button the software updates only the plugins already installed. It does not install additional plugins.

In the second example, you may be looking for a plugin used for a newer integration. This may also eventually lead to the cause mentioned above. <br><br>

Resolution

  1. Download the ExacqVision Server installer directly from the Software Downloads page.<br><br>
  2. Run the downloaded installer file manually.<br><br>
  3. Watch for the dialogue in which the listed plugins may be selected for install.<br><br>
  4. Scroll to the plugin you need and be sure it is check marked for install.<br><br>
  5. Complete the remainder of the installation steps. After the service restarts, the desired plugin should be listed in the Device Type options.

<br>

Categories
Knowledge Support Support Categories Products exacqVision Integrations

RTSP Plug-in used with ExacqVision Software

The RTSP plug-in supports generic streaming of audio and video using the RTSP/RTCP/RTP protocol. The plug-in automatically configures the streaming transport to either UDP or TCP. The default when the device is connected is TCP; if it fails to connect, it tries to connect through UDP. The plug-in does not support any configuration — it is only an audio/video streaming plug-in. The device must be configured through its web page or other application provided by the manufacturer.

<br>

Video Formats Supported

MJPEG
MPEG4
H.264

<br>

Audio Formats Supported

L16: uncompressed 16-bit audio with 8000 sampling rate (ACTi)

G711-muLaw: compressed PCM audio into 8-bit samples with 8000 sampling rate (AD, IPX, Pelco)

AAC: single channel (AXIS)

G726-16,24,32,40: ADPCM encoded audio with 2, 3, 4, and 5 bits per sample with 8000 sampling rate (AD, Panasonic, AXIS, Sony)

You can find the address to choose for your camera model from a number of locations online or by referring to the manufacturer’s manuals and documentation.

<br>

Exacq-Specific Controls

In the RTSP URL, control parameters provide additional control of the streaming functionality. These controls are used to override the default behaviors. The typical default behavior is to select the first video and audio stream available. The default transport protocol is TCP, and if the setup process failed with 461 or Unsupported Transport protocol, it switches to UDP and restarts the session. The usage of the override controls is to append the normal RTSP URL with # and follow with key word = value.

<br>

Video Stream Index Override Control

The key word for this control is stream, and the expected value is one of the available video stream index numbers. The stream index is the index of video stream found within the described response. Thus, if two video streams and one audio stream are available, index 1 would refer to the first stream and index 2 would refer to the second video stream. For example:

rtsp://[user-name]:[password]@[ip-address]:[port]/[path]#stream=1

To select video stream number 2 from the ACTi camera:

rtsp://Admin:123456@192.168.3.61:7070#stream=2

<br>

Video Track Index Override Control

The key word for this control is track, and the expected value is one of the available video track index numbers. The track index is the logical control path of a stream that is part of the the described response. Thus, a track with the value of 1 would refer to the the video stream with a control path of track1. For example:

rtsp://[user-name]:[password]@[ip-address]:[port]/[path]#track=1

To select video track number 2 from the ACTi camera:

rtsp://Admin:123456@192.168.3.61:7070#track=2

<br>

Transport Protocol Override Control

The key word for this control is transport, and the expected values are tcp, udp, or http. TCP and UDP are used to control the RTP streaming transport method. HTTP is for RTSP tunneling over HTTP, such as with ONVIF cameras. For example:

rtsp://[user-name]:[password]@[ip-address]:[port]/[path]#transport=udp

To select UDP as the transport protocol for the ACTi camera:

rtsp://Admin:123456@192.168.3.61:7070#transport=udp

Also note that multiple additional control parameters could be appended to the URI. The following example would stream the first track in UDP mode:

rtsp://Admin:123456@192.168.3.61:7070#stream=1&transport=udp

<br>