---
title: "Geutebrück"
source: /gcxone/devices/geutebrck
locale: en
updated: 2026-09-14
---
## Introduction

This guide describes the steps required to integrate Geutebrück with the GCXONE platform. Geutebrück is a professional Video Management System (VMS) that provides recording, live viewing, video playback, and event/alarm management for connected cameras and security hardware. GCXONE integrates directly with Geutebrück, allowing streams and events from G-Core servers to appear alongside other devices in the GCXONE platform.

| Web API Interface (HTTPS) | Port 13333 |
| --- | --- |
| RTSP Streaming | Port 554 |

Applications

• G-Set: system configuration client — used to add hardware, configure media channels, and set up event and behaviour rules.

• G-View: operator client for live viewing, playback, and event monitoring.

• GPLC Simulator: PLC test simulator for I/O and manual event workflows, used during testing.

## Geutebrück Configuration

A. Starting G-Core

G-Core is the server component of Geutebrück. It must be running before G-Set or G-View can connect. Start it from the Command Prompt as Administrator:

1. Open Command Prompt as Administrator.
2. Navigate to the G-Core installation folder: cd %gngpath%
3. Stop any running instance: GCoreServer.exe stop
4. Start G-Core — use Demo mode for testing (GCoreServer.exe demo) or Licensed mode for production (GCoreServer.exe start).

![G-Core running in Demo mode — server started and connected to the SQL database.](/api/media/file/blob-edited-2f2e6cb3.png?prefix=media)

*G-Core running in Demo mode — server started and connected to the SQL database.*

B. Connecting G-Set to the Server

Once G-Core is running, launch the G-Set client and connect to the server using the Connection Wizard.

**Step 1:** Open G-Set. Click **Connection Wizard** on the main screen.

![G-Set main screen — click Connection Wizard to begin.](/api/media/file/blob-1--edited-d649055b.png?prefix=media)

*G-Set main screen — click Connection Wizard to begin.*

**Step 2:** Enter the **Connection name**, **Host name** (G-Core server IP), **Username**, and **Password**. Default credentials: username = sysadmin, password = masterkey. Click **Ping Host** and **Check Connection** to verify, then click **OK**.

![Connection Wizard form — enter host details and verify connectivity before saving.](/api/media/file/blob-2--edited-d7a1a161.png?prefix=media)

*Connection Wizard form — enter host details and verify connectivity before saving.*

**Step 3:** In the Connections panel, right-click the connection and select **Connect**.

![Right-click the connection name and select Connect to establish the session.](/api/media/file/blob-3--edited-40164ca8.png?prefix=media)

*Right-click the connection name and select Connect to establish the session.*

C. Adding Hardware (IP Camera)

Hardware in G-Set represents the physical camera device. Each camera is added as an IP-Camera plugin module.

**Step 1:** In the left panel, expand **Media channels / Hardware** and click **Hardware**.

**Step 2:** In the Hardware module list, right-click and select **Add**.

![Hardware module list — right-click and select Add.](/api/media/file/blob-4--edited-a67a7f43.png?prefix=media)

*Hardware module list — right-click and select Add.*

**Step 3:** In the **Add hardware module** dialog, select **IP-Camera Plugin \<ONVIF IPC\>** and click **Add**.

![The Add hardware module dialog in Geutebrück G-Set with the ONVIF IPC plugin highlighted among the camera plugins, and the Add button marked.](/api/media/file/blob-5--edited-0fa3c7b7.png?prefix=media)

*Select IP-Camera Plugin \<ONVIF IPC\> and click Add.*

**Step 4:** Configure the hardware module and click **Save**:

| Name | Descriptive name for the module (e.g., SCT-Entrance) |
| --- | --- |
| Hostname | IP address of the camera |
| Username | Camera login username |
| Password | Camera login password |

![Hardware configuration panel — enter camera name, hostname, and credentials.](/api/media/file/blob-6--edited-cef91666.png?prefix=media)

*Hardware configuration panel — enter camera name, hostname, and credentials.*

D. Adding a Sensor (Media Channel)

A media channel in G-Set is what GCXONE recognises as a sensor. It links a video stream from a hardware module to the GCXONE device.

**Step 1:** In the left panel, click **Media channels** under Media channels / Hardware.

**Step 2:** Right-click in the list and select **Add**.

![Media channel list — right-click and select Add.](/api/media/file/blob-7--edited-219aa0d9.png?prefix=media)

*Media channel list — right-click and select Add.*

