NX Witness

Introduction

This guide describes the steps required to configure NX Witness for integration with GCXONE.

NX Witness Configuration

Connecting and creating an integration user

Step 1: Open the NX Witness client and click Connect to Server. Enter the admin/owner credentials — IP address (Host), username (Login), and Password — into the popup window, then click OK.

Step 2: After logging in, right-click Users and select New User...

Step 3: Fill in the new user form. User Type must be Local and Role must be Administrator.

Step 4: Make sure the Enable toggle is on. Click the three dots (⋯) to reveal Allow digest authentication for this user, and make sure it's selected.

Step 5: Once all the information is entered, the form should look like the screen below. Click OK to create the user.

Configuring the I/O module and event rules

Step 6: Right-click the I/O device and select I/O Module Issues to configure it.

Step 7: Click Add to open the Event Rules window, where you'll create the rules below.

Step 8: To add cameras or sensors as a rule's source, right-click each one individually and click Add.

Step 9: Create the following four rules, one at a time, using the When dropdown under Event to select each trigger:

• Rule 1 — Device Disconnected

• Rule 2 — On Analytics Event start

• Rule 3 — While Analytics Event

• Rule 4 — On Event Disconnected

For each rule, configure the Action tab to forward the event to GCXONE:

Rule 1 (Device Disconnected) — Action tab:

• Select: Do HTTP(S) request
• HTTP(S) URL: hanwahproxy.nxgen.cloud/eventIngest
• HTTP(S) Content: {"eventType": "motion.novideo", "cameraid": "[ENTER THE UNIQUE CAMERA ID]"}
• Content Type: application/json
• Login: [ENTER THE UNIQUE DEVICE ID]
• Password: [ENTER THE UNIQUE DEVICE ID]
• Authentication Type: Basic
• Request Method: POST
• Click Apply and OK.

Rule 2 (On Analytics Event start) — Action tab:

• Select: Do HTTP(S) request
• HTTP(S) URL: hanwahproxy.nxgen.cloud/eventIngest
• HTTP(S) Content: {"eventType": "analytics.intrusion", "cameraid": "[ENTER THE NX WITNESS CAMERA ID]"}
• Content Type: application/json
• Login: [ENTER THE GCXONE DEVICE ID]
• Password: [ENTER THE GCXONE DEVICE ID]
• Authentication Type: Basic
• Request Method: POST
• Click Apply and OK.

The Login/Password and Content fields both take the GCXONE device's identifiers — for reference, an example device/sensor overview page URL in GCXONE looks like:

gcx.nxgen.cloud/configuration/sp/4xx…a50444c98619e7xxxxxxxx?tab=overview — where sensor id is 882e8f525a50444c98619e7xxxxxxxx and device id is de78ee2cba8a4e2c91ce887cxxxxxx.

Once all four rules are created, the Event Rules list should look like this:

NX Witness Config Guide with GCXONE

Step 1: Navigate to the Devices tab.

Step 2: Click the Add New button.

Step 3: The Add Device dialog will be displayed.

Step 4: Open the Device dropdown, search for NX Witness, and select it.

The Connection Settings section includes an Enable Cloud option, letting the same NX Witness deployment connect either through Nx Cloud or over the local network.

Local Connection

When Enable Cloud is left unchecked, the device connects using the standard local network configuration. The following details are required:

• IP Address or Host Name
• User Name
• Password
• RTSP Port

Cloud Connection

When Enable Cloud is checked, the device is configured and accessed through Nx Cloud instead, and a public IP address or port is not required. The following details are required:

• User Name
• Password
• Server ID

A Cloud user can be added to the existing NX Witness system, and the corresponding Server ID can be shared with the authorized user to provide access through Nx Cloud.

User Benefit

This provides the flexibility to connect to the same NX Witness deployment using either Cloud-based or local network connectivity, without changing the existing deployment:

• Cloud Mode: Connect using a User Name, Password, and Server ID, without requiring a public IP address or port.
• Local Mode: Connect directly using an IP Address or Host Name, Port, and local user credentials.