Dejero WayPoint to Callaba: verify the MPEG-TS handoff
More live video workflow notes and product updates.
Protocol correction and handoff guide
The existing URL contains “srt-gateway,” but current official WayPoint documentation does not establish WayPoint as a native SRT endpoint. It describes a receiver that reconstructs feeds from Dejero transmitters, decodes AVC or HEVC and outputs SDI or MPEG-TS. The safe action is to correct the content now and review a future URL migration separately.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct verify the MPEG-TS handoff
| Path | Operational role | When to choose it |
|---|---|---|
| WayPoint MPEG-TS output | WayPoint reconstructs and decodes the Dejero feed, then sends MPEG-TS over its network output. | Choose when the next receiver supports the documented UDP or RTP MPEG-TS handoff. |
| WayPoint SDI output | WayPoint emits baseband SDI to a separate encoder or production system. | Choose when facility routing or a dedicated bridge owns the next transport conversion. |
| Explicit external SRT bridge | A named third-party encoder receives SDI or MPEG-TS and creates the SRT contribution feed. | Choose only after that bridge has its own official SRT documentation and acceptance test. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
Dejero transmitters and services own field transport. WayPoint owns reception of compatible Dejero transmissions, AVC/HEVC decode, output assignment, monitoring in Dejero Control and SDI or MPEG-TS playout.
Transport handoff
The verified native handoff is SDI or MPEG-TS with output format, codec/audio result, interface, network, UDP or RTP details and ownership. SRT belongs to a separately named bridge if one is used.
Callaba responsibility
Callaba begins only at a compatible documented input. It can monitor, record, route and publish the resulting feed, but it cannot turn an unsupported WayPoint control into a native SRT feature.
Replace the assumed SRT step with a verified interface contract
- 1. Identify the exact WayPoint generation, current software and compatible Dejero transmitter. Confirm the number and format of assigned outputs using the official product brief and device interface.
- 2. Choose SDI or MPEG-TS as the documented WayPoint boundary. For MPEG-TS, use a dedicated network and configure the receiving decoder or bridge according to Dejero network guidance.
- 3. If SRT is still required, name the physical or software bridge that converts the verified output. Record its input, encoder profile, SRT role, port, latency and encryption as a separate system.
- 4. Create a Callaba endpoint only for a protocol it actually receives from that bridge or source. Do not paste fictional WayPoint SRT fields into screenshots, FAQs or sales instructions.
- 5. Test Dejero reception, WayPoint output, the optional bridge, Callaba telemetry, recording and final destination independently. Preserve evidence at every boundary so incidents have a clear owner.
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.
- Dejero WayPoint product page — Official receiver role, Dejero compatibility, codecs and SDI/MPEG-TS output positioning.
- Dejero WayPoint 3 quick-start guide — Official network setup and MPEG-TS decoder handoff guidance.
- Dejero WayPoint 3 product brief — Official output formats, UDP/RTP transport and system capacity.
Frequently asked questions
Does Dejero WayPoint have a native SRT output?
The current official WayPoint sources reviewed for this page document reception from Dejero transmitters plus SDI or MPEG-TS output; they do not establish a native SRT endpoint. Do not claim one without newer exact-model documentation.
Why keep an srt-gateway URL if the content is corrected?
Changing the canonical URL is a separate migration decision that needs demand, backlink, redirect and internal-link review. Correcting the technical claim immediately is safer than combining it with an unmeasured URL move.
How can a WayPoint feed reach an SRT workflow?
Send an official SDI or MPEG-TS output into a separately documented encoder or protocol bridge, then connect that bridge to Callaba. Name and test both boundaries instead of attributing SRT to WayPoint.
What protocols are documented for WayPoint MPEG-TS output?
The reviewed WayPoint 3 product brief lists UDP and RTP for the MPEG-TS network output. Confirm the exact generation and current software before configuring the receiving system.
What should operators monitor during this handoff?
Monitor the Dejero transmission, WayPoint decode and output assignment, the optional bridge, Callaba receiver statistics, recording and final destination. Each layer needs its own owner and failure evidence.
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.
