VITEC MGW Ace Encoder SRT setup: send SRT to Callaba Gateway
More live video workflow notes and product updates.
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
The VITEC MGW Ace Encoder SRT setup is a direct contribution workflow: keep MGW Ace Encoder at the venue as the SRT Caller and let Callaba Gateway listen in the cloud. Use this setup when MGW Ace Encoder is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. It is useful for live contribution teams that need a hardware encoder feeding a managed cloud gateway instead of a single unmanaged CDN push.
Quick answer
To use VITEC MGW Ace Encoder with SRT, set MGW Ace Encoder as the SRT Caller and send the stream to a cloud SRT Listener. In this guide, Callaba works as the SRT gateway, receiver, monitor, recorder, and routing layer. Because SRT and RTMPS appear in later VITEC documentation and firmware notes, confirm the installed firmware and visible SRT, Stream ID, and RTMPS menus before the event.
MGW Ace Encoder sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and feed multiview in parallel, not as mandatory sequential setup steps.
- MGW Ace EncoderSRT Caller at venue
- Callaba GatewaySRT Listener in cloud
- Preview
- Record
- Route
- Restream
- Multiview
What this setup does
This workflow uses MGW Ace Encoder as the field contribution encoder. The encoder sends SRT over UDP to a Callaba SRT Listener. Callaba then becomes the operational point for checking incoming bitrate, preview, audio meters, recording, restreaming, routing, web playback, API control, and multiview.
The default direction is outbound from the venue. That usually avoids port forwarding at the venue because MGW Ace Encoder calls the cloud listener. Listener and Rendezvous modes are documented for this model, but I would use them only when the network design is tested and the firewall rules are known.
What this model can and cannot do in this workflow
- VITEC lists MGW Ace Encoder as an HEVC/H.265 and H.264 hardware encoder for HD/SD contribution, with public specs up to 1080p60, not 4K/UHD.
- The exact-model datasheet lists SRT Caller, Listener, and Rendezvous, plus UDP TS, RTP TS, RTSP/RTP ES, RIST, ProMPEG FEC, and RTMP. RTMP is listed for H.264.
- VITEC firmware notes for MGW Ace Encoder v2.5.1 add SRT StreamID and SRT with FEC. v2.6.0 adds RTMPS. v2.5.1, v2.6.0, and v2.6.2 notes list SRT library v1.4.1.
- Public sources for this model are inconsistent: older manual mirrors show older transport menus, while later VITEC pages and release notes include SRT, StreamID, and RTMPS. Confirm installed firmware and the visible streaming menu on the unit before the event.
- The encoder has 3G/HD/SD-SDI, HDMI v1.3, DVI-D, and Composite/CVBS video inputs, with embedded SDI/HDMI audio and analog audio options.
- It has two Gigabit Ethernet ports for streaming and management, plus DVB-ASI output for channel delivery workflows that are separate from this cloud ingest setup.
- Do not plan MGW Ace Encoder as a native NDI source. I did not find official exact-model NDI or ST 2110 support in the sources used for this guide.
- VITEC lists AES 128/256 key support, but public exact-model material does not clearly confirm an SRT passphrase field. If your firmware exposes one, treat the passphrase as exact, case-sensitive, and whitespace-sensitive.
- This guide is for MGW Ace Encoder. MGW Ace Decoder and MGW Ace Decoder 4K are receiver/decoder devices for turning network feeds back into video outputs, not the venue-side source encoder workflow described here.
Recommended workflow
For remote contribution, use MGW Ace Encoder as SRT Caller and Callaba as the cloud SRT Listener. Start with H.264 and AAC-LC for a compatibility test, then move to HEVC/H.265 if every downstream decoder, player, or distribution path in the workflow supports it.
If the SRT menu is not present on the installed firmware, update the encoder first. If that is not possible for the event, use RTMPS when the unit exposes it, or RTMP for an H.264 CDN-style path. Use RTSP through a bridge only when the production design needs a local pull from the encoder and a separate system will republish to Callaba.
When not to use this setup
Do not use this cloud SRT path when a local SDI connection is simpler and the encoder is next to the switcher. If the only destination is a public platform and you do not need cloud monitoring, recording, routing, or multiview, RTMP or RTMPS may be enough when your firmware exposes the required menu. Do not choose an NDI plan for this exact model unless you have separate official VITEC documentation for the exact unit.
Before you start
- Check the installed MGW Ace Encoder firmware and confirm SRT Caller settings are visible.
- Confirm whether your firmware exposes Stream ID and, if needed, RTMPS.
- Decide whether the first test uses H.264 or HEVC. H.264 is usually safer for initial preview and web playback checks.
- Confirm the outbound UDP path from the venue to the Callaba server.
- If SRT handshakes are difficult to diagnose, compare the device firmware notes with the server side because VITEC release notes list SRT library v1.4.1 for later MGW Ace Encoder firmware.
Create the Callaba ingest
In Callaba, create an SRT server/listener and choose a UDP port that is allowed through the cloud firewall. If you use Stream ID, copy it exactly from Callaba and keep it short for the first test. Stream ID values are case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can break the SRT handshake.
Wait for the listener to show an incoming connection, then check bitrate, uptime, preview, and audio meters before you build the rest of the production route.
Configure MGW Ace Encoder
In the MGW Ace Encoder web interface, open the streaming output configuration area for the encoder channel. Select the physical input, choose the encoding profile, and set the SRT output to Caller. Enter the Callaba server public hostname or IP address and the UDP port from the SRT listener.
If the firmware exposes Stream ID, paste the exact value from Callaba. If the firmware exposes SRT security or passphrase controls, use them only after a clean unencrypted test and make sure both sides match exactly.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba SRT servers | Create an SRT listener and choose a UDP port | 9000 or another open UDP port | Callaba should show waiting, then connected |
| Callaba SRT server | Stream ID, if required by your routing design | Short exact identifier | Must match the encoder exactly |
| MGW Ace input configuration | Select the active video input | SDI or HDMI for first test | Verify input lock before debugging SRT |
| MGW Ace encoding profile | Video codec | H.264 first; HEVC after compatibility test | Confirms preview and downstream decoder support |
| MGW Ace SRT output area | SRT connection mode | Caller | Venue initiates outbound UDP to Callaba |
| MGW Ace SRT output area | SRT latency value, if exposed | 250-500 ms for internet test | Lower only after RTT, loss, and retransmits are stable |
| MGW Ace SRT StreamID field | Paste the Callaba Stream ID, if used | Exact copy, no trailing spaces | Stream ID is case-sensitive and whitespace-sensitive |
| MGW Ace audio encoding | Audio codec and source | AAC-LC from embedded SDI/HDMI or chosen analog input | Confirm Callaba audio meters move |
Monitoring
After MGW Ace Encoder connects, monitor the incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters in Callaba. Treat preview, recording, routing, restreaming, and multiview as parallel uses of the same received source. Do not wait to test recording until after restreaming is built; verify each downstream output independently.
Failover and local ingest options
For production events, plan what happens if the main encoder, venue uplink, or primary contribution path fails. Callaba can be part of that continuity plan without changing the basic VITEC MGW Ace Encoder ingest workflow.
Recording and playback
Once the SRT ingest is stable, enable recording in Callaba if the show needs an archive or compliance copy. For browser playback and web players, test the codec chain early. HEVC can be correct for contribution, but H.264 is still the safer first choice when the same feed must be previewed or played in many browsers.
Troubleshooting
| Symptom | Check in Callaba | Check on MGW Ace Encoder | Likely fix |
|---|---|---|---|
| No connection | SRT listener port, public IP, and waiting status | SRT Caller mode, destination host, destination port | Open UDP firewall rules and confirm the encoder is calling the correct listener |
| Connection drops | RTT, packet loss, retransmits, uptime resets | Uplink stability and SRT latency value | Raise latency, reduce bitrate, or use a cleaner network path |
| Handshake fails after adding Stream ID | Exact Stream ID configured on the listener | StreamID field value | Remove trailing spaces, copied newlines, or capitalization differences |
| Passphrase test fails | Whether the listener expects encryption | Whether the exact firmware exposes an SRT passphrase/security field | Disable encryption for the first test, then re-enable only with matching values |
| Video connects but preview is black | Incoming bitrate and preview codec support | Input lock, codec, resolution, and profile | Test H.264 first; use HEVC only when downstream support is confirmed |
| No audio | Audio meters and recorded file audio | Selected audio input and audio codec | Select the correct embedded or analog source and retest with AAC-LC |
Official references
Useful resources for confirming the exact unit, firmware, and protocol behavior:
Vendor references
- VITEC MGW Ace Encoder product page
- VITEC MGW Ace Encoder datasheet
- MGW Ace Encoder version 2.5.1 release note
- MGW Ace Encoder version 2.6.0 release note
- MGW Ace Encoder version 2.6.2 release note
Protocol references
Callaba resources
FAQ
What if the SRT menu is missing on MGW Ace Encoder?
Update the firmware if possible. Later VITEC material confirms SRT and StreamID for this exact model, but older public manuals show older transport menus. If you cannot update before the event, use RTMPS or RTMP when the firmware exposes it, or use an RTSP bridge as a planned fallback.
Should MGW Ace Encoder be SRT Caller or Listener?
Use Caller for the normal cloud workflow. The encoder initiates an outbound connection to Callaba, which listens in the cloud. Listener or Rendezvous mode can work in documented SRT designs, but the venue side may need inbound UDP, port forwarding, firewall rules, or a tested NAT plan.
Can I use MGW Ace Encoder SRT Stream ID with Callaba?
Yes, when your firmware exposes StreamID. VITEC v2.5.1 release notes add SRT StreamID support for MGW Ace Encoder. Copy it exactly; capitalization, spaces, and pasted newlines matter.
Does MGW Ace Encoder support an SRT passphrase?
Do not assume it from the public material alone. VITEC lists AES 128/256 key support, but the sources used here do not clearly confirm an SRT passphrase field for this exact model. Use encrypted SRT only if the installed firmware UI or official manual confirms the field.
Can I use HEVC for the Callaba ingest?
MGW Ace Encoder is an HEVC/H.265 encoder, and the datasheet lists 1080p60 profiles. For the first production test, H.264 is usually easier to preview and distribute. Use HEVC when the full downstream chain supports it.
Is MGW Ace Encoder a native NDI source?
No official exact-model source used for this guide lists NDI or ST 2110 support. Do not design this unit as a native NDI source; use SDI/HDMI locally or confirmed IP protocols such as SRT, RTMP/RTMPS, or RTSP.
Next steps
- Create the Callaba SRT listener and note the public address, UDP port, and Stream ID if used.
- Configure MGW Ace Encoder as SRT Caller and start with H.264 plus AAC-LC.
- Confirm connection stats, preview, audio meters, and a short recording.
- Only then add HEVC, encryption, restreaming, routing, or automation.
Try Callaba Gateway with VITEC MGW Ace Encoder SRT
Create an SRT server in Callaba, send the device feed to the gateway, and check the received stream. After ingest is stable, use Callaba outputs for preview, recording, restreaming, multiview, playback, routing, or API workflows as parallel downstream options.