Tag: Onvif

Categories
Knowledge Support Support exacqVision Server Products

Onvif -Motion Not Working When Updating from 23.06 to 23.09

Product

  • exacqVision Server 23.09

Steps to Reproduce

Update exacqVision Server from 23.06 to 23.09

Expected Results

Motion works

Actual Results

Motion does not work

Steps to Troubleshooting

  1. Get PCAPs/ Logs from the 23.09 version
  2. Test adding an override of #config=dynamic to the camera’s address field on Add IP Cameras page
  3. Examine the logs to identify the following log message:
onvifnvcPI Verbose 10.247.216.144 searching for relevant settings<br>in JSON config file

Once troubleshooting is complete, roll the customer back to 23.06 for the time being until the issue is fixed. (See update at the bottom of page.)

Tier 3 Will create New Tickets based on the Manufacturers and link them to AES-701.

Update: When seeing motion issues with the above logs please see if Version 23.09.9.0 will allow motion and free run will record.
https://exacq.com/support/downloads.php

Categories
Cloudvue Knowledge Support Cloudvue Gateway Support Categories Products

Cloudvue Gateway Camera Integrations

Description 

Traditionally Cloudvue has focused on individual API integrations for cameras connecting to the Cloudvue Gateway. However, there are just too many camera manufactures to integrate with each. So, except for Illustra and Axis we rely on integrating with ONVIF Profile-S compliant cameras.

Customers that would like a specific API camera integration should submit their requests online at https://www.cloudvue.io/support-camera-integrations.  The request will be reviewed, and feedback provided.

Categories
Cloudvue Knowledge Support Cloudvue Gateway Support Products

Amcrest Cameras Fail to Add as ONVIF

Description 

Adding an Amcrest camera as ONVIF to a Cloudvue Gateway fails with an error message “Invalid Username / Password”. This is true even if the credentials being used work to login to the cameras web interface.

Product

  • Cloudvue Gateway
  • Cloudvue Software v22.9.2

Steps to Reproduce 

  • From the Devices tab in Cloudvue Local (Settings > Devices)
  • Scan For devices , select and add an Amcrest Camera
  • When prompted enter username, password and add as ONVIF

Expected Results 

  • Camera adds

Actual Results

  • Camera fails to add with an error message “Camera Save Failed … Invalid Username / Password”

Solution

  • Create a user in the camera called “onvif” and use those credentials when adding the camera in Cloudvue Local.

Reference: https://amcrest.com/forum/ip-cameras-f18/onvif-authentication-not-working-in-newer-cameras-t13723.html

Re: ONVIF authentication not working in newer cameras

Post by ckchessmaster » Wed Jan 18, 2023 12:58 pm

Categories
User Guides Knowledge Support Documentation Support Illustra Categories Products exacqVision Integrations

Enhanced vs Standard Security on Illustra cameras

After logging into your Illustra camera for the first time, accepting the End User License Agreement, and creating a Host ID, you will be asked to select a security mode.

SecurityMode.png

Enhanced is selected by default. As the message indicates, Enhanced will automatically select several advanced security options, such as enabling additional authentication needs, like forcing the creation of a non-default username, and requiring HTTPS. Regardless of the selection chosen on initial setup, individual settings can always be changed later by navigating to Security Status, under the Security menu.

Selecting ‘Enhanced’ Security performs the following:

  • Requires authentication to the RTSP video stream
  • Changes Authentication from Basic to Digest
  • Disables HTTP, requiring HTTPS connections for the camera GUI and Video
  • Disables uPnP, which hides the device from device discovery.
Security settings, as automatically selected by Enhanced Mode. Individual settings may still be changed manually.

Changing any of the security settings only requires you to click the Edit link beside the listed option. Some settings offer the ability to change port numbers and some offer additional setting fields to configure. 

Notice that Onvif Discovery may be individually disabled on this page as well. Clicking the Edit link for Onvif Discovery redirects to the Remote Access options page. This permits you to disable Onvif Discovery, or require Onvif User Authentication. 

The Users configuration page permits additional user accounts to be created, in which a user role is assigned. Enabling Onvif User Authentication directs the camera to only accept commands from authenticated users. 

<br>

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories Products

Unable to Add Hikvision Camera to Cloudvue Gateway

Description 

While older Hikvision cameras can be added as model specific newer models do not have individual API integrations and must be added using ONVIF.   Before scanning or adding the camera in Cloudvue or Cloudvue Local the following items must be configured within the camera web interface on each camera. 

Product 

  • Cloudvue Gateway

Solution

RTSP Authentication

  • Configuration > System > Security
  • Set to digest or digest/basic.

ONVIF or Open Network Video Interface

  • Configuration > Network > Advanced Settings > Integration Protocol
  • Must be enabled.

