Axis Camera Station Pro

Introduction

This guide describes the steps required to integrate AXIS Camera Station Pro (ACS) with the GCXONE platform. ACS is a professional Video Management System (VMS) from Axis that provides recording, live viewing, video playback, and event/alarm management for connected cameras and security hardware. GCXONE integrates directly with ACS via its API, allowing streams and events from an ACS server to appear alongside other devices in the GCXONE platform. This document is based on AXIS Camera Station Pro version 6.15.15482 and ACS API version 2.39.

Integration capabilities

1. Video: when an alarm is triggered, the relevant camera can be automatically displayed live in the Video Viewer, for example:

• Camera views in 1/2x2, 3x3, and 4x4 layouts are supported, and desired cameras can be dragged into the window.
• Recordings can be played back directly from the NXGEN client.
• Recordings can be rewound by a specific amount of time.
• PTZ cameras can be controlled directly from the NXGEN client, including access to predefined presets.

1. Intercom: NXGEN's integrated cloud SIP server establishes bidirectional audio with Axis speakers and intercoms via SIP (VoIP).
2. Audio: live announcements or stored audio clips can be played to selected network speakers from the NXGEN client.
3. Controls to and from ACS Pro: virtual buttons created in the NXGEN client can trigger ACS Pro HTTPS (external) triggers, for example:

• Setting a bookmark or sending an HTTP notification to another system
• Sending a message to the ACS Pro mobile app
• Enabling or disabling one or more Action Rules
• Opening one or more doors once, permanently, or switching to lockdown mode

Conversely, using ACS Pro Action Rules, any ACS Pro trigger (such as VMD or AXIS Object Analytics) can generate an alarm event in GCXONE via an HTTP POST request to acsproxy.nxgen.cloud/eventIngest.

1. Device control: AXIS speakers, I/O devices, intercom relay contacts, and strobe sirens are controlled directly (via port forwarding), enabling functions such as:

• Activating and deactivating a strobe siren
• Playing an audio clip on a speaker
• Playing an audio clip on one or more audio zones via integration with AXIS Audio Manager Pro
• Activating a relay on an I/O module, an output on a camera, or on another Axis device
• Activating a virtual input on a camera or another Axis device

I/O device connections (e.g. on the A9188 and A9210) are detected via port forwarding, with locally assigned input/output names shown through the discovery function and whether each I/O is configurable as an input or output indicated accordingly.

Axis Camera Station Pro Configuration

1. Prerequisites

This guide is based on AXIS Camera Station Pro version 6.15.15482 and ACS API version 2.39. If you are using a different version and something does not work as described, contact NXGEN. The abbreviation "ACS" used throughout this guide refers to "AXIS Camera Station Pro."

2. Video Connection Checklist

Internet access:

1. A static IPv4 address for the system is required.
2. Open port 29204 on the router (ACS Pro API). If the provider restricts ports to a specific range (e.g., due to DS-Lite), port forwarding is required.
3. Check the port's accessibility from the Internet using an online tool, e.g. portchecker.co.

ACS Pro:

1. Integrate cameras and assign unique, identifiable names.
2. Set up continuous recording for all cameras at native resolution.
3. Create a user account with the "Operator" role, including a name and password.
4. Create rules for the required alerts (VMD or AOA).
5. Create presets for PTZ cameras.

Speakers, intercoms, strobe sirens, and relay modules (direct integration into NXGEN):

1. IP address, username, and password for each device.
2. Pin assignments for I/O or relay outputs.

3. Installing ACS Pro

Axis Video Recorders: Axis offers two preconfigured recorder series — the S12 Recording Server Series (the last two digits indicate the default license count, e.g. S1232 = 32 licenses, expandable) and the S21/S22 Appliance Series, all-in-one recorders with an integrated switch (the last two digits indicate both connected devices and included licenses). A user manual for each recorder is available at axis.com/de-de/support — search the recorder model (e.g. S2216). Connect the recorder to the Internet to install updates and license the device, and document all created users and passwords.