**Step 3:** In the **Module channels** dialog, select the hardware module you just created and click **Add**.

![Module channels dialog — select the hardware module (e.g., Module channel 1 on <SCT-Entrance>) and click Add.](/api/media/file/blob-9--edited-2f1370af.png?prefix=media)

*Module channels dialog — select the hardware module (e.g., Module channel 1 on \<SCT-Entrance\>) and click Add.*

**Step 4:** Enter the channel details and click **Save**:

| Name | e.g., SCT-Entrance |
| --- | --- |
| Description | e.g. This is entrance camera |

![Geutebrück G-Set media channel configuration, with the Name and Description fields for SCT-Entrance highlighted above the media channel source and numbering settings.](/api/media/file/blob-10--edited-3bc5b86b.png?prefix=media)

*Media channel settings — enter the channel name and description.*

**Step 5:** Select the channel in the tree, open **Permanent recording**, enable it, and click **Save**. The sensor is now added and linked.

![Permanent recording enabled for the media channel.](/api/media/file/blob-11--edited-9a452e62.png?prefix=media)

*Permanent recording enabled for the media channel.*

G-View Application

G-View is the operator client used to watch live feeds, review recorded footage, and monitor events.

**Step 1:** Launch G-View. In the **Video servers** panel, right-click the server name and select **Connect**.

![G-View — right-click the server and select Connect.](/api/media/file/blob-12--edited-ac439803.png?prefix=media)

*G-View — right-click the server and select Connect.*

**Step 2:** Expand the server tree. Double-click a media channel to open its live stream.

**Step 3:** Use the playback controls and the Event / MOS timeline tabs to review recorded footage and jump to event markers.

![Geutebrück G-View playing back footage from the SCT-Entrance camera, with the channel highlighted in the tree on the left and a timeline and transport controls below.](/api/media/file/blob-13--edited-90ee108c.png?prefix=media)

*G-View live feed — SCT-Entrance channel streaming with timeline visible.*

## Geutebrück Config Guide with GCXONE

A. Add a Geutebrück Device

Register the Geutebrück G-Core server as a device under the target site.

**Step 1:** Navigate to the target site in the Configuration app, open the **Devices** tab, and click **Add New**.

![Site Devices tab — click Add New to register a new Geutebrück device.](/api/media/file/blob-14--edited-e0a3f598.png?prefix=media)

*Site Devices tab — click Add New to register a new Geutebrück device.*

**Step 2:** In the **Add Device** dialog, open the **Device** dropdown and select **Geutebrueck**, then enter all required fields: Name, IP Address or Host, User Name, Password, Server Port, HTTPS Port, RTSP Port, Control Port. Server Port, HTTPS Port, and RTSP Port default to 13333, 13333, and 554 respectively, matching G-Core's default configuration.

![The Add Device dialog with Geutebrueck chosen, showing the name field and connection settings for address, credentials, server port, HTTPS port and RTSP port.](/api/media/file/blob-15--edited-7fac2684.png?prefix=media)

*Add Device dialog — select Geutebrueck as the device type and fill in the server connection details.*

**Step 3:** Below the connection fields, the dialog also has a **Select Entity Group** dropdown, an **Enable Audio** toggle (on by default), a required **Timezone**, a **Device Configuration** section (Site Pulse Configuration), an **Advanced Settings** section (Event Polling, Configure Heatmap Mask, Periodic Health Check, Event Retention Time — 30 days by default), and an optional **Location** section (Latitude, Longitude, Plus Code, What3Words).

**Step 4:** Click **Discover** to confirm GCXONE can reach the device, then click **Save**.

B. Verify the Live Stream in GCXONE

Once saved, sensors from G-Set appear under the device in GCXONE. Open any sensor in the Video Viewer to confirm the live stream is active.

![GCXONE Video Viewer — live stream from the Geutebrück-connected camera confirmed.](/api/media/file/blob-16--edited-33e1fbf4.png?prefix=media)

*GCXONE Video Viewer — live stream from the Geutebrück-connected camera confirmed.*

Event Rule Configuration in G-Set

Event rules define what triggers an alarm, how the system responds, what is recorded, and how the alarm appears in G-View and GCXONE. The Event/Alarm Wizard guides you through five steps.

To open the wizard: in G-Set navigate to **Events / Behaviour Rules** → **Events**, right-click in the event list and select **Add**.

Step 1 — Event Settings

Enter the event name, configure timing, and set database storage options.

**•Event name:** enter a descriptive name (e.g., VMD event).

