Haivision Makito X4 Rugged SRT setup: field contribution with Callaba Gateway

May 19, 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

Haivision Makito X4 Rugged is the ruggedized version of the Makito X4 encoder family for demanding field, vehicle, ISR and remote contribution environments. Unlike a regular studio-style Makito X4 deployment, the Rugged version is built for harsh operating conditions, vibration, mobile platforms, constrained links and workflows where metadata such as KLV or CoT can be part of the real value of the stream.

The practical Callaba path is straightforward: create an SRT listener in Callaba Gateway, then configure Makito X4 Rugged as an SRT caller. After Callaba receives the field stream, you can monitor it in the browser, put it on a multiview board, record it, create playback links, or route it to another destination.

This guide is written for the search intent behind Haivision Makito X4 Rugged SRT, Makito X4 Rugged multiview, Makito X4 Rugged recorder, Makito X4 Rugged playback, Haivision rugged encoder SRT Gateway, field contribution SRT and Callaba SRT Gateway.

Quick answer: how do I connect Makito X4 Rugged to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then create an SRT stream on Makito X4 Rugged in Caller mode. Enter the Callaba public IP or DNS name, destination port, latency, stream ID if used, and the same passphrase if encryption is enabled.

Makito X4 Rugged sends native SRT from field or mission environments to Callaba Gateway. Callaba then handles browser monitoring, recording, playback and routing.

What this setup does

This workflow sends a live field video feed from Makito X4 Rugged to Callaba Gateway over SRT. Callaba receives the stream in the cloud and turns that field contribution feed into something operators can monitor, record, play back and route.

Makito X4 Rugged: encodes the source and sends native SRT from the field.
Callaba Gateway: listens on a public UDP port and accepts the incoming SRT stream.
Operators: use Callaba to check preview, bitrate, codec, audio, metadata, recording, multiview and downstream routing.

Makito X4 Rugged role

Makito X4 Rugged is useful when the source is not sitting in a clean studio rack. It is built for mobile and fixed platforms, harsh environments, constrained networks and workflows where metadata may matter as much as the picture.

Use case	Makito X4 Rugged job	Callaba job
Field contribution	Encode and send SRT from the field location.	Receive, monitor, record and route the stream.
ISR or sensor feed	Carry video and metadata from analog or digital sources.	Act as the cloud gateway and operational checkpoint.
Constrained network path	Tune bitrate, codec and SRT latency for field conditions.	Observe connection state, packet behavior, preview and recording.

Recommended SRT mode: Callaba Listener, Makito X4 Rugged Caller

For normal cloud ingest, use this direction:

Callaba Gateway: Listener
Haivision Makito X4 Rugged: Caller

This keeps the public UDP listener on the cloud side. The field unit only needs to send outbound UDP traffic to the Callaba IP and port, which is usually easier than exposing an encoder behind mobile, satellite, vehicle or venue networking.

For field ingest, Makito X4 Rugged calls the Callaba listener. This keeps the reachable endpoint in the cloud.

A typical URL shape for the rugged encoder SRT caller side can look like this:

srt://YOUR_CALLABA_IP:10500?mode=caller&latency=300&streamid=makito-x4-rugged-main

Use this as a field-format example. In the Makito interface, these values may be entered as separate fields: mode, address, destination port, latency, stream ID and encryption settings.

Latency starting points: for SATCOM or high-jitter field paths, start around 600–800 ms. For 4G/LTE field contribution, start around 300–500 ms. For stable wired networks, you can try 120–200 ms after the stream is clean. Treat these as test values, not fixed rules.

Before you start

Prepare the field network and media profile before the first production test. Rugged workflows fail most often because too many things are tested at once: source, encoder profile, network, encryption, metadata and downstream routing.

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

UDP port Choose one UDP port for this input and open it in the cloud firewall or security group.

Latency Start around 600–800 ms for SATCOM, 300–500 ms for 4G/LTE field links, and 120–200 ms only after a wired path is proven stable.

Bitrate headroom Keep video bitrate below the real uplink limit. Leave room for SRT recovery, metadata and changing field conditions.

Codec profile Use H.264 for the first ingest test when possible. Move to HEVC/H.265 after the Callaba and downstream path are confirmed.

Metadata If KLV or CoT metadata is part of the mission, confirm whether it must be preserved, filtered, monitored or forwarded downstream.