Using Your Own Server: if you prefer not to use an Axis video recorder, check the release notes at axis.com/de-de/products/axis-camera-station-pro/support for supported Windows versions and hardware/software requirements. If unsure about hardware specs, use an Axis video recorder with an equal or higher device count as a sizing reference (e.g. for 73 cameras + 2 door controllers + 5 intercoms = 80 devices, reference the S1296 server). Download the "AXIS Camera Station Pro – Update for Server and Client" ZIP file from the same page, unzip it, and run the Windows installer (e.g. AXISCameraStationPro_6.15.15482) following the installer's instructions.

4. Settings in ACS

4.1 Communication

Communication with an ACS system is encrypted via HTTPS. By default, TCP port 29204 is used. This port is configured in ACS under "AXIS Camera Station Pro Service Control" on the "General" tab (right-click). The key field is "Port range" — typically 29200–29250. The ACS API port is always the lower limit of this range plus 4 (e.g. 29200 + 4 = 29204). If a different range is configured, enter the lower limit plus 4 in the "Server Port" field of the NXGEN configuration.

Figure — Right-click the ACS tray icon and select "Open AXIS Camera Station Pro Service Control."

Figure — Service Control window, General tab, Ports range field.

4.2 Integrating Cameras and Setting Up Recording

Add the camera and set the recording method to "Continuous."

