Answers to the questions we hear most.

A device is always added under a site, so you must first create a Customer and then a Site for it. In Configuration at the Service Provider level, add the Customer, open its Sites tab and add the Site, then select that Site, open the Devices tab and click Add. In the Add Device dialog choose the device type or integration, enter the configuration and any network or authentication details, and click Save to register it. Once saved the device appears in the Devices list for that site and the platform begins monitoring it and processing its events.

• Configuration, then Customers, then Add, and Save the customer
• Open the customer's Sites tab, click Add, and Save the site
• Select the site, open Devices, click Add, choose the integration, then Save

The IO tab lists every configured input and output port across the platform in one table, showing its ID, date, device, name, site, type, and whether it appears on the map or in Salvo. Inputs receive a signal from an external source and outputs send a signal to trigger a physical action such as opening a gate or activating an alarm. IO ports marked Yes for Show on Map can be placed on the map in edit mode with the Add IO button and then triggered by clicking their icon, so an operator can open a gate straight from the map during an incident.

• Reached from Configuration Page, Service Provider Level, IO tab
• Edit sets type, name, display name, IO URL, time duration and zone
• Export at the top right exports the full IO table

On the camera, go to Event Management, open the Recipients tab and add a recipient of Type HTTPS with the URL https://axisproxy.nxgen.cloud/eventIngest/, using the nxgenDeviceId as both the user name and the password. Then open the Rules tab and create one rule for each event type that must be notified to GCX-ONE. The nxgenDeviceId comes from the Unique Reference Number shown after the device is discovered and saved in GCX-ONE.

• Recipient type HTTPS, URL https://axisproxy.nxgen.cloud/eventIngest/
• Username and password are both the nxgenDeviceId
• The control port must be open and defaults to 80 if no value is entered

The Hikvision device must be set up with Continuous Recording, and you must whitelist the IP address 35.156.60.98, which is the Hikvision Receiver. Local Mode has to be installed for P2P streaming, audio and encrypted stream. On the device, create a user for NXGEN with the listed local and remote permissions, enable ISAPI under Network, Advanced Settings, Integration Protocol, and set both RTSP and WEB authentication to Digest.

• Whitelist 35.156.60.98 for the Hikvision Receiver
• Enable ISAPI under Network, Advanced Settings, Integration Protocol
• Enable NTP under System Settings and Time Settings

Log in to your Hik Partner Pro account, making sure you are registered as an ARC, then go to Home, My Service Overview and Apply Now, and continue through the ARC details. At the end of step 2 the ARC ID and key are sent to the registered email address, and that email must be forwarded to the NXGEN team so they can configure the tenant. In GCX-ONE the device is then added by selecting Hik-ProConnect and entering Name, Serial Number, Encryption Key and Timezone before clicking Discover and Save.

Before you start, whitelist the IP 52.59.60.20, which is the Dahua Receiver, unless you use NXGEN OpenVPN services, in which case configure the new IP address given by NXGEN instead. Local Mode must be installed on operator workstations for P2P streaming, audio and encrypted stream. Then open the Devices tab, click Add, select Dahua from the Device dropdown, fill in Name, IP Address or Host, Username, Password, HTTPS Port, TCP Port, RTSP Port, HTTP Port and Timezone, click Discover and then Save.

• Whitelist 52.59.60.20 for the Dahua Receiver
• Create a device user, NXG recommended, with manual control, system, camera, system info and event rights

A Dahua detection rule only pushes to the platform once alarm reporting is switched on for it. After configuring the rule under AI, Parameters and IVS, scroll down in the parameters section, click More, then click Log and Report Alarm, which is what enables the device to push alarms to GCX-ONE. The same applies to Video Detection alarms, where you click More and then Log to make the alarms available on GCX-ONE.

• AI by Recorder offers Tripwire and Intrusion detection
• AI by Camera adds virtual fence, abandoned object, fast moving, parking and crowd gathering
• Recommended sensitivity 70 and threshold 5 for video detection

