---
title: "Cathexis VMS"
source: /gcxone/devices/cathexis
locale: en
updated: 2026-09-27
---
## Introduction

The GCXONE–Cathexis integration connects the Cathexis video management environment with GCXONE, allowing video and event information from a Cathexis installation to be available within the GCXONE monitoring workflow.

CathexisVision acts as the video management layer, managing connected cameras, live and recorded video, integrated devices, alarms, and supported camera functions such as PTZ. Cathexis also provides an integration framework for connecting external systems and devices through its integration database and API.

Through this integration, GCXONE communicates with the configured Cathexis server and retrieves the required camera and event information. Camera streams can be accessed through the Cathexis interfaces, while device and event information can be used by GCXONE for monitoring and alarm handling.

### Scope of Integration

The GCXONE–Cathexis integration is focused on bringing the required video and event capabilities from a CathexisVision system into GCXONE.

For a configured Cathexis system, GCXONE can support the following integration areas:

- **Camera discovery and identification** — Retrieve the available cameras and use their Cathexis camera IDs for further operations.
- **Live video** — Access the camera's live stream through the Cathexis video interface.
- **Recorded video** — Access recorded footage associated with a camera when required for event investigation.
- **Reference images** — Retrieve a camera reference image for identification or event presentation.
- **PTZ control** — Control supported PTZ cameras and perform supported PTZ operations, including preset-related functions.
- **Device and camera events** — Receive Cathexis event and technical alarm information, including the associated camera details where provided.
- **Event-associated video** — Use the camera and review-track (recorded video) information included with an alarm to identify the relevant video associated with an event.
- **Integration with Cathexis devices and objects** — Cathexis uses its integration framework to associate integrated devices and their objects with cameras and events.

### System Architecture

![Architecture diagram showing cameras and integrated devices feeding CathexisVision, which connects over HTTP/HTTPS on port 33104 to the GCXONE integration layer and on to operators in the monitoring layer.](/api/media/file/01-system-architecture-edited-cefe7fbd.png?prefix=media)

#### Field Layer – Cameras and Video Devices

This is the physical layer where video and related device data originate.

It can include:

- IP cameras
- Video units / encoders
- I/O devices
- Cameras with supported analytics or event capabilities

CathexisVision manages these devices and provides access to their video, status, and supported functions. Depending on the camera capabilities, Cathexis can provide live feeds, recorded video, PTZ functions, and camera events.

#### Cathexis Platform Layer – CathexisVision

The CathexisVision server acts as the **video management layer** between the physical devices and GCXONE.

It is responsible for:

- Managing connected cameras and video resources
- Recording and providing access to stored video
- Managing camera availability and configuration
- Processing supported events and alarms
- Providing camera resources, live feeds, and review tracks
- Providing supported PTZ and I/O functions

The Cathexis API provides GCXONE with access to these resources through authenticated API interfaces.

#### Integration Layer – GCXONE

The **GCXONE integration layer** connects to the CathexisVision environment and retrieves the resources GCXONE needs.

At this layer, GCXONE:

- Discovers and identifies available cameras
- Retrieves camera information and available streams
- Accesses live and recorded video
- Handles supported PTZ operations
- Retrieves reference images where required
- Receives and processes supported event and alarm information

Cathexis provides camera IDs, live-feed URLs, review tracks (recorded video), and supported PTZ information through the API, which GCXONE uses to perform these operations.

#### Monitoring Layer – GCXONE

The monitoring layer is where the integrated Cathexis information becomes available to operators through GCXONE.

Operators can use GCXONE to:

- View live camera video
- Review recorded footage where supported
- Receive and investigate alarms and events
- Access supported PTZ controls

This layer provides the operator-facing view while CathexisVision continues to manage the underlying video infrastructure and recording environment.

## Cathexis Configuration

This section describes the CathexisVision configuration required before connecting the system to GCXONE. Complete the steps in the order below so that cameras, video streams, events, and technical alarms are available to the GCXONE integration.

>  **Note:** The exact options available can vary depending on the CathexisVision version, installed drivers, and licensed features.

### Step 1: Create or Select the Cathexis Site

A **Site** groups the Cathexis servers and resources that belong to the same deployment. Cameras and integrated devices are configured on the servers within the site. If the Cathexis server is already installed as a single-server site, use the existing site rather than creating another one.