Set the continuous recording profile to "High" (the camera's native resolution).

Figure — Adding a camera with Continuous recording and High profile.

4.3 Time Synchronization

Ensure the device has the correct time set. It is strongly recommended to use an NTP server so that time remains synchronized between NXGEN and the recorder. On a Windows 11 Pro server (ACS Pro runs on Windows 11), configure the NTP server via the time synchronization settings:

1. Open Control Panel → Clock and Region → Date and Time.
2. Go to the Internet Time tab and click Change settings.
3. Check "Synchronize with an Internet time server."
4. Enter your NTP server (e.g. "ntp.axis.com" or your own) in the Server field.
5. Click Update Now → OK.

When a device (camera, door controller, I/O device, intercom, etc.) is added to ACS Pro, it automatically inherits the NTP time from the ACS Pro server; this can be customized per device if needed.

Figure — Windows Internet Time settings and per-device time customization.

4.4 User Setup

1. In Windows Computer Management, create a user account for access (e.g. named NXGEN).

Figure — Creating the NXGEN user account in Windows Computer Management.

2. Add the user to ACS and assign the "Operator" role.

Figure — Adding the NXGEN user to ACS with the Operator role.

3. Assign camera access rights to this operator.

Figure — Assigning camera access rights to the operator.

4.5 Set Up an Alarm Zone on the Camera

On the camera, set up a detection zone for motion detection (VMD) — in this example named "Profile 1." NXGEN's cloud-based AI evaluates the alarm images received from ACS and applies object filters. You can also use AXIS Object Analytics on the camera to classify people or vehicles specifically and reduce false alarms.

Figure — VMD detection zone "Profile 1" on the camera.

4.6 Create an Alarm Rule and Logging

Create a rule in ACS. Select "Profile 1" from the camera's VMD as the trigger. As the action, create an HTTPS POST request to NXGEN with the exact specification below.

Figure — Creating a new rule in ACS with the camera's VMD trigger and an HTTPS POST action.

Two IDs from NXGEN are required: "authenticationToken" and "genesisCamId" (see "Trigger from ACS" in the Config Guide section for where to retrieve these).

Figure — HTTPS POST action fields: URL, method, and payload.

URL: https://acsproxy.nxgen.cloud/eventIngest

{ "initialRequest": { "payload": { "type": "NOTIFICATION", "authenticationToken": "<authenticationToken>", "notifications": [ { "event": { "type": "ALARM_TRIGGERED", "genesisCamId": "<genesisCamId>", "timestamp": "$(TriggerData.TimeUtc)", "cameraId": "$(TriggerData.SourceId)" } } ] } } }

Figure — Testing the connection to NXGEN after entering the authenticationToken and genesisCamId.

Once the two required IDs have been entered, you can test the connection to NXGEN.

Typically, add a second action, "Raise Alarm," to generate a logged alarm in ACS Pro. Enter a title and description for precise localization.

The "Logs" view then displays the alarms recorded and stored in the ACS database.

Figure — Raise Alarm action and the ACS Logs view.

Axis Camera Station Pro Config Guide with GCXONE

1. Create ACS Recorder

In the NXGEN client, add a new device ("Add New" → ACS Recorder) under the location.

Figure — Devices tab, empty before adding the ACS Recorder.

Enter the IP address of the Internet connection and port 29204 (or the equivalent forwarded port configured on your router). Enter the operator created in ACS as the "User Name" and "Password." Select the correct time zone and click "Discover."

Figure — Add New ACS Recorder dialog: entering the IP address, port, operator credentials, and time zone.

The serial number of the ACS recorder is read automatically during import. Cameras integrated into ACS and enabled for the user account are automatically displayed and added to the NXGEN client, and can be saved by clicking "Save."

Figure — Discovered device with its cameras listed, ready to Save.

2. Assign and Configure Camera Type

For the camera/sensor, go to its settings page via "Actions" → "Edit." Under General Information you can select the camera type (e.g. PTZ).

Figure — Actions menu → Edit, to open the camera's settings page.

Figure — General Information: selecting the camera type (PTZ).

Select "Actions" → "View" to switch to a video stream layout where you can access image masking.

Figure — Actions → View, switching to the video stream layout for masking.

Image areas can be temporarily or permanently deactivated for recurring false alarms (trees, headlights, etc.):

Figure — Image masking options in the video stream layout.

use "Timed Mask" (shown in blue) for a specific period

Figure — Timed Mask (blue), for temporary deactivation.

"Camera Mask" (shown in red) for permanent deactivation.

Figure — Camera Mask (red), for permanent deactivation.

3. Video Viewer

In the Video Viewer, camera views are available in 1/2x2/3x3/4x4 layouts; cameras can be dragged into the desired window.

Recordings stored in ACS can be viewed by selecting a specific time and date. A PTZ camera can be moved and zoomed using the on-screen controls, and preset positions stored in the camera can be accessed; keyboard shortcuts are available. Creating "tags" lets you assemble, label, and save layouts for system-specific, user-friendly overviews.

Figure — Video Viewer layouts, PTZ controls, and tags.

4. Map

Cameras can be placed on the map based on their mounting position, with Map and Satellite display options. Colored text boxes can mark important areas or positions.

After saving a camera's position, clicking it on the plan shows the live image, geodata, active status, and an uploaded reference image (product photo or the actual mounting location) on the right.

Figure — Camera placed on the Map with live image panel.

5. Trigger from ACS

The ACS recorder's "Unique Reference Number," shown at the end of its URL, is the authenticationToken.

Figure — The ACS recorder's Unique Reference Number (authenticationToken) at the end of its URL.

In the example: 8e410bf4e4614c3094d621420f134aa7

Figure — Example authenticationToken value.

In the recorder's sensor overview, the "Sensor Reference Number" listed at the top for the desired camera is the genesisCamId — it can be copied via a button.

Figure — Sensor Reference Number (genesisCamId) in the camera's sensor overview, with copy button.

With both IDs, you can complete the ACS rule setup described in "Create an Alarm Rule and Logging" above to transfer the rule to NXGEN.

6. Video Activity Search

Alarms can be searched and displayed in the "Video Search" view. For a camera running simple Motion Detection (VMD), any movement in the alarm field (including shadows, animals, etc.) triggers an alarm; NXGEN's cloud-based AI evaluates and classifies each alarm as "false" or "true." You can filter by various criteria — for example, a detected vehicle appears as a true alarm (green dot) with a vehicle icon, while other alarms are marked "False Alarm" in red. Note that a privacy zone that pixelates part of the image limits AI detection accuracy in that area.

Figure — Video Search results: true alarms (green dot) and false alarms (marked in red).

Clicking an alarm shows more detail.

Figure — Alarm detail view after clicking a result.

Using the filter panel, you can search for real alarms within a specific time range and type (e.g. vehicles).

Figure — Filter panel for searching alarms by time range and type.

Selecting "24h," for example, might display 3 matching alarms. Hovering over a result automatically plays the video clip of the incident.

Figure — Filtering alarms by time range with hover-to-play preview.

7. Trigger to ACS

To create virtual buttons in the NXGEN client that execute actions in ACS, create an entry of type "Output" in the recorder's path under the IO tab.

Figure — IO tab: creating a new Output-type entry.

Enter the ACS API command in the "IO URL" field — for example, a TriggerFacade call with rising and falling edges, each 5 seconds long:

Figure — IO URL field with the TriggerFacade command.

https://IP-Address:Port/Acs/Api/TriggerFacade/ActivateDeactivateTrigger?{"triggerName":"NXGEN","deactivateAfterSeconds":"5"}

Figure — Trigger name and Display Name fields for the Output entry.

The trigger name is important — it is required in ACS. The "Display Name" is the name shown on the button in NXGEN. To enable the control in the Video Viewer and Map, click "Show on Salvo" in the row so it displays "Yes." A virtual button (e.g. named "Alarm") then appears automatically in the Video Viewer; clicking it sends the HTTPS message to ACS.

Figure — Show on Salvo enabled, making the virtual button appear in the Video Viewer.

In ACS, create an "Action Rule"

Figure — Creating a new Action Rule in ACS.

that uses the HTTPS message from NXGEN as the trigger; any desired function can be programmed as the action — for example, triggering an alarm and bringing a PTZ camera to the foreground with a "Live view alerts" panel showing the alarm image and message.

Figure — Action Rule using the NXGEN HTTPS message as the trigger, with a PTZ camera action.

Because the pulse lasts approximately 5 seconds, two messages are typically received (rising and falling edge).

Figure — Live view alerts panel showing the triggered alarm.

8. Connect IP Devices Directly to NXGEN

8.1 Relay Module

In the Object view, use "Add New" to add the device (e.g. an A9210) individually as an "Axis" device

Figure — Add New device dialog, adding the A9210 as an Axis device.

— communication happens directly with the Axis device, not via ACS. By default, TCP port 443 is used (in this example forwarded to port 6901 on the router). Enter the time zone and click "Search" to detect the device.

Figure — Entering the port and time zone, then clicking Search.

Figure — Relay module detected and ready to save.

Once detected, the device appears alongside the ACS recorder.

Figure — Relay module listed alongside the ACS recorder.

Click the location to assign the device type

Figure — Clicking the location to open the device's path.

— this displays the correct path in the address bar — then click "Sensors" and,

Figure — Sensors tab for the relay module.

under "Edit," change the relay module to "IOT."

Figure — Edit → changing the sensor type to IOT.

The system recognizes the relay module's inputs and outputs, viewable and labelable via "IO"

Figure — IO view listing the relay module's inputs and outputs.

— for example, name the relay output "Barrier" and set the switching pulse to 5–60 seconds in 5-second increments (default is continuous switching).

Figure — Naming an output ("Barrier") and setting the switching pulse.

All outputs (digital ports and relays) can be integrated into the diagram; clicking an output toggles it, with status shown by color. There may be a delay before the color-coded status updates with feedback from the device, during which the pop-up window is blocked.

Figure — Relay outputs shown in the diagram, with color-coded status.

Figure — Pop-up window for triggering an output.

All relay module buttons also appear in the Video Viewer with their assigned labels; a tag (e.g. "PTZ") can be assigned for display there, since devices like relay modules and speakers provide no video stream.

Figure — Relay module buttons in the Video Viewer, labeled with the assigned tag.

Figure — Relay module device overview in NXGEN, showing the assigned "PTZ" tag.

8.2 Speakers

Add the speaker individually via "Add New" using the location path in the Devices view, importing it as "GenesisAudio."

Figure — Add New device dialog, importing the speaker as GenesisAudio.

Direct communication is encrypted via HTTPS on TCP port 443 by default (in this example forwarded to port 6902). Enter the time zone and click "Discover" to detect the device —

Figure — Entering the port and time zone, then clicking Discover.

it appears in the list and is automatically set to the "speaker" device type.

Figure — Speaker detected and listed.

Figure — Device type automatically set to "speaker."

To establish SIP communication, click "Edit Device" to obtain the automatically generated login credentials for the NXGEN SIP server,

Figure — Edit Device, showing the auto-generated SIP login credentials.

then enter these credentials into the new SIP account you create for the speaker.

Figure — Entering the SIP credentials into the speaker's new SIP account.

The speaker is now integrated and can be addressed via headset in the Video Viewer by pressing the microphone button — when it turns green with a beep, the connection is established. If the speaker's internal microphone is enabled in its web GUI, two-way communication is also possible.

Figure — Microphone button in the Video Viewer for two-way audio.

Speakers can be selected via the "Audio sources" menu (all available speakers are enabled by default), and an audio file can be played through the selected speaker.

Figure — Audio sources menu, with all available speakers enabled by default.

MP3 files can be loaded into NXGEN via the "Audio" tab (e.g. voice prompts);

Figure — Loading MP3 files into NXGEN via the Audio tab.

use the "Speaker" button in the Video Viewer to select and play the desired file.

Figure — Speaker button in the Video Viewer, for selecting and playing a file.

8.3 Intercom

Intercoms (e.g. an A8207-VE) are added directly as "Axis" devices. Two ports must be opened on the router: 443 (Control, Server, HTTPS) and 554 (RTSP) — in this example, both were modified via port forwarding. The device is recognized with its exposed video streams and view areas, and its serial number is read automatically.

Figure — Adding the intercom (A8207-VE) as an Axis device, with ports 443 and 554.

Intercom audio functions are made available by creating an additional "GenesisAudio" entry

Figure — Creating an additional GenesisAudio entry for the intercom's audio.

; the intercom's I/O ports are automatically detected and available for further use.

Figure — Intercom's I/O ports, automatically detected.

Enter the SIP server credentials displayed in NXGEN into the Axis device.

Figure — Entering the SIP server credentials into the intercom.

Figure — SIP account settings on the intercom.

If the connection succeeds, the status appears in green with "OK."

Figure — Intercom SIP status showing green "OK."

To link the intercom's call button to NXGEN, retrieve the intercom's reference ID in NXGEN (located at the end of its URL).

Figure — Intercom reference ID at the end of its URL in NXGEN.

In the example:

Figure — Example reference ID value.

In the intercom's web GUI, create a recipient in the required format, appending the reference ID to the end of the URL and also entering it in the username and password fields.

Figure — Creating a recipient in the intercom's web GUI, with the reference ID in the username and password fields.

Press the test button to verify the connection to NXGEN.

Figure — Test button to verify the connection to NXGEN.

Create a rule in the intercom using the call button as the trigger and "Send a video sequence" as the action, selecting the recipient created earlier (e.g. "NXGEN"), a folder name, and the desired camera stream.

Figure — Intercom rule using the call button as the trigger.

Figure — "Send a video sequence" action, with the recipient, folder, and camera stream selected.

In the NXGEN client, the call is now listed as an alert under "Video Search," where the cloud AI also evaluates the video sequence (for example, classifying a visible person as a real alarm).

Figure — Intercom call listed as an alert in Video Search.

Switching intercom contacts to open a door or gate is done via IO programming

Figure — IO tab for the intercom's contacts.

— for the "Door" relay, enter the required HTTPS request in the "IO URL" field; the contact can then be activated from the Video Viewer using the virtual button:

https://IP-Address:Port/axis-cgi/io/port.cgi?action=6%3A%2F

Figure — Door relay IO URL field, activated via the virtual button in the Video Viewer.