Teradek Prism 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 is a professional encoder and decoder line for live contribution, distribution and remote production. In a Callaba workflow, Prism is usually the hardware SRT edge: it encodes a camera or program feed and sends it to Callaba, or it decodes a return feed coming from Callaba.

The clean ingest path is simple: create an SRT listener in Callaba Gateway, then configure Prism as an SRT caller. After Callaba receives the feed, you can monitor it in the browser, record it, route it, create playback links, or use it in a multiview board.

This guide is written for the search intent behind Teradek Prism SRT, Prism SRT setup, Prism Callaba Gateway, Prism multiview, Prism recorder, Prism playback and Prism decoder return feed.

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

For contribution, create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then set Teradek Prism to SRT Caller. Enter the Callaba public IP or DNS name, destination port, latency, stream ID if used, and matching passphrase if encryption is enabled. For return feed, configure Prism decoder as Caller to pull from Callaba, or Listener if Callaba pushes to Prism.

Prism can send SRT to Callaba for cloud ingest or decode a return feed from Callaba for local output.

What this setup does

This workflow connects a Teradek Prism encoder or decoder with Callaba Gateway over SRT.

Contribution: Prism encodes a live source and sends SRT to Callaba.
Cloud operations: Callaba receives the SRT feed, then provides browser preview, multiview, recording, playback and routing.
Return feed: Prism can decode a feed from Callaba and output it locally over SDI or HDMI, depending on model and license.

Which Prism devices this guide fits

This article focuses on the practical SRT behavior of the Prism line: encoder output to Callaba and decoder return feed from Callaba. Exact hardware ports, channel density, firmware and licenses can differ by Prism model.

Prism family	SRT support	Good Callaba angle	Note
Prism Flex Mk I / Mk II	SRT is part of the Prism protocol set. Flex Mk II supports single encode and can support bi-directional encode/decode with an additional license.	Portable SRT contribution to Callaba, return monitoring, event workflows.	Best fit for this article.
Prism Mobile / Prism Jetpack	Designed around mobile contribution workflows. Confirm active firmware, bonding/Core setup and available SRT or return-feed options.	Field contribution to Callaba, backup paths, return monitoring.	Check license and Core/CoreNEXT workflow.
Prism Rack / 1RU / 2RU	Prism family supports SRT, but channel count, line cards and model generation matter.	High-density rack encode/decode and 24/7 workflows.	Better as a separate rack-focused article.

Practical note: if your Prism unit has separate encoder and decoder licenses, confirm the active license before planning ingest or return feed. The network setup may be correct while the feature is not active.

SRT support note: SRT is supported across the modern Prism line, but exact behavior depends on model, firmware, active license and whether you are using encode, decode or return-video mode. Always confirm the exact device page or Teradek guide for your model before an event.

Recommended workflow

For the first test, use a simple path that is easy to debug:

Connect the SDI or HDMI source to Prism.
Confirm Prism sees video and audio.
Create a Callaba SRT listener.
Configure Prism as SRT Caller to the Callaba public IP or DNS name.
Start Prism output and check Callaba preview, bitrate, codec, audio and recording.

The first test should prove source → Prism → SRT → Callaba. Add advanced settings after that.

Recommended SRT mode

For contribution into Callaba, use Teradek Prism as SRT Caller and Callaba Gateway as SRT Listener. This keeps the public listening port on the cloud side. The venue or production network only needs to allow Prism to send outbound UDP traffic to Callaba.

srt://YOUR_CALLABA_IP:11300?mode=caller&latency=200&streamid=prism-main

If Prism exposes these values as fields instead of one URL, enter the same information separately: host, port, connection type, latency, stream ID and encryption settings.

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

Before you start

Prepare the Prism and Callaba sides before you change the production profile.

Firmware and license Confirm your Prism firmware, encoder license and decoder license match the workflow you want to run.

Core / CoreNEXT version Prism interface labels can differ between firmware and Core/CoreNEXT versions. If SRT fields look different, check the Stream, Output, Ingest or SRT sections for the same values: mode, address, port, latency, stream ID and encryption.

