media server logo
Operator documentation

Multiview and video calls

Use this runbook to build an operator view or browser room that exposes the right sources without exposing private controls. It keeps the UI task, verification and automation path together.

UIQuick start → Multiview boards

What this solves

This procedure gives an operator one controlled path to build an operator view or browser room that exposes the right sources without exposing private controls.

When to use it

Use it during initial setup, a planned change or incident recovery when you need to build an operator view or browser room that exposes the right sources without exposing private controls.

Dashboard path

Quick start → Multiview boardsRoute/multiview-dashboard/list
Quick start → Video callsRoute/conferences-dashboard/list

Prerequisites

  • Administrator access to the Callaba instance and permission to change this module.

  • A maintenance window or a non-production resource plus a real test source or client.

  • A record of the current values, allocated ports and credentials before you save changes.

Steps in the Callaba UI

  1. 01

    In the dashboard sidebar, follow Quick start → Multiview boards. Open the source-backed route /multiview-dashboard/list. In the dashboard sidebar, follow Quick start → Video calls. Open the source-backed route /conferences-dashboard/list.

  2. 02

    Before changing Multiview and video calls, record these current values: inputs, layout_id, visibility, source_kind, source_id, participant_name.

  3. 03

    In Multiview and video calls, set inputs, layout_id, visibility, source_kind, source_id, participant_name so you can build an operator view or browser room that exposes the right sources without exposing private controls. Keep unrelated values unchanged.

  4. 04

    Run Save [creating-form-save]. Wait for the form or listing to settle before testing another variable.

  5. 05

    Use a real source, destination or browser client and confirm these live signals: status, tile_index, isConnected, participant_id, room_id.

Controls to review
  • inputs
  • layout_id
  • visibility
  • source_kind
  • source_id
  • participant_name
Actions to run
  • Savecreating-form-save
Signals to verify
  • status
  • tile_index
  • isConnected
  • participant_id
  • room_id

Expected result

The runbook is complete when Save [creating-form-save] succeeds and a real workflow reports status, tile_index, isConnected, participant_id, room_id.

Troubleshooting

The saved change does not appear

Confirm the save response, refresh the module once and compare the visible values with the record made before the change. Correct validation errors before retrying.

The connection or playback path fails

Check the exact host, port, protocol, credentials and firewall path used by the real client. Test one source and one destination before restoring the full workflow.

The module starts but health is unstable

Return to the last known working values, inspect live statistics and process errors, then reintroduce one change at a time.