Collect the device serial number, username and password and provide them to NXGEN, and make sure the device is online before proceeding. In Dolynk Care, add a site, add the device by serial number, then use the Security Service option to set GCX-ONE as the ARC, searching for NXGEN Technology AG with the email dev@nxgen.info and clicking the shield icon next to it before clicking Apply. In GCX-ONE, select DahuaCloudArc in the Add Device dialog and enter Name, Serial number, User name, Password and Timezone, then Discover and Save.

• Serial number, username and password go to NXGEN
• Search dev@nxgen.info in Dolynk Care to find NXGEN Technology AG
• The ARC sharing request is approved automatically

Yes. The HTTPS Port field is mandatory when adding a Hanwha device, alongside IP Address or Host, Username, Password and RTSP Port. Enter those fields in the Add Device dialog after selecting Hanwha, click Discover, and click Save once the device is discovered. To check event routing afterwards, log in to the Hanwha web client, right-click the sensor, select Camera Changes, click Do HTTPS Request in the event rule list and verify the configured HTTP URL and HTTP Content.

Yes. In the NX Witness client, create a new user with User Type Local and the Administrator role, make sure the Enable toggle is on, and under the three dots select Allow digest authentication for this user. Then add the device in GCXONE by selecting NX Witness and entering IP Address or Host, Username, Password, RTSP Port and HTTPS Port, which is mandatory, before clicking Discover and Save. Event rules on each camera use a Do HTTP(S) request action posting JSON to https://hanwahproxy.nxgen.cloud/eventIngest with Basic authentication, where the login and password are both the GCXONE device ID.

• User Type Local, role Administrator, digest authentication allowed
• HTTPS Port is mandatory in the Add Device dialog
• Rules to create include Device Disconnected and On Analytics Event start

Open 80 and 443 for the Management Client, 7563 for the streaming port, 8081 for the Web Client and 22331 for the Event Service. Users must be able to log in to the Management Client with Windows Authentication or Basic Authentication, and where no VPN or direct IP connection is used one of those must be enabled and the user must have administrative privileges. Milestone servers are treated as NVR devices in GCX-ONE, and the device must be added with the same credentials used in the Management Client, selecting the appropriate authentication type.

• 80 and 443 Management Client, 7563 streaming, 8081 Web Client, 22331 Event Service
• Use XProtect Smart Client 2021 R1 with the latest hotfixes applied
• Define the recording server IP in the RecorderConfig file to avoid DNS resolution issues

Because the alarm has not been mapped. Customer-defined alarms must be set up in the GCX-ONE alarm mapping table, and an alarm that is not mapped appears as General Alarm in Talos. During the initial setup of the Milestone receiver, give NXGEN Support a list of your alarm events so they can be added to the mapping table, keep naming consistent across Milestone servers, and notify support whenever new events are added. Note also that by default listening is enabled only for Milestone alarms, so contact NXGEN Support if event listening needs to be enabled.

Yes. Avigilon is onboarded as a Video Management System discovered through its WebAPI Endpoint, with live view, analytics such as motion and object detection, alarm management, user management and PTZ controls all supported. You need the Avigilon ACC client software, the ACC 7 Web Endpoint Service, administrative access to the Avigilon system, and an IT team to set up port forwarding on the firewall or router. In the GC-X-ONE Configuration App, select Avigilon and fill in Name, IP Address or Host Name, User Name, Password, RTSP Port with a default of 554, Control Port with a default of 443, Server Port, HTTPs Port with a default of 443, Serial Number, Device Id and Timezone, then click Discover.

• WebAPI Endpoint installation is required for external communication
• A user group for GC-X-ONE access is mandatory, named NXGEN or NXG
• Periodic Health Check defaults to 30 days

