media server logo
VIDEO SURVEILLANCE WORKFLOW

Watch every live site and keep the evidence that matters

Callaba brings camera and encoder feeds into one operator workflow: receive the signal, watch multiple locations in Multiview, preserve recordings, and keep a recovery path ready when an upstream feed becomes unavailable.

FROM CAMERA TO OPERATOR

A visible path from live feeds to monitored evidence

Keep contribution health, the operator view, and recording ownership in the same workflow instead of hiding failures behind an isolated player.

  1. 01

    Receive

    Accept SRT, RTMP, RTSP, or NDI sources from sites and encoders.

  2. 02

    Observe

    Place approved feeds in a browser Multiview for one operator or a shared team.

  3. 03

    Protect

    Use primary and backup paths and switch sources when the operating plan requires it.

  4. 04

    Retain

    Record selected feeds and attach storage for review or controlled playback.

OPERATIONAL OUTCOMES

Built for monitoring teams that need signal context

The workflow stays useful before, during, and after an incident because operators can see the live source and retain the relevant media.

01

Multi-site operator view

Combine approved feeds in one browser wall without giving every viewer access to the management UI.

02

Resilient contribution

Keep primary and backup inputs explicit so operators know which source is active.

03

Recording and archive

Record continuously or selectively and keep media on storage controlled by your team.

WHERE THE WORKFLOW FITS

Use the same operating model across real production scenarios

Remote facilities

Watch stores, campuses, venues, construction sites, or industrial locations from a central operations room.

Event and venue security

Bring temporary camera feeds into a monitored wall and retain the feeds required for review.

Infrastructure observation

Combine live contribution, signal health, and recording for distributed technical sites.

Security-integrator controlled deployment

Deploy the streaming, monitoring, and recording layer on infrastructure selected by the integrator while keeping camera and physical-access systems separate.

PRODUCT LAYER

Choose the Callaba products behind the workflow

Start with the modules the operators need. Add the remaining capabilities as the production path, audience, and retention plan become clear.

IMPLEMENTATION GUIDE

Compare cloud and local recording for remote surveillance video

Plan source ownership, Multiview monitoring, recording location, retention, and recovery without treating Callaba as a VMS or physical-access platform.

Read the surveillance workflow guide
OPTIONAL AUTOMATION LAYER

Automate the monitored wall after the product workflow is proven

Create and start the Multiview through the REST API, then connect recording and storage modules when the operating policy is stable.

Read the API workflow
WORKFLOW QUESTIONS

Video surveillance streaming FAQ

Can Callaba show surveillance feeds in one browser Multiview?

Yes. Approved live sources can be arranged in a Multiview so an operator can watch several locations from one browser surface.

Can the same workflow record selected camera feeds?

Yes. Recording and storage are separate modules, so teams can retain the feeds required by their operating and retention policies.

Does Callaba replace a physical camera, VMS, or access-control system?

No. Callaba manages live video contribution, monitoring, routing, recording, and playback around compatible sources. It does not claim camera fleet management, ONVIF or PTZ control, incident alerting, surveillance archive search, or physical-access functions.

Can surveillance video run on private infrastructure?

Yes. Callaba can run in the cloud or on a self-hosted Linux server, depending on network, storage, and governance requirements.

Can operators switch to a backup source?

Yes. Callaba provides explicit source and routing controls for manual and configured recovery workflows; the exact transition behavior should be tested with the real encoders and network.