ONVIF User

  • Configuration > Network > Advanced Settings > Integration Protocol
  • An ONVIF user with the following attributes is added.
    • Username: admin
    • Password: same as the current admin user used to access the cameras web interface
    • Level: Administrator

NOTE: Customers have reported that sometimes the settings don’t get applied in the camera.  Please double check by logging out and back into the camera and reviewing.

Categories
Knowledge Support Support exacqVision Server Categories Products

Client Crashes When Analytics Enabled on Onvif Multi-Sensor Camera’s

*** INTERNAL USE ***

Description 

Reports of the exacqVision Client and/or system crashes have been reported from Illustra or Samsung  multi-sensor cameras using the ONVIF PLUGIN when analytics is  enabled.

Product 

  • exacqVision Server 22.09.4.0

Steps to Reproduce 

  • Add a multi-sensor camera using the onvif plugin
  • Enable analytics
  • The client will crash shortly after enabling the camera analytics.

Expected Results 

  • analytics are available and system runs normally

Actual Results 

  • After about 10 seconds the client crashes
  • There is one report of a system Blue Screening as well

Solution

  • Disable Analytics
  • Wait for the release of exacqVision Server 22.12

NOTE: 

Information about an available branch build is available here

Also see AESW-3366

Categories
Knowledge Support Support exacqVision Server Products

Steps to handle Protego cameras without #transport=rtsp

Description 

Steps to handle Protego cameras without #transport=rtsp

Product 

  • exacqVision Server
  • Protego branded cameras

Expected Results 

Camera connects normally without any issues.

Actual Results 

Camera connects then drops, then connects then drops on repeat. Only when the camera has #transport=rtsp on the end does the connection stay stable.

Solution

  1. Navigate to the server installation folder
    1. Windows – Typically this is under C:\Program Files\exacqVision\Server
    2. Linux – Typically this is under ~/usr/local/exacq/server
  2. Find the file named onvifnvcpi.json and TAKE A BACKUP!
  3. You can open and edit this in notepad or nano or whatever you prefer.
  4. CTRL+F to open the find menu
    1. Search for “Sunell”
    2. Enter “Protego” as an alias, ensuring to follow the format of the other aliases. Also ensure not to delete any other lines in this file as it can mess with other onvif functionality.
  5. Save and close the file.
  6. Restart the ExacqVision Server service.
    1. In windows this can be done from within the “services” program, searching “services” in the start menu should bring it up.
    2. In Linux open terminal and type.
      1. sudo systemctl stop edvrserver
      2. sudo systemctl start edvrserver
  7. Check connected cameras and you should be able to remove #transport=rtsp.
Categories
Knowledge Support Support Categories Products exacqVision Integrations

Infinova – Onvif not triggering motion

Description

When the Infinova camera is added there is no motion shown in the client

Product 

  • exacqVision Server
    • Onvif Plugin

Steps to Reproduce 

  1. Add Infinova camera to exacqVision Server
  2. Configure motion within exacqVision and/or camera
  3. Trigger motion

Expected Results 

Motion is triggered

Actual Results 

No Motion seen on Exacq

Solution

Add the following to the section to the onvif JSON file in the server configuration. 

      {<br>
        "manufacturer": "Infinova",<br>
        "motion": {<br>
          "topic": [<br>
            {<br>
              "name": "VideoSource/MotionAlarm/",<br>
              "data": {<br>
                "name": "State",<br>
                "on": "true",<br>
                "off": "false"<br>
              }<br>
            }<br>
          ],<br>
          "configuration": {<br>
            "analytics": {<br>
              "name": "MyCellMotion"<br>
            },<br>
            "rule": {<br>
              "name": "MyMotionDetectorRule"<br>
            }<br>
          }<br>
        },<br>
        "analytics": {<br>
          "topic": [<br>
            {<br>
              "name": VideoSource/ImageTooBlurry/ImagingService",<br>
              "data": {},<br>
              "analytics_metadata": []<br>
            },<br>
            {<br>
              "name": "VideoSource/ImageTooDark/ImagingService",<br>
              "data": {},<br>
              "analytics_metadata": []<br>
            },<br>
            {<br>
              "name": VideoSource/ImageTooBright/ImagingService",<br>
              "data": {},<br>
              "analytics_metadata": []<br>
            },<br>
            {<br>
              "name": VideoSource/GlobalSceneChange/ImagingService",<br>
              "data": {},<br>
              "analytics_metadata": []<br>
            }<br>
          ]<br>
        },<br>
        "options": {<br>
          "createpullpoint-wsa-header": "true",<br>
          "event-type-for-motion-detection": "pull",<br>
          "event-type-for-input-trigger": "pull",<br>
          "backfill-supported": "true"<br>
        }<br>
      },<br>

<br>

Note: If upgraded this will be removed if it is not be fixed yet

Ticket – AES-20