**•Retrigger mode:** set to Retrigger to allow the event to restart while already active.

**•Store to database:** ensure On start and On stop are enabled so events appear in logs.

![Step 1 — Event Settings. Configure the event name, ring buffer, retrigger mode, and database logging.](/api/media/file/blob-17--edited-c5095f67.png?prefix=media)

*Step 1 — Event Settings. Configure the event name, ring buffer, retrigger mode, and database logging.*

Step 2 — Action Settings

Define which alarm actions start and stop the event by dragging items from the Action list into the Start by and Stop by zones.

**•Start by:** G-Tect/VMD alarm — triggers the event when motion is detected.

**•Stop by:** G-Tect/VMD alarm finished — ends the event when motion stops.

![The Action settings step in Geutebrück G-Set, with a G-Tect VMD alarm as the start trigger and the action list open on G-Tect/VMD alarm finished.](/api/media/file/blob-18--edited-3e46b2de.png?prefix=media)

*Step 2 — Action Settings. G-Tect/VMD alarm assigned as the Start action. The Action list shows all available triggers.*

Step 3 — Recording Settings

Assign the media channels to record when the event fires by dragging them from the channel list into the Recording channels drop zone.

![Step 3 — Recording Settings. SCT-Entrance is available in the media channels list.](/api/media/file/blob-19--edited-3934afba.png?prefix=media)

*Step 3 — Recording Settings. SCT-Entrance is available in the media channels list.*

Step 4 — Alarm Settings

Configure the alarm that appears in G-View and GCXONE when the event fires.

**•Alarm name:** e.g., test or VMD alarm.

**•Alarm priority:** High, Medium, or Low.

**•Media channels:** drag the camera channel so the alarm opens its feed automatically.

**•Default alarm scene:** enable to display the camera when the alarm is acknowledged.

![Step 4 — Alarm Settings. Alarm name, priority, and associated media channel are configured.](/api/media/file/blob-20--edited-3b254002.png?prefix=media)

*Step 4 — Alarm Settings. Alarm name, priority, and associated media channel are configured.*

Step 5 — Summary

Review the complete configuration in one table, then click Save & Finish to commit the event rule.

![Step 5 — Configuration Summary. VMD event with G-Tect/VMD alarm trigger, SCT-Entrance recording, and test alarm confirmed.](/api/media/file/blob-21--edited-62857483.png?prefix=media)

*Step 5 — Configuration Summary. VMD event with G-Tect/VMD alarm trigger, SCT-Entrance recording, and test alarm confirmed.*

Reviewing the Event Configuration

After saving, clicking an event in the G-Set Events tree opens its full configuration — including the event tree, recording task, media channels, and playback profile.

![Event configuration detail — VMD event tree showing Recording tasks, StartBy, StopBy, and recording profile at 25 fps on SCT-Entrance.](/api/media/file/blob-22--edited-43e066d9.png?prefix=media)

*Event configuration detail — VMD event tree showing Recording tasks, StartBy, StopBy, and recording profile at 25 fps on SCT-Entrance.*

**Note:** Once events are saved in G-Set, they are automatically transmitted to GCXONE via the device integration. No additional configuration is required in GCXONE to receive Geutebrück events — they appear in the GCXONE event log alongside other device events.

## Troubleshooting

Viewing Event Logs in G-View

All triggered events are logged in the G-View Event list. A populated log confirms the device is online and events are being captured correctly.

**Step 1:** Open G-View and connect to the server.

**Step 2:** In the top menu bar, click **View** then select **Event list**.

![G-View — View menu with Event list highlighted.](/api/media/file/blob-24--edited-26168248.png?prefix=media)

*G-View — View menu with Event list highlighted.*

**Step 3:** The Event list opens. Each entry shows:

| Start time | Timestamp when the event was triggered |
| --- | --- |
| Event name | Name assigned in Step 1 of the Event Wizard |
| Stop time | Timestamp when the event ended |
| Text / Description | Description text set in the event configuration |

![G-View Event list — VMD events logged with start time, stop time, event name, and description. A populated log confirms end-to-end integration.](/api/media/file/blob-23--edited-64a1c452.png?prefix=media)

*G-View Event list — VMD events logged with start time, stop time, event name, and description. A populated log confirms end-to-end integration.*

A populated event log confirms that events configured in G-Set are successfully captured, stored, and visible in G-View — validating the complete Geutebrück integration from device to GCXONE.

For technical support or integration assistance, contact NXGEN Technology AG through the GCXONE support portal.