Firmware wording note: field names can change between Makito firmware versions. Look for the SRT protocol or transport settings, then match the meaning of these fields: SRT mode, destination address, port, latency, Stream ID or Stream Identifier, and AES or Encryption passphrase.

Step 1: create the SRT listener in Callaba

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 10500.
Set latency, for example 300 ms as a field-friendly starting point.
Add stream ID and passphrase if your workflow requires them.
Open the selected UDP port in the cloud firewall or security group.
Copy the SRT publisher URL or copy the host, port and SRT settings for the Makito profile.

Testing rule: for the first field test, use one stream, one Callaba listener, one UDP port and no encryption. After the first clean connection, add stream ID, passphrase, metadata validation, recording, multiview and routing.

Step 2: configure the Makito X4 Rugged SRT output

Open the Makito X4 Rugged web interface and configure the stream output that should send field contribution to Callaba.

Select the video input or encoded stream you want to send.
Choose a conservative profile for the first test: H.264, HD, moderate bitrate and known-good audio.
Create or edit an output stream and select TS over SRT or the SRT transport option available in your firmware.
Set the SRT connection mode to Caller.
Enter the Callaba public IP address or DNS name as the destination address.
Enter the same destination UDP port that Callaba is listening on.
Set latency to your starting value.
Enter stream ID if Callaba expects one.
Enable encryption only if you have already prepared the same passphrase in Callaba.
Start the stream and check connection state, preview, audio, metadata and statistics in Callaba.

Settings table

This is the fastest way to avoid mismatches between Makito X4 Rugged and Callaba.

Makito X4 Rugged and Callaba must agree on SRT direction, port, stream ID, encryption, latency, codec and metadata expectations.

Setting	Makito X4 Rugged	Callaba Gateway	Why it matters
SRT mode	Caller	Listener	One side waits, the other connects.
Port	Destination UDP port	Open listener UDP port	A wrong port looks like no connection.
Latency	300–800 ms field starting point	Same policy	Noisy links need recovery time.
Stream ID	`makito-x4-rugged-main`	Same value if expected	Identifies the feed and can drive access/routing logic.
Passphrase	Same passphrase if encrypted	Same passphrase if encrypted	Encryption fails if values do not match.
Metadata	KLV / CoT if used	Preserve or route as needed	Metadata is often part of the real field value.

Codec test rule: Makito X4 Rugged can send HEVC/H.265, but for the first Callaba ingest test use H.264 if possible. If you plan to use HEVC, confirm that your Callaba installation and the downstream preview, player, recorder or transcoding path support that codec.

KLV and CoT metadata notes

Makito X4 Rugged is often used in environments where metadata matters: sensor position, geospatial context, mission data, tracking or downstream exploitation systems. In those workflows, do not treat the video preview as the only test.

In this workflow, treat Callaba as the gateway and transport layer for the received SRT stream. Callaba does not decode KLV or CoT into a dedicated visual metadata panel in the web interface. The practical goal is to preserve the SRT/TS path and pass the stream onward through restreaming, recording or routing when your downstream system expects that metadata. To validate metadata, use a stream analyzer on the receiving side, for example ffprobe or the specialized software used by your operations team.

Confirm whether KLV or CoT metadata is present at the encoder input.
Decide whether metadata should be preserved, filtered or forwarded.
Test the full downstream chain that needs the metadata, not only the browser preview.
Document whether the workflow is video-only, video-plus-audio or video-plus-metadata before the event.

Operational note: browser multiview proves the received picture and audio. It does not automatically prove that every downstream metadata consumer is satisfied. Test metadata separately when it is mission-critical.

Makito X4 Rugged multiview workflow with Callaba

The rugged encoder provides the field contribution stream. Callaba provides the browser monitoring surface after ingest. This matters when operators need to watch several feeds, verify bitrate and audio, and keep route state visible.

After Callaba receives the rugged field stream, the same source can be monitored, recorded, played back and routed.

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

Makito X4 Rugged recorder workflow: field side vs Callaba cloud recording

Source-side validation and Callaba cloud recording do different jobs. Field-side checks confirm that the source exists and the encoder profile is active. Callaba recording confirms that the SRT stream actually reached the cloud workflow.