The invitation is what lets GCXONE verify and connect to your Hub or NVR, so it has to be accepted before you add the device. In AJAX PRO Desktop go to Space Settings, Security Companies, Invite via Email and send the invitation to Ajax@nxgen.io. After the device is added in GCXONE, open its overview page for the SIA receiver details and add that receiver in AJAX PRO Desktop under Company, CMS connection, Add Receiver, with the protocol set to SIA DC-09.

• Hub ID is needed for an AJAX Hub, Device ID for an AJAX NVR
• Receiver IP, port and encryption key are set at Company Level
• Account Number is set at Object Level and Format must be ADM-CID

Make sure RTSP port 554 and the HTTP control port 443 are open, whitelist the CamectReceiver IP if you do not use NXGEN OpenVPN services, or configure the private IP address given by NXGEN if you do, and have Local Mode installed on operator workstations. On the hub, check the time zone, enable RTSP under Hub Settings and Cameras, and create a local NXGEN user with live view, query cameras, pan and tilt, view alerts, view footage, share cameras and change operating modes. Then under Hub Settings and Alert, enable Detect alerts, click Add Monitoring and choose NXGEN as the monitoring site, or IMMIX if NXGEN is unavailable, or XML over TCP if neither is listed.

• RTSP port 554 and HTTP control port 443 must be open
• Set the site ID to 1 as a dummy value and add the Genesis TCP address
• Add the cameras that must forward alarms to Genesis

Complete the required configurations in the Vivotek Vortex portal and have the API Key and External Group ID to hand, then add the device in GCXONE with Device Name, API Key and External Group ID and click Discover to fetch the available cameras. Custom properties must also be configured at the Service Provider level, and discovery will not work without them. GCXONE does not currently have a UI for configuring custom properties directly.

• Required fields: Device Name, API Key, External Group ID
• Custom properties at Service Provider level are required for discovery
• Once onboarded: live streaming, playback, jumpback, events, I/O control, health check, arm and disarm

Open Video Viewer from the left navigation menu and use the Device Explorer panel on the left to browse the cameras you have access to, expanding an NVR or device group to see its cameras. Drag a camera into the viewer area and it starts streaming. Then pick a layout from the bottom toolbar, either a single view or a grid such as 2x2, 3x3 or 4x4. You need at least one customer or site with devices and sensors configured, and the Operator role gives you the viewer.

A loading spinner with no video, a black screen or an "Unable to start stream" error usually points to device availability, permissions or the network rather than the viewer itself. Start by confirming the device is online in the Device Explorer and that your account has Live View or Operator permissions on that source device, then check the streaming configuration and test network connectivity. If the device is reachable but still silent, restart the camera or device. Clearing the browser cache is part of the standard checklist before contacting support.

• Verify the device shows online in the Device Explorer
• Confirm Live View or Operator permissions on the source device
• Check that ports 554, 80 and 443 are open and not blocked by the firewall
• Restart the camera or device, then clear the browser cache and reload

Press R to reload the stream. That refreshes a lagging or frozen feed and is worth trying before you escalate it as a connectivity issue. The same toolbar carries S to stop the stream, J to jump back to a point before the current timestamp, A to listen to the camera microphone, O for two-way audio through its speaker where the camera supports it, and plus and minus for digital zoom. PTZ controls sit on the right of the toolbar and show PTZ Unavailable when the camera does not support them.

• Reload [R] refreshes a frozen or lagging stream
• Jump Back [J] rewinds to before the current timestamp
• PTZ Preset jumps the camera to a saved position

Open the Video Viewer, then the Device Explorer from the left panel, where cameras are organised by customer, site and device. Drag and drop a site, device or sensor onto the grid, or double-click it in the device tree, and streaming starts immediately. Each tile carries its own stream controls so you can refresh, close, freeze or resume a feed without touching the others. You can switch between 1x1, 2x2, 3x3 and 4x4 grid layouts at any time without interrupting active streams.

• Browse the camera tree in the Device Explorer by customer, site and device
• Drag and drop onto the grid, or double-click a sensor in the tree
• Switch grid layouts instantly without stopping active streams
• Save the current arrangement with Save View for one-click recall