Can Callaba record Prism Rack SRT channels?

Yes. Once Callaba receives each Prism Rack SRT channel, it can record the received feed.

Teradek Prism Rack SRT setup with Callaba Gateway

May 20, 2026

Written by Iurii Pakholkov

Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.

Release: Callaba 8.4

Teradek Prism Rack is a high-density rack workflow for live broadcast contribution, encode/decode, server rooms, production trucks and mobile fly-packs. In a Callaba workflow, Prism Rack usually works as the dense hardware SRT edge, while Callaba becomes the cloud operations layer after SRT ingest.

The clean path is simple: create one or more SRT listeners in Callaba Gateway, then configure each Prism Rack encoder card or channel as an SRT caller. After Callaba receives the streams, operators can use browser multiview, recording, playback links, restreaming, API workflows or failover routing.

This guide is written for Teradek Prism Rack SRT, Prism Rack Callaba Gateway, Prism Rack multiview, Prism Rack recorder, Prism Rack playback and Prism Rack return feed.

Quick answer: how do I connect Teradek Prism Rack to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open one UDP port per important rack output, then configure the matching Prism Rack encoder card or channel as SRT Caller. Enter the Callaba public IP or DNS name, destination port, latency, stream ID if used, and matching passphrase if encryption is enabled. Label each Callaba input by rack slot and channel.

Prism Rack is the dense hardware layer. Callaba is the browser-based cloud workflow layer after SRT ingest.

What this setup does

This workflow connects one or more Prism Rack encode/decode channels with Callaba Gateway over SRT.

Contribution: Prism Rack encoder cards send SRT outputs to Callaba.
Cloud operations: Callaba receives each SRT channel, then provides browser preview, multiview, recording, playback and routing.
Return feed: Prism Rack decoder cards can decode an SRT feed from Callaba and output it locally, depending on card type and license.

Prism Rack specifics: 1RU, 2RU, cards and channels

A Prism Rack setup is not just a single encoder. You need to think in terms of chassis, card type, channel, port and route. That is the main difference from a portable Prism workflow.

Rack element	Why it matters for SRT	Callaba naming rule
1RU / 2RU chassis	The rack size and installed cards decide density and redundancy planning.	Include rack name in the Callaba input label.
Encoder card	Creates the outbound SRT contribution stream.	Use names like `prism-rack-a-card-1-main`.
Decoder card	Receives return feeds or distribution feeds from Callaba.	Label return feeds separately from ingest feeds.
Channel / output mapping	Wrong mapping can send the wrong channel to the right SRT listener.	Match port, stream ID and label to the physical card/channel.

Practical note: in rack workflows, clean naming is not cosmetic. It prevents an operator from routing card 2 when the real source is on card 3.

Recommended workflow

For the first test, do not configure every rack channel at once. Prove one card and one output, then scale.

Identify the Prism Rack chassis, slot, card and channel.
Confirm the source signal is present on the selected encoder card.
Create one Callaba SRT listener for the first channel.
Configure the matching Prism Rack output as SRT Caller.
Start the output and confirm Callaba preview, bitrate, codec, audio and recording.
Duplicate the pattern for more rack channels only after the first one is stable.

Start with one rack output. Then repeat the same clean pattern for the remaining channels.

Recommended SRT mode

For contribution into Callaba, use this pattern first:

Prism Rack encoder card: SRT Caller
Callaba Gateway: SRT Listener

Use one clear UDP port per important rack output. Do not reuse the same port for unrelated channels unless your routing design explicitly requires it.

srt://YOUR_CALLABA_IP:11400?mode=caller&latency=200&streamid=prism-rack-a-card-1-main

Second rack channel example:
srt://YOUR_CALLABA_IP:11401?mode=caller&latency=200&streamid=prism-rack-a-card-2-main

Use Rack Encoder Caller → Callaba Listener for ingest. For return feed, decide whether the rack decoder pulls from Callaba or listens for a Callaba push.

Before you start

Prepare the rack map before you change live output profiles.

Rack map Write down chassis, slot, card type, input and output before creating Callaba listeners.

Firmware and license Confirm the Prism firmware, card type, encode/decode license and HEVC/HDR requirements for each card.

SRT license Verify that the selected Prism Rack encoder card has active SRT output capability. Some deployments may require a feature unlock, active license or supported firmware for the exact card and workflow.

Source signal Confirm the physical input is stable before debugging SRT.

Network interface Confirm which network interface is used for SRT output: management, streaming, Wired 1 or Wired 2. Check source IP, IP routing and firewall rules for that interface.

Step 1: create Callaba SRT listeners

Open your Callaba Gateway environment.
Go to SRT Servers and create a new incoming SRT server.
Set the role to Listener if the UI exposes this option.
Create the first port, for example 11400.
Name it after the rack mapping, for example prism-rack-a-card-1-main.
Set latency, stream ID and passphrase if your workflow requires them.
Open the selected UDP port in the cloud firewall or security group.
Repeat for the next channel only after the first channel works.

Step 2: configure Prism Rack encoder output

In the Prism Rack web interface, configure the correct encoder card and output. This is where rack workflows usually fail: the SRT fields are correct, but the wrong card or channel is selected.

Select the correct chassis, slot, card and channel.
Confirm the input signal is visible on that encoder card.
Choose the encoding profile: codec, resolution, frame rate and bitrate.
Select SRT as the streaming protocol.
Set connection type to Caller.
Enter the Callaba public IP address or DNS name.
Enter the UDP port assigned to this rack channel.
Set latency, stream ID and encryption/passphrase if needed.
Start streaming and confirm Callaba receives the correct channel.

