Haivision MoJoPro SRT setup: smartphone contribution with Callaba Gateway
More live video workflow notes and product updates.
Haivision MoJoPro mobile contribution
Move a MoJoPro live from the phone to StreamHub, then expose a controlled SRT feed in Callaba
MoJoPro turns a supported iOS or Android phone into a professional mobile camera for live and recorded contribution. In this Callaba workflow, the app sends its field contribution to Haivision StreamHub over SST; StreamHub selects the mobile input and creates an SRT IP output; Callaba receives that output for browser Multiview, recording, routing, or delivery.
The important boundary: MoJoPro is not the SRT output in this design
Haivision describes MoJoPro contribution over aggregated cellular and Wi-Fi connections using SST. StreamHub is the receiver that can decode, record, transcode, and distribute that input. The SRT session begins at the separate StreamHub IP output and ends at Callaba. Keeping those stages explicit prevents an operator from troubleshooting an SRT port when the phone has not yet reached StreamHub.
This architecture also keeps the phone simple: the field journalist selects the approved connection and live profiles, checks picture and audio, and starts the transmission. The control-room team owns input assignment and the downstream SRT contract.
The pulses show operational handoffs, not measured bonding performance or end-to-end latency. Motion is removed when the visitor prefers reduced motion.
Decide who controls each stage
| Question | Primary evidence | Owner during the event |
|---|---|---|
| Is the phone capturing the correct shot and audio? | MoJoPro camera view, input selection, VU meter, and live state. | Field operator or mobile journalist. |
| Did the mobile transmission reach production? | MoJoPro network state plus the expected input visible in StreamHub. | Field operator and StreamHub operator together. |
| Is the correct input assigned to SRT? | StreamHub source-to-IP-output assignment. | StreamHub operator. |
| Did Callaba receive the handoff? | Named SRT publisher, session state, and sustained incoming bitrate. | Callaba operator. |
| Can the production actually use the media? | Decoded Multiview tile, audio check, recording, and selected delivery branch. | Downstream production owner. |
Prepare the MoJoPro connection without typing production secrets on site
Haivision StreamHub can export a connection profile for MoJoPro. In StreamHub, open the connection-profile control, verify the public address or hostname the phone can reach, and download the profile. Import the resulting profile into the app using the approved distribution process. Validate it on the same MoJoPro version and mobile operating system planned for the event.
Keep one clearly named destination for the intended StreamHub and one live profile for the event’s picture and audio requirements. MoJoPro supports H.264 and HEVC according to Haivision’s product documentation, but the choice must be compatible with StreamHub and every downstream Callaba branch. A local recording profile may intentionally differ from the live profile; document which file is the editorial master.
Before leaving for the venue, confirm camera permissions, microphone selection, available storage, battery and charging plan, orientation policy, notifications, and the operator’s ability to lock the live view. These are not SRT settings, but they are common reasons a technically healthy network feed becomes unusable.
Create the StreamHub SRT output and Callaba receiver
- Start with Callaba. Create an SRT Listener, assign a reachable UDP port, approve the expected publisher identity, and apply firewall restrictions. Start it before the StreamHub output calls.
- Create the output profile in StreamHub. Select SRT, choose Caller for the straightforward outbound handoff, enter the Callaba address and port, and configure the agreed latency and optional encryption.
- Match access values. Stream ID and encryption settings must agree at both ends. Do not place passphrases in channel names, screenshots, article URLs, or QR codes intended for broad distribution.
- Assign the live MoJoPro input. Wait until the expected mobile source is visible in StreamHub, then bind that exact input to the SRT output. A profile without an assigned source carries nothing useful.
- Accept the output in Callaba. Verify publisher identity and transport state, then open the media in Multiview or record a short sample. Listen as well as look.
Use the Callaba SRT Server guide for current dashboard controls. The SRT Server product page explains the monitoring, access-control, routing, recording, and deployment layers available after the handoff.
Run a phone-to-control-room acceptance test
Start the MoJoPro live from a location with known connectivity. Confirm the app shows an active transmission and useful bitrate, then identify the matching input in StreamHub. Ask the field operator to cover the lens briefly and speak a unique phrase; this proves source identity without relying on a filename. Assign the source to SRT and verify the same visual and audio cue in Callaba.
Next, start a short Callaba recording and open the intended downstream destination. Check the live picture, recorded file, audio channels, and lip sync. If video return or intercom is part of the production, test it as its own reverse-direction workflow; do not infer its health from the outgoing picture.
Finish with controlled recovery: move between expected networks, background and foreground the app only as permitted by the runbook, and interrupt the StreamHub output separately. Record what reconnects automatically and what requires an operator. Behavior can vary with app, OS, StreamHub, and policy versions.
Use MoJoPro for the jobs it is good at
Breaking-news contribution: pre-provision profiles so a journalist can begin a verified live without assembling an SRT URL in the field. Remote interview: use the phone camera and selected microphone while the control room monitors the handoff and records the accepted source. Sports or event update: retain a local file while delivering a live contribution, then define which asset should be forwarded if the live path is interrupted.
Diagnose the first missing proof
The app cannot reach StreamHub
Verify the imported connection profile, reachable hostname, mobile permissions, network state, receiver availability, and assignment policy. Keep the downstream SRT output out of the diagnosis.
StreamHub sees the phone but has no usable media
Check the selected camera, microphone, live profile, codec, and app permissions. Compare the local camera preview with StreamHub’s decoded input.
StreamHub is healthy but Callaba is idle
Confirm that the SRT output is started and carries the MoJoPro input. Compare mode, address, UDP port, firewall, Stream ID, and encryption on both endpoints.
The wrong mobile source reaches Callaba
Do not rebuild the SRT transport. Correct the StreamHub input assignment and use unique source names for simultaneous reporters.
Audio is silent or distorted
Inspect MoJoPro’s input and VU meter first, then StreamHub, then Callaba. Avoid changing codec and network settings while tracing an input-gain problem.
The recording fails but live monitoring works
Preserve the proven phone, StreamHub, and SRT path. Check only the selected Callaba recorder, storage, retention, and file playback.
Official references
Use Haivision’s MoJoPro product page for current capture, codec, and network-aggregation claims. Match operator steps to the installed app in the official MoJoPro live-streaming documentation. Generate the approved mobile connection from Haivision’s StreamHub connection-profile procedure, then configure the downstream route with the official StreamHub SRT output guide.
Review adjacent contribution options in the Haivision and Callaba workflow hub. Recheck app, OS, and StreamHub versions before every production rollout.
Give the mobile live a visible receiving boundary
Prove the phone in StreamHub, prove the SRT handoff in Callaba, and only then attach recording, routing, or delivery.