Layer	What it verifies	Use case
Field/source side	That the source and encoder profile are correct before transmission.	Use during local setup and source validation.
Callaba cloud recording	That the SRT stream actually arrived in Callaba.	Use when you need cloud-side proof of the received workflow.

Makito X4 Rugged playback workflow with Callaba

Callaba playback means browser player, HLS output, embed link or a cloud route after Callaba receives the stream. These links are created in Callaba after you set up a web player or HLS path for the incoming stream.

HLS playlist after Callaba ingest:
https://YOUR_CALLABA_DOMAIN/hls/makito-x4-rugged-main/playlist.m3u8

Player or embed page:
https://YOUR_CALLABA_DOMAIN/embed/makito-x4-rugged-main

Where the links come from: these example URLs are not generated automatically for every stream. Callaba creates them after you create a Web Player or HLS packaging path. Depending on your settings, links may include temporary tokens or authorization parameters.

Troubleshooting

Most rugged contribution problems are caused by source signal, field network, connection-mode, port, stream ID, encryption, codec or metadata mismatches.

Debug the source and SRT connection first. Then check media profile, metadata, preview and downstream output.

1. No connection in Callaba

Confirm Callaba is in Listener mode.
Confirm Makito X4 Rugged is in Caller mode for ingest.
Check destination IP or DNS name on the rugged encoder.
Check that the UDP port is open in the cloud firewall.
Check whether the field network allows outbound UDP to that port.

2. Connection starts, then drops

Increase SRT latency.
Lower bitrate and test again.
Check path stability, packet loss and reconnect behavior.
Avoid starting with the highest 4K profile for the first field test.

3. Connected, but no picture or no audio

Confirm the source input is active on Makito X4 Rugged.
Start with H.264 and a conservative HD profile before testing HEVC or 4K.
If the SRT connection is established but no picture appears, check whether Callaba and the downstream player path support the codec sent by Makito X4 Rugged.
Before debugging downstream output, check whether audio exists in the Callaba source through preview or multiview.

4. Metadata is missing downstream

Confirm that KLV or CoT metadata is actually present in the input signal on the Makito side. Use the Makito interface or a known-good test analyzer.
Check that metadata filtering is not enabled on the Makito SRT output.
Confirm that the final receiving application expects metadata in the same format and transport mechanism, for example KLV inside MPEG-TS over SRT.
If Callaba receives video but the final consumer does not see metadata, test the same SRT stream with ffprobe or a specialized metadata analyzer at the receiver side.
Do not use browser preview as the only metadata validation method. Browser preview proves picture and audio, not mission metadata compatibility.

5. Stream ID or encryption fails

Make sure the stream ID entered on Makito X4 Rugged matches what Callaba expects.
Use the exact same passphrase and encryption settings on both sides.
Test once without encryption, then enable encryption after the base SRT path is stable.

Official references used for this guide

Use these if you need exact Haivision firmware wording, rugged device capabilities, SRT behavior or field encoder specifications.

FAQ

Can Haivision Makito X4 Rugged send SRT to Callaba Gateway?

Yes. Makito X4 Rugged is a native SRT-capable encoder. In a simple cloud ingest setup, create a Callaba SRT listener and configure the rugged encoder as an SRT caller.

Should Makito X4 Rugged be Caller or Listener?

For most public cloud ingest workflows, set Callaba Gateway as Listener and Makito X4 Rugged as Caller. This keeps the open UDP port on the cloud side and lets the field unit send outbound traffic.

Can Callaba record a Makito X4 Rugged stream?

Yes. After Callaba receives the SRT stream, it can record the cloud-side feed as proof that the stream reached the gateway.

Can I monitor Makito X4 Rugged in Callaba multiview?

Yes. After the SRT stream reaches Callaba, operators can monitor it in browser preview or multiview depending on deployment and version.

What should I test first, HEVC or H.264?

Start with H.264 for the first Callaba ingest test when possible. HEVC/H.265 can be used after you confirm that the full Callaba and downstream workflow supports it.

Final practical rule

Make the first rugged field contribution test boring. One source, one UDP port, one listener, one caller, conservative bitrate, H.264 first, metadata off unless needed. When that path is stable, add stream ID, encryption, metadata validation, recording, multiview, playback and downstream destinations.

Last updated: May 19, 2026

Try Callaba Gateway with your Haivision Makito X4 Rugged

Create an SRT listener in Callaba, send a rugged field 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 Makito SRT docs