Testing rule: never start rack testing with all channels. First prove one card, one output, one UDP port, one Callaba listener. Then duplicate the known-good pattern.

Prism Rack decoder and return feed from Callaba

Prism Rack can also be used on the decode side. This matters when you want return feeds, confidence monitors, local SDI output or central distribution from Callaba into a rack decoder card.

Decoder card check: confirm the installed card supports the decode workflow you need and that the required license is active. SRT may connect while the physical output stays empty if the decoder card, license or output mapping is wrong.

Rack decoder pulls from Callaba:
srt://YOUR_CALLABA_IP:11410?mode=caller&latency=200&streamid=prism-rack-return

Callaba pushes to rack decoder:
srt://PRISM_RACK_PUBLIC_IP:11420?mode=caller&latency=200&streamid=prism-rack-return

Settings table

Use this table to avoid the common rack mismatch: correct SRT values, wrong slot or wrong output mapping.

Rack workflows add card and channel mapping on top of normal SRT settings.

Setting	Prism Rack	Callaba Gateway	Why it matters
Slot / card	Encoder or decoder card	Named SRT input	Keeps rack mapping clear.
Role	Caller first	Listener first	Simplest cloud ingest pattern.
Port	Destination UDP	Open listener port	Use one documented port per output.
Codec / bitrate / audio	Encoder profile	Preview and monitor	Proves the stream is production-usable.
Redundancy	Power and network plan	Backup route or backup input	Important for 24/7 rack workflows.

Multi-channel operations

The main value of Prism Rack is density. The main risk is operational confusion. Treat every rack output as a named production object.

Name by hardware path Include rack, slot, card and channel in Callaba names.

Separate UDP ports Use separate documented ports for separate live outputs unless you intentionally use stream ID routing.

Monitor actual bitrate Do not rely only on configured bitrate. Watch what Callaba receives.

Per-channel verification Use Callaba preview to confirm video, audio, codec, resolution and bitrate for every rack channel. Do not assume one working channel means all channels work.

Test failover separately Main/backup logic should be tested after basic ingest is stable.

Prism Rack multiview workflow with Callaba

After Prism Rack sends SRT channels to Callaba, operators can place those channels into a browser-based multiview board. This is useful when the rack is feeding multiple live sources and the team needs one browser view for state, audio, bitrate, connection behavior and route status.

After Callaba receives Prism Rack SRT channels, they can be monitored, recorded, played back and routed from the cloud workflow.

Interactive check: open the Callaba multiview demo to see how received sources can look after cloud ingest.

Prism Rack recorder workflow: rack-side proof vs cloud-side proof

Rack-side recording and Callaba recording prove different parts of the chain. A rack-side record proves that the source reached the hardware system. Callaba recording proves that the SRT channel reached the cloud workflow.

Prism Rack playback workflow with Callaba

After Callaba receives Prism Rack SRT channels, you can create browser playback or HLS/embed links for people who should not connect directly to the rack hardware.

HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/prism-rack-a-card-1-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/prism-rack-a-card-1-main

Where browser links come from: HLS or browser playback is not automatic for every SRT session. Callaba creates player or HLS links after you create a Web Player or HLS packaging path for that stream. For multi-channel rack work, create a separate Web Player or HLS path for each rack channel so operators do not confuse card 1 with card 2. See the Callaba Web Players API documentation if you need to automate player creation.

Troubleshooting

Most Prism Rack to Callaba issues are mapping issues first and SRT issues second. Check slot, card, source and channel mapping before changing the network settings.

Start with the rack card and channel map before debugging Callaba.

1. Stream does not appear in Callaba

Confirm the correct Prism Rack slot and encoder card are selected.
Confirm the input signal is present on that card.
Confirm the output is enabled and actively streaming.
Confirm Prism Rack is Caller and Callaba is Listener for the first test.
Check the Callaba public IP or DNS name and UDP port.
If Prism Rack has multiple network interfaces, confirm that SRT output uses the interface that has a route to Callaba. Check the source IP in the output settings if available, or verify routing at the network level.
Open the UDP port in the cloud firewall or security group.

Official references used for this guide

Use these if you need exact Prism Rack capabilities, encoder settings, decoder settings, return video behavior or SRT field names.

FAQ

Can Teradek Prism Rack send SRT to Callaba Gateway?

Yes. Configure the relevant Prism Rack encoder card or channel as SRT Caller and send it to a Callaba SRT Listener.

Should Prism Rack be Caller or Listener?

For most cloud ingest workflows, use Prism Rack encoder outputs as Caller and Callaba as Listener. For return feeds, a Prism Rack decoder card can either pull from Callaba as Caller or listen while Callaba pushes to it.

Can Callaba multiview show multiple Prism Rack channels?

Yes. After the rack channels are received by Callaba, they can be placed into a browser multiview board depending on deployment and version.

What is different between Prism Rack and Prism Flex setup?

The SRT role logic is similar, but Prism Rack adds chassis, slot, card, channel and output mapping. Always label each Callaba listener by rack slot and channel to avoid operational confusion. Prism Rack also brings rack-specific operations such as redundant power planning on 2RU systems and multiple Ethernet paths for management and streaming. Those details do not change the SRT URL itself, but they matter for 24/7 reliability.

Final practical rule

In rack workflows, the mapping is as important as the SRT URL. Prove one card, one channel, one UDP port and one Callaba listener first. Then scale the exact same pattern across the rack.

Last updated: May 20, 2026

Try Callaba Gateway with Teradek Prism Rack

Create SRT listeners in Callaba, send Prism Rack SRT channels to the gateway, and monitor the feeds before routing them to recording, restreaming, multiview, playback or player delivery.

See SRT server setup Open multiview demo Web Player docs Prism Rack docs