Turn a room into a webinar workflow
Expose a room as an interactive session for speakers while keeping a cleaner viewer-facing layer for the wider audience.
Run browser guest or webinar rooms, then connect the call to recording or the media output your live workflow needs.
Bring browser rooms, participants, recording and media output into the live workflow.
Expose a room as an interactive session for speakers while keeping a cleaner viewer-facing layer for the wider audience.
Decide who joins, who only watches, and how the room is exposed instead of letting those rules live only in ad hoc meeting links.
Keep discussion beside the live call with in-room chat, then let an approved participant share a screen when the room needs a presentation, review, or live demonstration.
Use the same room model for support, monitoring, webinars, internal reviews, or public-facing interactive sessions.
Open a controlled guest or webinar join path in the browser, without asking speakers or invited participants to install a platform-specific app.
When the session should reach beyond the participants themselves, connect the room to viewer playback or other distribution layers.
Preserve sessions for replay or audit without rebuilding the live room around a separate recording workflow.
Bring remote speakers into a live interview, panel or presentation. Choose the participant video and audio tracks available from the Callaba room, place them alongside cameras or presentation media in Video Mixer, and adjust the sound. Prepare the guest layout in Preview before taking it to Program. Publish or record the finished programme; the operator chooses the tracks rather than automatically putting everyone on air.
Bring one guest into the next scene when you need control of that person’s picture and sound. In AV Mixer, select the guest’s available participant track instead of treating the room as one feed.
This path is available when your Callaba 8.8 deployment lists the room and its participant tracks in AV Mixer.
Invite the guest to a Callaba video-call room and make sure they are publishing the picture or sound you expect to use.
In AV Mixer, open Inputs, then Other, then Video call. Choose the Room and the guest’s participant stream, check its Video and Audio indicators, then choose Add.
Place the selected guest source in a Preview scene with the production elements that belong around it. Preview remains separate from the live Program state.
Once Program is started and Preview contains a video layer, select CUT or FADE, set Duration when needed, and use TAKE to move the prepared scene to Program.
Supported behavior sits beside a practical acceptance check. The installed Callaba interface and the real source, destination, and infrastructure profile remain authoritative.
| Capability | Supported behavior | Acceptance check |
|---|---|---|
| Let guests join from the browser | Open a controlled guest or webinar join path in the browser, without asking speakers or invited participants to install a platform-specific app. | The intended model is browser-first participation so the join flow stays lightweight for operators, speakers, and guests. |
| Separate participants from viewers when needed | Use the same event surface for active speakers and passive viewers without forcing every attendee into the same participation mode. | Lower resolution, frame rate or bitrate generally uses less data. Longer calls and layouts receiving several participant videos use more, so test the selected quality and the real network plan for the expected call setup. |
| Turn a room into a webinar workflow | Expose a room as an interactive session for speakers while keeping a cleaner viewer-facing layer for the wider audience. | Yes. That is often the right approach for webinars, monitoring, or any scenario where not everyone should be an active room participant. |
| Collaborate with in-room chat and screen sharing | Keep discussion beside the live call with in-room chat, then let an approved participant share a screen when the room needs a presentation, review, or live demonstration. | Plan from the bitrate rather than a fixed per-call number: 1–5 Mbps transfers about 0.45–2.25 GB in an hour in one direction. Actual use depends on resolution, frame rate, codec, bitrate, call length, and how many participant videos a device sends or receives. |
| Send the room into playback or external distribution | When the session should reach beyond the participants themselves, connect the room to viewer playback or other distribution layers. | Yes. That is often the right approach for webinars, monitoring, or any scenario where not everyone should be an active room participant. |
| Record sessions without changing the room logic | Preserve sessions for replay or audit without rebuilding the live room around a separate recording workflow. | Use the recording workflow when the session needs an archive or replay. Make a short recording with the intended room layout and participant audio, then check the finished file before the live session. |
You have seen what the product does. These three guides take you into the exact controls, show what to connect next, and give you a practical check before the workflow goes live.
Ingest, route, secure, and deliver live and VOD — via UI or API. Cloud on AWS or on-prem.
The pay-as-you-go cloud tariff is ideal for those who need all the advantages of the cloud, such as instant deployment of Callaba, low latency due to the global network of data centers, server reliability, data backup, scalability, managed services, and much more.
Deploy Callaba on AWSThe unlimited tariff is a good fit for actively growing organizations of medium and large size that would like to have no limitations like those in the bundled tariff, while also maintaining full control over their data.
Install Callaba self-hostedRealtime rooms become much easier to control when room creation, viewer playback, and recording are treated as separate modules. Use the API when calls or webinars need to behave like part of your own app, event stack, or operator workflow.
Plan from the bitrate rather than a fixed per-call number: 1–5 Mbps transfers about 0.45–2.25 GB in an hour in one direction. Actual use depends on resolution, frame rate, codec, bitrate, call length, and how many participant videos a device sends or receives.
Lower resolution, frame rate or bitrate generally uses less data. Longer calls and layouts receiving several participant videos use more, so test the selected quality and the real network plan for the expected call setup.
Use the recording workflow when the session needs an archive or replay. Make a short recording with the intended room layout and participant audio, then check the finished file before the live session.
Yes. That is often the right approach for webinars, monitoring, or any scenario where not everyone should be an active room participant.
The intended model is browser-first participation so the join flow stays lightweight for operators, speakers, and guests.
Start with Video calls, then use Web players for viewer-facing surfaces and Recordings when sessions need archives or replay.
Video conferencing bandwidth is the measured audio-and-video bitrate sent by each participant plus the streams that participant receives. It changes with codec, resolution, frame rate, screen sharing, layout, and packet overhead, so plan from the actual send and receive bitrates with headroom instead of using one universal Mbps figure.