<br>

Categories
Knowledge Support Support Categories Products exacqVision Integrations

GSD – Onvif Not Triggering Motion

*** INTERNAL USE ***

Description

exacqVision Server is not detecting motion from GSD cameras using the onvif plugin.

Product 

  • exacqVision Server 22.09
  • Onvif Plugin (onvifnvcpi.json)
  • GSD Cameras
    • D2F28IP5MP-L
    • D2FDA28IP5MP-L

Steps to Reproduce 

  • Add GSD camera to exacq server
  • Configure motion on exacq and/or the camera
  • Trigger motion

Expected Results 

  • Motion is detected in exacqVision

Actual Results 

  • Motion is not triggered in exacqVision

Solution

WARNING – This is temporary and will not survive an upgrade of exacqVision Server Software

Modify the “options” section for “manufacturer”: “GSD” in the onvifnvcpi.json

Before Change
After Change

Note: See AES-69 for additional information

Categories
Knowledge Support Support exacqVision Server Categories Products

Altering the Onvif JSON file

*** INTERNAL USE ***

Product 

exacqVision Server > Onvif plugin

Steps to Reproduce

  1. Ensure motion detection is enabled within the camera.
  2. Add the Onvif camera to the exacqVision Server. If motion was enabled in the camera after being added to the system, toggle the Enable checkbox beside the camera on the Add IP Cameras page so exacqVision queries the camera for the updated settings.
  3. Configure motion settings within exacqVision.
  4. Trigger motion, ensuring a motion boarder appears around the image and/or motion recording is indicated on the search timeline.

Expected Results 

The motion alert is triggered and video is recorded.

Actual Results 

No motion alert is displayed and/or no motion recording occurs.

Solution

In some instances you may alter the Onvif JSON file if there is an element missing.

The onvifnvcpi.json file is organized into blocks by manufacturer. Nested within each manufacturer are action types and within those are “topics”, which define the name and state of these types. Some brands may appear more than once depending on changes in labeling, and tome topics may include several names for the same activity, such as motion, depending on the many iterations of naming conventions that manufacturer has used.

Discovering and Adding Topics

IMPORTANT: Always create a backup of the onvifnvcpi.json file prior to attempting any manual changes.

Onvif Device Manager is a free software application that can display the topics provided by the camera device.

  1. Connect to the camera using Onvif Device Manager. The below example uses a Geovision GV-TBL8810, although the topics for this already exist in the JSON file, this provides a good example.<br><br>
  2. After connecting the camera, select the Metadata link beside the video source with the camera thumbnail.
    <br><br>
  3. Expand the Metadata details near the top.
    <br><br>
  4. The topic name you will be looking for will vary between manufacturers and even firmware versions. In this example, we find a topic with “Motion” in the name. The device used in this example shows:
    tns1:RuleEngine/CellMotionDetector/Motion
    Then see that nested below it includes a Data field holding an attribute titled “IsMotion”. This is what we’re looking for.
    <br><br>
  5. A quick search reveals that GeoVision already exists in the json file, there’s actually two entries with different attributes in this file. But if GeoVision did not already exist, you would need to enter a new block, replicating the same nested formatting and being sure to enter it in the same level as the other camera “blocks” within the json format. With so many nested levels this may be difficult, Notepad++ can help display, collapse, and expand json files to make them easier to work with. All camera manufacturer blocks are within a list named “items”, which begins near the top of the document.<br><br>
  6. The first attribute within this block is the “manufacturer”, listed here as “GeoVision_2”.
    <br><br>
  7. Beneath this is the “motion” block, containing a list of any motion attributes. Notice, that this entry contains multiple motion attributes due to the manufacturer using multiple methods in different models and firmware versions. But you can see the first one matches the line discovered in Onvif Device Manager earlier.
    “RuleEngine/CellMotionDetector/Motion“

    If you were adding a new entry, you would use this as the “name” attribute under “topic”.<br><br>
  8. Nested below is the “data” attribute, which matches the “Data” item listed in Onvif Device Manager. First, enter the name.

    When entering these, they must match EXACTLY as listed by Onvif Device Manager.<br><br>
  9. Then enter the “on” and “off” states. In this example, the camera sends a status of “true” or “false”. Other cameras or firmware versions may state “0” or “1”. While both are boolean values in terms of programming, these must be entered exactly as the camera provides them.<br><br>
  10. Once all values have been entered and the proper closing brackets are applied so that the json file is formatted correctly, save the file.<br><br>
  11. Restart the exacqVision Server service and test your changes. If you do not see results, you may need to go back and check your json formatting, or the entries used.

IMPORTANT: Manual changes to the onvifnvcpi.json file are not retained during exacqVision Server software updates. If you have made manual changes to this file, you must make a copy of it prior to updating the software, then place it back in the Server directory after updating.

<br>