**Navigation:** File → Enterprise manager

Create or select the required site and verify that the Cathexis server is available.

![CathexisVision Enterprise manager tab listing the available site.](/api/media/file/02-enterprise-manager-edited-42f93ed9.png?prefix=media)

### Step 2: Add and Verify Cameras

Add the cameras that will be monitored through GCXONE.

**Navigation:** Site → Open → Setup → Configure Servers → Cameras

Click **New** to open the **New camera** wizard. Cathexis provides the required connection fields based on the selected camera driver.

Enter the required connection details:

- **Driver**
- **IP address**
- **Video input**, if applicable
- **Port**
- **Login** (camera username)
- **Password** (camera password)

#### Camera Driver Selection

Cameras can be added using either the **camera-specific driver** or the **Generic Encoder** driver.

- **Camera-specific driver:** Supports the integration capabilities provided by the selected driver, including streaming, events, and PTZ where supported.
- **Generic Encoder:** Can be used when a camera-specific driver is not available. With the Generic Encoder driver, live streaming and events are supported, but PTZ control is not available.

>  **Recommended:** Use the camera-specific driver whenever the required camera model is supported. Use Generic Encoder when only streaming and event functionality is required.

The camera should be successfully connected and displaying video before continuing.

![New camera dialog with the Driver, IP address, Video input, Port, Login, and Password fields.](/api/media/file/03-new-camera-dialog-edited-3e7bd8c5.png?prefix=media)

#### Camera Verification

After adding the camera, verify that:

- Live video is available.
- The camera is not showing a connection fault.
- The required recording configuration is available if playback is required.

This ensures GCXONE can retrieve the camera information and video resources through Cathexis.

### Step 3: Configure the GCXONE API Base Station

For event delivery, Cathexis uses an **API Base Station** as the destination for alarms.

The Base Station should point to the **GCXONE service endpoint** that receives Cathexis alarms.

**Navigation:** Site → Setup → Configure Servers → Base-stations

Create a new Base Station and select:

- **Name:** A descriptive name, such as API-BASE
- **Type:** API
- **Address:** `https://cathexisproxy.nxgen.cloud/eventIngest`
- **Port:** 443
- **User:** Enter the device's unique identifier from GCXONE. GCXONE uses it to match incoming alarms to the correct device.

Cathexis supports API-type Base Stations for sending alarms to an external system.

![Server Base-stations tab with the configured API Base Station listed and the New button highlighted.](/api/media/file/04-base-stations-tab-edited-42f5da5b.png?prefix=media)

![Edit API-BASE dialog with Type set to API, the cathexisproxy.nxgen.cloud/eventIngest address, port 443, and the User field.](/api/media/file/05-edit-api-base-dialog-edited-a0d2c610.png?prefix=media)

>  **Important:** The GCXONE endpoint must be reachable from the Cathexis server. Network/firewall rules should allow the Cathexis server to send the alarm requests to the configured GCXONE endpoint.

### Step 4: Configure Event Alarms

Cathexis events determine **when an alarm is generated and what action should be performed**.

Before creating an event, ensure that the required resources are already configured, such as:

- Camera
- Video analytics or motion trigger, if required
- Recording database (see Step 7)
- Other required inputs or triggers

Cathexis recommends configuring these resources before creating the event.

**Navigation:** Site → Setup → Configure Servers → Events

Click **New** to create the required event.

Configure the event according to the required monitoring scenario and select the appropriate trigger (motion recordings are recommended). Set the trigger **Hold time** to **0** so that events are sent to GCXONE immediately.

![New event dialog on the General tab, with the Name, Description, Schedule, and Priority fields.](/api/media/file/06-new-event-general-tab-edited-ae7d3314.png?prefix=media)

![New trigger dialog with Trigger while set to motion, Hold time set to 0 sec, and Schedule set to Always.](/api/media/file/07-new-trigger-dialog-edited-c0fd201f.png?prefix=media)

#### Event Description

- **Name:** Enter a clear alarm name (optional).
- **Description (important):** Enter `$input_name`.

The **Description** configured for the event will be included in the alarm information sent through the Cathexis API.

### Step 5: Configure the Event to Call the GCXONE Base Station

After creating the event trigger, configure its action so that the alarm is sent to the GCXONE API Base Station.

On the event **Actions** tab, click **New** and add both **Record camera** and **Call base-station**. Both are required so that camera information is sent along with each event.

