111 questions, answered from the documentation and linked back to it.
Yes. Load the cameras you want in the viewer, click Save View, give it a name, then select or create a Tag to organise it and save. To bring it back later, go to Tags and pick your tag. Saving a layout at the start of a shift means reloading it in seconds rather than rebuilding it, and tags are worth organising by site, shift or camera type so the right view is quick to find.
Cloud Streaming routes video through the GCXONE cloud infrastructure, so it is reachable from anywhere with an internet connection and is encrypted and optimised for remote access. Local Mode is a direct peer-to-peer connection between the operator workstation and the device, giving minimal latency, reduced WAN bandwidth and improved audio quality through local SDKs. Local Mode requires the Local Mode service to be installed on the operator workstation, and it falls back to cloud streaming automatically when it is unavailable.
Yes - Video Viewer, Video Search and Maps each have their own Multi Monitor toggle, so you send each one to a dedicated screen independently. In Video Viewer the toggle is in the bottom-left toolbar; the viewer then splits and the secondary monitor section is highlighted in yellow, and whatever you load into that section is what appears on the second monitor. Enable the toggle inside Video Search or Maps to extend those the same way. With it set up, opening an alarm in Video Search switches the Video Viewer on its dedicated monitor to the alarm's camera, and the Maps panel pans to the alarm site if Maps multi-monitor is also active.
Pixelated, choppy or low-resolution video is normally a bitrate or bandwidth constraint. Open the device web interface and increase the bitrate, with roughly 2 to 4 Mbps recommended for 1080p, then check the bandwidth actually available and lower the GCXONE stream quality to Medium or Low if it is tight. Enabling GreenStream (Auto quality) lets GCXONE pick the resolution for you, and using secondary streams for grid views while limiting concurrent streams removes a common cause. For on-site workstations, test network latency and use Local Mode, which improves quality on the local network.
Frequent pauses, a recurring loading spinner or "Connection lost" messages usually indicate packet loss, an overloaded device or a timeout that is too short. Reduce stream quality, limit the number of concurrent streams and close unused video windows first, then test for packet loss with an extended ping to the device IP and check cables, switches, routing and WiFi interference. For streams that die after a period of time, increase the timeout in GCXONE streaming settings to 30 to 60 seconds and adjust firewall timeouts to allow persistent connections. Reducing concurrent connections to the device, and restarting it if overloaded, resolves the rest.
In Local Mode the SDK path talks to the device directly, so RTSP is not required, but if an RTSP port has been entered then streaming happens only over that configured port. With the Cloud Only toggle the SDK streams via cloud regardless of Local Mode. For users without Local Mode, streaming works only on the basis of the RTSP port configured. Audio needs a localhost URL at device level in Local Mode, or the streaming03 URL for the Cloud Only toggle.
PTZ controls only appear when the camera, the device configuration and your account all allow it. Confirm the camera hardware actually supports PTZ and that PTZ is enabled on the device, then check that your user has PTZ permissions and that PTZ controls are enabled in the Live View settings. On the platform side, the PTZ toggle must be switched on in the Sensor Edit page for the controls to become available.
PTZ control is supported on Axis, Dahua, Hikvision and Milestone devices, and the controls appear only when the PTZ toggle is enabled in the Sensor Edit page and the user holds the required permissions. Before you start, the PTZ camera must be added to GCXONE, online and streaming correctly, and PTZ has to be enabled on the device itself with an appropriate protocol such as ONVIF or a manufacturer-specific one. Cameras also operate within defined pan and tilt ranges that depend on the model.
Playback is reachable from two places. In the Video Viewer, click the Playback button in the Stream Controls bar to open a date and time picker, use the calendar, the Quick Date Selection slider or the exact time control, and confirm with Set — the stream switches to playback mode and shows a timeline bar covering the full 24-hour recording history that you can scrub through. Playback is also available from the Video Activity Search when reviewing an alarm event, where a four-panel view shows Pre Alarm, Alarm, Post Alarm and Live footage together. Playback timestamps are shown in the site's local timezone so they line up with the alarm header and other feeds.
Isolate temporarily suppresses alarms from one specific sensor for a chosen period, which is useful when maintenance, construction or cleaning work would otherwise flood operators with non-relevant alarms. It is controlled from the bottom toolbar of the Video Viewer: pick the isolate time first, then switch the Isolate Sensor toggle on. When the period ends the sensor resumes normal alarm generation automatically, and an operator can also toggle it off at any point. The state and timer survive closing the camera view — reopen the stream and the remaining time is shown straight away.
GCXONE offers three mask options in one panel: Timed Mask, History and Camera Mask. Timed Mask is a time-limited block drawn over camera zones, shown as a blue grid, with a timer of 30 minutes, 1 hour or 2 hours, and it is available to both Admins and Operators. Camera Mask is a permanent grid-based block shown as a red grid and is accessible to Admins only. History uses recorded activity over 1, 5, 10 or 30 days as a reference to highlight zones before you decide what to mask.
Event Clips automatically capture a short video segment whenever an alarm or motion event fires, so operators see the pre-event, event moment and post-event context without searching recorded footage. Devices keep a short rolling recording buffer, and the system extracts the segment from it and attaches the clip to the alarm; where AI is enabled the clip can be enriched with detection results before the operator opens it. Supported devices include ADPRO, Axis, Dahua and Milestone, and some battery-powered devices such as Ajax or Reconeyez may return images instead of video because of hardware limitations. Typical clip duration is around 10 seconds, 5 seconds before and 5 after, and it can be adjusted to site requirements.
Yes — Multi Monitoring links Video Search, Video Viewer and Maps opened in separate browser tabs, so selecting a camera or alarm in one module reflects in the others instantly. Open Video Viewer in one tab, Video Search in another and Maps optionally in a third, then turn the Multi Monitor toggle on in each: bottom left in the Video Viewer, top right in Video Search. After that, choosing an alarm or camera in Video Search opens the corresponding stream in the Video Viewer and highlights the same device in Maps where it is mapped.
No. The AJAX integration supports discovery and alarm reception only, with no live streaming, playback or PTZ features. Alarms are transmitted using SIA, the Security Industry Association Protocol, and all alarms from the Hub or NVR objects are received collectively under that device in GCXONE. Add an AJAX Hub for AJAX manufactured cameras and an AJAX NVR for third-party cameras.
No. Reconeyez is a wireless, battery-powered intrusion detection system that is image-based and event-driven, so live streaming and playback are not supported and Local Mode does not apply. On an alarm it captures snapshots and short video clips of typically 10 to 15 seconds, which you review in the cloud portal or mobile app, and the battery-powered design is what limits live video. Ajax PIR-CAMs work the same way, with event-based image capture only.
An alarm arrives in the Talos queue with its customer and site name, device and sensor reference, timestamp, classification and a preview or video clip. Opening it shows four panes — Pre Alarm, Alarm, Post Alarm and Preview — and a toolbar of six review tools: Jump Back to rewind to a point before the trigger, choosing anything from 15 seconds up to 1 day or a custom duration; Live to switch to the camera in real time; Playback to review recorded footage; Play Clip, where Alarm Clip Download is enabled for that device; Mask to apply a temporary or permanent mask to a zone; and Trigger Alarm to raise one manually. Use Jump Back before confirming or dismissing anything, because what happened before the trigger usually reveals the real cause.
Alarm Clip Download automatically retrieves a short video clip for each alarm event and stores it securely inside the system, typically covering 5 to 10 seconds before the trigger and 5 to 10 seconds after it. Because the footage lives in the platform rather than on the device, operators can review the event even when the device is offline or the network is unstable — there is no dependency on live or archived playback from the camera. The clip is shown in the Preview quadrant of the Quad View, and it works the same way in both VAS and Salvo environments.
Event Overflow is a platform-wide safeguard that stops a malfunctioning or misconfigured device from flooding GCXONE. If a single device sends more than 25 alarms within any 5-minute window, the overflow threshold is breached, an internal event.overflow alarm is raised, and all further alarms from that sensor are discarded for the rest of the window. The system re-checks at the start of each new 5-minute window and continues suppression if the rate is still too high. It is a protective feature working as designed, not a bug.
Yes. Even when individual device counts pass through GCXONE, the CMS layer (Evalink Talos) applies its own overflow logic at the site level, aggregating alarms across all sensors on that site. For example, two devices each sending 15 alarms are below the per-device threshold of 25, so GCXONE lets them through, but Talos sees 30 alarms for the site and blocks them. In Talos this appears as the error code Alarm Limit Exceeded.
Log in to GCXONE, open the Configuration App and select the hierarchy level where you want it enabled — Service Provider, Customer, Site or Device. Switch to the Analytics tab, find Alarm Clip Download in the analytics list, click the Settings icon, select Subscribe and click Confirm. New alarm events will then carry a video clip button in the Quad View for both VAS and Salvo. The Play Clip button only appears where the feature is subscribed for the device and the device itself supports alarm clip download, so verify device support before relying on it for incident documentation.
Ask the assistant for an answer drawn from the whole documentation, or open a ticket and talk to a person.
New features, fixes and integration updates for GCXONE, delivered to your inbox as they are released.
