exacqVision Server 6.2 to 7.2.3
<br>
ONVIF PTZ camera with two streams may display as two different cameras even if “Manage all streams as quality” is checked. This is because the XML is reporting the secondary context as being an independent PTZ which is something generally used for fisheyes where PTZing one stream doesn’t PTZ the other streams.
<br>
No workaround
<br>
Update exacqVision Server to 7.4.0
<br>
This bug caused the Onvif configuration failed to handle a complete soap message when they are partially send. The end result is that there would be a long delay before the camera would be “connected”
<br>
r34959 (dev build 5_1_9_34964)
<br>
All
<br>
Use the Hitachi DI-CB320G(F8-48-97-9E-76-9E 10.16.11.47:8080 root/admin) for testing.
connect the camera with Onvif plugin.
<br>
Camera connected with minimum delay.
<br>
Camera in “connecting” state for long time(could be 10-20 minutes) and finally connected.
<br>
none
<br>
r103397 (dev build 8.1.8.103450)
<br>
Onvif
Onvif plugin does allow additional parameters in the host name for added supports. Such as profile/tranport settings(#Profile=1 or #transport=udp). Profile expects a number but would crash the server if a string is entered.
<br>
<br>
All
<br>
connect onvif camera with host name and profile with string.
example: 10.16.1.1#profile=test
<br>
string in profile is ignored and defaulted to the first profile.
server does not crash.
<br>
server crashes with invalid string entry.
<br>
remove profile entry or reconnect with valid profile number.
<br>
r103382 dev build 8.1.8.103450
<br>
Onvif
In rare cases, a camera’s firmware might not provide valid video as the first profile, causing the ONVIF plug-in to crash and producing a log message of “profile 0 missing video encoder configuration.” This was specifically observed with an APAC camera running version 1.1 firmware. This could affect exacqVision Server 6.2.x and later.
<br>
As a workaround, specify a valid profile with the IP hostname:
10.16.10.224#profile=1
10.16.10.224#profile=2
exacqVision 5.4 or later
<br>
When certain cameras are connected using the ONVIF plugin and the plugin is configured to use metadata streaming to receive motion and alarm events, a memory leak is possible. If memory usage increases enough exacqVision can crash. The crash is typically in ntdll which show a heap memory issue.
To validate this issue is the root cause of a crash, stop the Onvif plugin from requesting a metadata stream as described in the workaround.
<br>
Edit the /exacqVision/server/onvifnvcpi.json file to remove the manufacturer’s entry. This will result in the loss of motion-based recording, so modify the recording schedule to use free run recording.
<br>
No fix at this time.
Starting with exacqVision Server 9.3.21, some ONVIF cameras may repeatedly disconnect and reconnect, which causes gaps in video recording. The following log message repeating pattern may also be observed:
27/02/2020 00:00:27 onvifnvcPI Verbose 172.28.140.17: Context 017 HQ Office R&D. Media open but data timed out. Close and retry27/02/2020 00:00:27 onvifnvcPI Verbose 172.28.140.17: 017 HQ Office R&D Context 0 Connection status changed to 027/02/2020 00:00:27 onvifnvcPI Warning 172.28.140.17: Context 017 HQ Office R&D. Stream closing27/02/2020 00:00:27 onvifnvcPI Verbose 172.28.140.17: Context 017 HQ Office R&D. Ok to begin playback27/02/2020 00:00:27 onvifnvcPI Verbose Opening 017 HQ Office R&D. RTSP Uri path: rtsp://172.28.140.17:554/main27/02/2020 00:00:37 onvifnvcPI Verbose 172.28.140.17: Context 017 HQ Office R&D. Media open but data timed out. Close and retry27/02/2020 00:00:37 onvifnvcPI Warning 172.28.140.17: Context 017 HQ Office R&D. Stream closing
This issue was introduced when the RTSP streaming implementation was changed in the ONVIF plugin.
<br>
Downgrade to latest 9.2.x version or upgrade to exacqVision Server 20.03.6 (and dev build 20.03.110)
Fixed with exacqVision Server 20.03.6 (and dev build 20.03.110)
<br>
Starting with exacqVision Server 9.3.21
<br>
exacqVision Server 20.03.6 (and dev build 20.03.110).
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>
Use continuous recording or upgrade.
<br>
Fixed in exacqVision Server version 20.03.119
<br>
exacqVision Server lower than 20.03.119
<br>
exacqVision Server 20.03.119
<br>
The Onvif plugin has always time-stamped frames as they arrive at the server. With issues of network latency and camera streaming problems, this could cause video to look jittery. An option was added to provide time-stamping with camera time. Adding #timestamp=camera in the hostname would use the presentation time provided by the camera. The default will still time-stamp frames at the server.
<br>
Supported started with dev build 8.3.28.109905.
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}
<br><br>
| Plugin | Option | Usage |
|---|---|---|
| ACTi | transport=http | HTTP stream support for legacy platforms and user data |
| ACTi | transport=rtsp | RTSP stream with separate metadata socket for motion/input trigger/video loss/etc. |
| Axis | zoom=config | By default zoom only cameras support. |
| Axis | zoom=operation | Force zoom only operation and controls as part of PTZ and live view. |
| Axis | blocksize=off | On by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues. |
| Axis | transport= {udp,tcp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Axis | tunnelport={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. |
| Axis | timestamp={server,trusted} | Override timestamp to server time(server) for problem cameras or to camera adjusted by RTSP/RTCP per RFC(trusted) |
| Arecont | none | |
| Dahua | transport= {udp,tcp,rtsph} | Transport overrides for use with Secure Streaming |
| Dahua | timestamp = server | Stamp with server time. |
| Dahua | timezone=camera | Allow camera to retain timezone when connected to exacq (do not push GMT as we normally do). |
| Dahua | timezone=utc | push GMT to device, this is also default if not provided. |
| Hikvision | timestamp=rtp | Force to camera timestamp without waiting for RTCP sync. |
| Hikvision | transport={tcp,udp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Hikvision | getparameter_override=true | Needed for HQHI-SATA encoder to prevent stream interruption. |
| Hikvision | osd_override=off | Allow camera time OSD to be displayed (when enabled on camera) |
| Hikvision | timezone=camera | Allow camera to retain timezone when connected to exacq (do not push GMT as we normally do). |
| Hikvision | timezone=server | Push GMT timezone to camera (because Illustra standard does NOT do this as default) |
| Hikvision1 | timestamp=server | Stamp with server time. |
| Hikvision1 | timestamp=rtcp | Stamp with server time until sync with RTCP server report. |
| Hikvision1 | support=legacy | Support original CGI interface. |
| Hikvision1 | support=isapi | Support ISAPI interface. |
| Illustra3 | transport=udp | Stream RTSP session with UDP protocol. |
| Illustra3 | zoom=operation | Force zoom only operation and controls as part of PTZ and live view. |
| IllustraFlex | none | |
| Illustra | none | |
| Ioimage | none | |
| Ipx | none | |
| IQEye | none | |
| Onvif | transport=udp | 1 TCP socket for RTSP and up to 6 UDP sockets for video, audio, and application data and their RTCP streams. |
| Onvif | transport=rtsp | 1 TCP socket for RTSP with all other streams interleaved in it. |
| Onvif | transport=http | Default 2 TCP sockets for RTSP over HTTP over TCP. ( 1 long POST and 1 long GET ) |
| Onvif | Profile=x | Connect to a specific profile number. |
| Onvif | nat=1 | Support nNAT translation to WAN address. |
| Onvif | timestamp=server | Stamp with server time. |
| Onvif | bank=x | Select 4 channel encoder banks. |
| Onvif | http=1.0 | For Samsung SPE-100/400 that requires http1.0 for live555. |
| Onvif | support=profile-s | Force Profile-S implementation for cameras that do not fully support Profile-T. |
| Onvif | events=pull or stream | Select metadata event mode when the manufacturer option is ALL. |
| Onvif | use_caps={on,off} | Use deprecated GetCapabilities for when GetServices is poorly implemented. |
| Onvif | tunnel_alive = auto,get_parameter,set_parameter,options,none | Keep alive mechanism during RTPS-over-HTTP, defaults to auto. |
| Panasonic | transport=udp | Stream RTSP session with UDP protocol. |
| Panasonic | timestamp=server | Stamp with server time. |
| Pelco | transport=udp | Stream RTSP session with UDP protocol. |
| RTSP | transport=udp | Stream RTSP session with UDP protocol. |
| RTSP | transport={tcp,udp,rtsp,rtsph,rtsphs} | All Transport overrides. |
| RTSP | timestamp=server | Stamp with server time. |
| RTSP | timestamp=rtcp | Stamp with server time until sync with RTCP server report. |
| RTSP | timestamp=trusted | Stamp with cameras time adjusted by RTSP/RTCP per RFC. |
| RTSP | stream=x | Select specific stream number. |
| RTSP | track=x | Select specific track number. |
| RTSP | tunnelport={1025-65535} | Tunneling port replacing the :portnum on URL. |
| RTSP | embed_port=* | Forced RTSP URL format in tunnel. |
| RTSP | http=1.0,1.1 | Forced RTSP URL version number. |
| RTSP | bc_audio=supported | Backchannel audio out. |
| RTSP | bc_samplerate=xxxx | Backchannel sampling rate. |
| RTSP | bc_samplesize=xxxx | Backchannel sampling size. |
| RTSP | bc_mode=ts | Backchannel timestamp mode(duration(default)/timestamp using RTCP adjustment). |
| Samsung | transport={tcp,udp,rtsp,rtsph,rtsphs} | Transport overrides for use with Secure Streaming |
| Samsung | tunnelport={1025-65535} | Tunneling port if different than one used for CGI. |
| Samsung | http=1.0,1.1 | Fix for some older devices. |
| Samsung | embed_port=* | Fix Internal URL inside tunnel if needed. |
| Sanyo | none | |
| Sony | timestamp=server | Stamp with server time. |
| StarDot | none | |
| UDP | none | |
| Vivotek | support=legacy | Use legacy API and support. |
| Vivotek | support=onefw | Use 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 | Description |
|---|---|
| transport | Stream session with the specified protocol { TCP | UDP }. |
| timestamp | Stamp 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. |
| zoom | Override configuration or operation zoom function. |
| blocksize | On by default, but could turn off blocksize in the RTSP session for some cameras with streaming issues. |
| profile | Connect to profile number N; N is a number from 1 to the number of profiles supported by the camera. |
| nat | Support NAT translation to WAN address. |
| bank | Select 4 channel encoder banks. N is 1 – number of banks, usually in set { 1 | 2 | 3 | 4}. |
| support | Override support API. For example, used by Vivotek to support either legacy or oneFw. |
| stream | Select a specific stream ID for devices supporting multiple streams. |
| track | Select a specific track for devices supporting multiple media tracks. |
| tunnelport | Workaround 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_port | Value 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>
The streaming profile of ONVIF (Profile S) provides a standard interface for streaming video and audio between conformant devices (cameras or encoders) and clients (VMS). The ExacqVision VMS is listed as an ONVIF Profile S-conformant client.
Extensive testing with a wide variety of ONVIF Profile S-conformant cameras has revealed enough inconsistency that Exacq does not explicitly declare support for all Profile S cameras for use with ExacqVision. Only the IP cameras listed in the Exacq IP Camera Integration database are officially compatible and supported for use with ExacqVision. Cameras not listed in the camera database should not be considered compatible with ExacqVision, even if they are Profile S-conformant.
If you are interested in using an ONVIF Profile S-conformant camera that is not listed in our camera database, please submit an integration request on the IP camera integration web page by clicking “Can’t Find Camera?”
<br>