Select the **GCXONE API Base Station** you created in Step 3 as the destination.

Cathexis supports a primary **First try** Base Station and an optional **Then try** Base Station if a secondary destination is required.

Select all check boxes on the **Call base-station** and **Alarm preview** tabs.

On the **Resources** tab, select **Use trigger resources** at the bottom.

![New event Actions tab with Record camera and Call base-station highlighted in the New menu.](/api/media/file/08-event-actions-tab-edited-d2afeb16.png?prefix=media)

![Call base-station dialog on the Alarm preview tab, with Enable alarm preview, Use trigger cameras, and Include trigger info checked, and the pre- and post-event image counts.](/api/media/file/09-call-base-station-alarm-preview-edited-72c9792f.png?prefix=media)

![New event Resources tab with Use trigger resources checked.](/api/media/file/10-event-resources-tab-edited-b05a6618.png?prefix=media)

### Step 6: Configure Technical Alarms

Technical alarms are used for system or infrastructure conditions rather than normal camera events.

Examples supported by Cathexis include:

- Camera faults
- Database problems
- Disk errors
- Network connectivity
- Recording failure
- Software failure
- Integration database issues
- Server monitoring conditions

**Navigation:** Site → Setup → Configure Servers → Technical alarms

Create the individual technical alarms required for the deployment.

For each technical alarm, configure:

- Descriptive alarm name (optional)
- Required technical condition
- **Repeat alarms at most once every**, where required
- **Call base-station** enabled, with the GCXONE API Base Station selected

![Technical alarms list with Call-basestation enabled and API-BASE assigned for each alarm.](/api/media/file/11-technical-alarms-list-edited-2dce46e6.png?prefix=media)

![Edit CameraFaults dialog with Call base-station checked and API-BASE selected as First try.](/api/media/file/12-edit-camerafaults-dialog-edited-950421af.png?prefix=media)

### Step 7: Configure the Database

Cathexis integrations use a dedicated **Database**. If the database has not previously been initialized on the server, initialize it before configuring the integration.

**Navigation:** Site → Setup → Databases

If required:

1. Initialize the database.
2. Select the appropriate partition.
3. Allocate the required database size.
4. Create the required integration database.

The Database is used by Cathexis to store integration-related data and events.

![Server Databases page showing the recording databases and partition usage, with the New button highlighted.](/api/media/file/13-databases-edited-cc788112.png?prefix=media)

### Step 8: Configure Integration Devices

If the GCXONE integration uses Cathexis **Integration Devices**, configure them through the **Integration devices** panel.

**Navigation:** Setup → Configure Servers → Integration devices

Click **New device**, select the appropriate driver, and continue with the device configuration.

Cathexis provides configuration tabs for the integrated device, including Objects, Object Properties, Device Events, Object Groups, and General information, depending on the integration.

![Integration devices page with New device highlighted and the Select a driver list open.](/api/media/file/14-integration-devices-edited-1a2d0233.png?prefix=media)

### Configure the Cathexis API

>  **Important:** GCXONE uses the **Cathexis API** to retrieve information such as site details, camera resources, live feeds, recorded tracks, reference images, and supported controls. The Cathexis API uses the standard HTTP API port **33104/TCP**. If HTTPS is required, use an SSL/TLS proxy in front of the API, as described in the Cathexis API documentation.

## Cathexis Config Guide with GCXONE

### Configuration Requirements

When you add the Cathexis device in GCXONE, enter the following details:

1. **Device:** Cathexis
2. **Name:** A name for the device.
3. **IP Address Or Host Name:** The IP address or hostname of the Cathexis server accessible from GCXONE.
4. **User Name:** Valid Cathexis user credentials with the required API access.
5. **Password:** Password for the configured Cathexis user.
6. **Enable Https:** Enable this option if the Cathexis API is configured to use HTTPS.
7. **HTTP Port:** The HTTP port configured for Cathexis API communication.
8. **HTTPS Port:** Enter the HTTPS port when HTTPS is enabled.
9. **Timezone:** Select the device timezone.

![GCXONE Edit Device dialog with Device set to Cathexis, showing the connection settings (IP address, username, password, Enable HTTPS, HTTP port 33104) and the timezone.](/api/media/file/16-gcxone-edit-device-edited-7c311c6a.png?prefix=media)