Source signal Confirm the SDI or HDMI input is stable before debugging SRT.

Callaba address Use the public IP address or DNS name of the Callaba instance that will receive the stream.

UDP firewall Open the selected UDP port on the Callaba side and allow SRT traffic from the Prism network.

First-test profile Start with H.264, 1080p and moderate bitrate. Move to HEVC, 4K or HDR after the first clean connection.

Encryption Add encryption only after the first clean test, unless your production policy requires it from the start.

Step 1: create the Callaba SRT listener

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.
Choose a UDP port, for example 11300.
Set latency, for example 200 ms as a starting value.
Add stream ID and passphrase if your workflow requires them.
Open the selected UDP port in the cloud firewall or security group.

Step 2: configure Prism as SRT encoder

In the Prism web interface or app, configure the encoder output that should send the live feed to Callaba. Exact labels can differ by firmware, but look for encoder configuration, streaming destination, protocol, connection type and SRT settings.

Select the correct input source.
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 as the host.
Enter the Callaba UDP port.
Set latency or buffer value.
Set stream ID and encryption/passphrase if needed.
Start streaming and confirm Callaba receives the feed.

Testing rule: do not start with the most complex profile. First prove Prism to Callaba with one output, H.264, moderate bitrate and no unnecessary routing. Then add HEVC, 4K, HDR, encryption, recording or failover.

Prism decoder and return feed from Callaba

Prism can also be used on the decode side. This matters when you want a return feed, confidence monitor, local SDI/HDMI output, or engineering view at a remote site.

Decoder license check: for a return-feed workflow, confirm that your Prism unit has active decoding or Return Video capability. Without the right license or mode, the SRT session can connect while the SDI/HDMI output still stays empty.

Decoder pulls from Callaba: Prism decoder is Caller, Callaba is Listener. This is usually easier when the decoder is behind NAT.
Callaba pushes to decoder: Callaba is Caller, Prism decoder is Listener. Use this when the decoder has a reachable public address or correct port forwarding.

Decoder pulls from Callaba:
srt://YOUR_CALLABA_IP:11310?mode=caller&latency=200&streamid=prism-return

Callaba pushes to Prism decoder:
srt://PRISM_DECODER_PUBLIC_IP:11320?mode=caller&latency=200&streamid=prism-return

In the first example, the Prism decoder is configured as Caller and connects to a Callaba listener. In the second example, Callaba is configured as Caller and connects to a Prism decoder listener.

Settings table

Use this table to avoid the common mismatch: SRT connects, but the media profile, stream ID, passphrase or decoder output mapping is wrong.

SRT transport settings and media settings must both be correct. A connected socket does not prove usable video.

Setting	Prism	Callaba Gateway	Why it matters
Role	Caller first	Listener first	Simplest cloud ingest pattern.
Address	Callaba IP / DNS	Public endpoint	Prism must reach Callaba.
Port	Destination UDP	Open listener port	Wrong port means no connection.
Latency	Buffer / SRT latency	Same policy	Too low can break noisy paths.
Stream ID	`prism-main`	Same value if expected	Helps route and identify the feed.
Encryption	Same passphrase if used	Same passphrase	Encryption fails if values do not match.
Codec / bitrate / audio	Encoder profile	Preview and monitor	Proves the stream is production-usable.
Decode output	SDI / HDMI output mapping	SRT source route	Return feed must be mapped to physical output.

Codec, bitrate and latency notes

Prism can be used in advanced production profiles, but the first connection should be conservative.

Codec: start with H.264 for the first test. Move to HEVC when the path is proven.
HEVC: confirm your Prism model, firmware and license support the HEVC workflow you want. H.264 is the safer compatibility path for the first Callaba test.
Resolution: start with 1080p if possible, then move to 4K or HDR workflows after validation.
Bitrate: use a value comfortably below the uplink capacity.
Latency: start around 120–500 ms for normal internet contribution and increase on unstable networks.
Audio: confirm embedded or analog audio is present before debugging Callaba.

Prism multiview workflow with Callaba

