Teradek SRT Gateway Workflows with Callaba
More live video workflow notes and product updates.
Teradek Prism contribution
Choose the Prism form factor at the source, then prove the same SRT handoff in Callaba
Prism is a product family, not a single encoder screen. A modular chassis in a facility, a rack deployment, a compact Flex and a mobile unit used with a verified bonding service solve different source-side problems. The common operational result is a feed that arrives at a known Callaba endpoint with enough evidence for a remote operator to trust it.
The handoff is successful only when Callaba shows the intended publisher, sustained bitrate, usable picture and audio—not merely when the Prism interface reports that it is streaming.
Which Prism belongs in this design?
| Path | Use it when | What must be proved | Model guide |
|---|---|---|---|
| Prism | A modular encode or decode platform fits the facility. | Installed cards, AVC/HEVC choice, simultaneous jobs and the selected SRT direction. | Prism setup |
| Prism Rack | Centralised I/O and channel density matter. | The complete channel mix at production rates, not one sample feed. | Rack setup |
| Prism Flex | A compact encoder or decoder is preferable to a rack chassis. | The exact hardware generation, input, codec and network output. | Flex setup |
| Prism Mobile | Field contribution needs a mobile, bonded source. | Modem/service state, the server handoff and behavior when one access network is removed. | Mobile setup |
Two source shapes can use one receiving standard
For an internet contribution, Prism as Caller and Callaba as Listener is often the simplest first topology because the source initiates outbound UDP toward a public endpoint. It is not a universal rule. If the deployed Prism role, firewall or facility policy requires another mode, document which peer initiates and keep both configurations consistent.
Do not confuse bonded access with end-to-end failover
What mobile bonding can protect
A mobile service can combine or manage access links on the transmitter side. Its subscription, supported modems, regional coverage and server handoff are part of the Teradek design and must be verified with the exact unit.
What Callaba recovery can protect
A separately configured Callaba route can change the downstream source or destination after a failure. That is an application workflow with its own trigger and test; it is not automatically created because the field encoder uses more than one uplink.
If return video is required, give it a separate source, destination, port, codec and acceptance record. A healthy forward contribution does not prove the reverse path.
Sign off the contribution in this order
- Record the exact Prism model, module layout, software version, licensed services and physical input.
- Lock the source format and audio map, then choose the encode profile supported by the complete downstream chain.
- Create a named Callaba SRT server, agree the mode, host, UDP port, latency, Stream ID and passphrase policy, and expose only the required network boundary.
- Run representative motion and audio while watching bitrate, RTT, packet recovery and decoded output in Callaba.
- Make and play back a short recording, then interrupt the real field or facility network and measure reconnection.
- Add Multiview, delivery routes or recovery paths only after the original contribution has a recorded pass result.
Use the documentation for the installed Prism
Review Teradek’s current Prism family overview, encoder configuration guide and official SRT setup note. Menu names and supported combinations can vary by chassis, module, software and service plan.
