YoloLiv YoloBox SRT and RTMPS workflows with Callaba
More live video workflow notes and product updates.
Portable production decision hub
YoloBox models can combine switching, encoding, recording and mobile connectivity in one portable unit, but they do not expose one interchangeable transport path. Start with the exact model and firmware, then choose direct SRT, RTMPS, or a service-assisted handoff before configuring Callaba.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct YoloLiv YoloBox SRT and RTMPS workflows with Callaba
| Path | Operational role | When to choose it |
|---|---|---|
| YoloBox Extreme | Direct SRT or RTMPS contribution from a high-input portable switcher. | Choose this path when the current Extreme specification and firmware expose the output protocol required by the event. |
| YoloBox Pro | Verified RTMP or RTMPS ingest followed by SRT routing in Callaba. | Do not infer direct SRT output from SRT input support or from another YoloBox model. |
| YoloBox Ultra | Portable SRT workflow with model-specific caller, listener and bonding caveats. | Confirm firmware, connection role and whether Network Bonding is part of the selected path. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
YoloBox owns camera inputs, switching, local graphics, source encoding and the first network uplink.
Transport handoff
The handoff is one documented SRT or RTMPS output. Record its URL, mode, codec, bitrate and security values in the runbook without exposing credentials.
Callaba responsibility
Callaba owns the cloud or private ingest endpoint, transport telemetry, browser Multiview, recording, downstream routes, playback and API automation.
Preflight a portable YoloBox production path
- 1. Identify the exact YoloBox model, installed firmware and enabled transport features. A menu shown in a video for another model is not evidence.
- 2. Choose one primary contribution method. Prefer direct SRT when the exact model documents it; keep RTMPS as a deliberate alternative, not a hidden automatic assumption.
- 3. Create the matching Callaba listener or receiving endpoint and copy the generated connection values exactly. Keep Stream ID and passphrase outside screenshots and analytics notes.
- 4. Test the same Ethernet, Wi-Fi, cellular or bonded path that will be used at the venue. Measure stability while switching sources and recording locally.
- 5. Verify video, audio, telemetry, recording and at least one downstream route in Callaba. A connected socket alone does not prove a production-ready workflow.
After preflight, use the SRT Gateway hub for architecture choices, the SRT Server guide for receiver concepts, Multiview for browser operations, and the SRT API documentation for automation. These shared resources do not replace the model-specific guide linked in the decision table.
Official references reviewed
Capabilities and menu fields can change with hardware revisions, firmware and account entitlements. Recheck the exact model before a production event.
- YoloBox Extreme technical specifications — Current protocol, input, output and encoding capabilities for Extreme.
- YoloBox Ultra technical specifications — Model-specific streaming and production capabilities for Ultra.
- YoloLiv Network Bonding — Service boundary and availability for optional bonded connectivity.
Frequently asked questions
Which YoloBox models can send SRT directly to Callaba?
YoloLiv documents SRT output for YoloBox Extreme, while Ultra has its own SRT workflow and role controls. For Pro, use the verified RTMP or RTMPS path unless the installed firmware and an official model-specific source explicitly document direct SRT output.
Does YoloBox Pro support SRT output or only SRT input?
Do not treat an SRT input feature as proof of an SRT program output. The safe production plan is RTMP or RTMPS from Pro into Callaba, followed by SRT routing from Callaba, until current Pro documentation proves the required output mode.
Is YoloLiv Network Bonding required?
No. Bonding is an optional connectivity layer, not a requirement for every Callaba ingest. Use it only when the field network design needs multiple uplinks and the selected YoloLiv plan, model and region support the service.
Should YoloBox use caller or listener mode?
Use the relationship supported by the exact model and make the opposite side in Callaba match it. A common field pattern is source-side caller to a reachable Callaba listener, but Ultra can expose different roles, so verify before the event.
When should RTMPS be used instead of SRT?
Use RTMPS when the model has a verified RTMPS output, the network permits HTTPS-style egress more easily, or direct SRT is not available. Choose SRT when recovery, transport telemetry and explicit latency control are operational requirements.
Move from device choice to a tested receiving path
Open the exact-model guide, validate one contribution feed in Callaba, then add recording, monitoring and downstream routes only after the ingest contract is stable.