After Prism sends the SRT feed to Callaba, operators can place that feed into a browser-based multiview board. This is useful when Prism is one of several contribution sources and the team needs to see stream state, bitrate, audio and route behavior in one place.

After Callaba receives the Prism SRT feed, the stream can become part of a browser monitoring, recording, playback and routing workflow.

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

Prism recorder workflow: source-side proof vs cloud-side proof

If your Prism workflow includes local or source-side recording, treat that recording as proof that the source side existed. Callaba recording proves something different: the SRT feed reached the cloud workflow and was available there.

Layer	What it proves	Use case
Source-side recording	The camera or production signal existed locally.	Field backup and local archive.
Callaba recording	The Prism SRT feed reached Callaba.	Cloud-side proof, replay and downstream workflow archive.

If you compare source-side recordings with Callaba recordings, use a consistent time source such as NTP where possible. Time differences can make it harder to match incidents and operator notes.

Prism playback workflow with Callaba

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

HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/prism-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/prism-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. See the Callaba Web Players API documentation if you need to automate player creation.

Troubleshooting

Most Prism to Callaba issues are not mysterious. Check source, encoder profile, SRT role, port, security settings and Callaba preview in that order.

Start with the SDI/HDMI source and Prism encoder profile before debugging Callaba.

1. Stream does not appear in Callaba

Confirm Prism sees the source signal.
Confirm Prism output is enabled and actively streaming.
Confirm Prism is Caller and Callaba is Listener for the first test.
Check the Callaba public IP or DNS name and UDP port.
Open the UDP port in the cloud firewall or security group.

2. SRT connects, but picture or audio is missing

Confirm the source has picture and audio before encoding.
Start with H.264 before testing HEVC or advanced profiles.
Check resolution, frame rate, bitrate and audio mapping.
Use Callaba preview or multiview to confirm what reaches the cloud side.

3. Encryption fails

Enable encryption on both sides or disable it on both sides.
Use the exact same passphrase.
Check any AES strength or encryption option if the interface exposes it.
Test without encryption first if the production policy allows it.

4. Return feed connects but no local output

Confirm the Prism decoder receives the stream.
Confirm the decoder or Return Video license is active on this Prism unit.
If SRT connects but the Prism output is black, temporarily switch the return feed to H.264 1080p and test again before using HEVC, 4K or HDR.
Confirm the decoded feed is mapped to the correct SDI or HDMI output.
Check output resolution and frame rate compatibility with the monitor or downstream device.
Check audio output mapping if video works but audio does not.

Official references used for this guide

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

FAQ

Can Teradek Prism send SRT to Callaba Gateway?

Yes. Configure Prism as an SRT Caller and send it to a Callaba SRT Listener.

Should Prism be Caller or Listener?

For most cloud ingest workflows, use Prism as Caller and Callaba as Listener. For return-feed decoding, the Prism decoder can either pull from Callaba as Caller or listen while Callaba pushes to it.

Can Callaba record a Prism SRT stream?

Yes. Once Callaba receives the Prism SRT stream, it can record the received feed.

Can I monitor Prism output in Callaba multiview?

Yes. After Prism sends SRT to Callaba, the feed can be used in browser preview or multiview depending on the deployment and version.

Can Callaba send a return feed to a Prism decoder?

Yes. Configure an SRT output route in Callaba and configure the Prism decoder side with matching SRT role, address, port, latency, stream ID and encryption settings.

Why does my Prism return feed connect but show no SDI or HDMI output?

Check that the Prism decoder or Return Video license is active, that the codec and resolution are supported, and that the decoded feed is mapped to the correct SDI or HDMI output. For the first test, use H.264 1080p before testing HEVC, 4K or HDR.

Final practical rule

Prove transport before you optimize quality. First get one Prism SRT feed into Callaba with a conservative H.264 profile. Then add HEVC, 4K, HDR, encryption, recording, return feed, multiview and routing.

Last updated: May 20, 2026

Try Callaba Gateway with Teradek Prism

Create an SRT listener in Callaba, send a Prism SRT stream to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback or player delivery.

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