Live Video Broadcasting over Bonded 4G LTE and 5G

Bring your encoder, cellular connections and video relay

portabella 2000i and 4000i transparent satisfaction

Want to see a live demo?

We respect your privacy.

Current Streamer models transport an already encoded video stream over multiple WAN connections:

Live production deployment guide

Stream encoded video over bonded WAN connections

Build the workflow around your encoder, current Streamer transport, usable WAN paths and a configured video relay. Validate what the audience or studio receives as well as the device’s connection status.

Encoded video from the field to a server or CDN

  1. Camera / sourceFeed your encoder or switcher
  2. EncoderProduces the selected IP stream
  3. StreamerBonds the configured WAN paths
  4. Video relayReassembles and forwards the stream
  5. DestinationStudio server or compatible CDN
An encoded stream enters Streamer via Ethernet; portable 4000i models also support Wi-Fi input. The video relay is part of the transport path. A decoder is a separate receiving-side requirement when the studio needs a baseband video output.

Choose the transport and production equipment

Current Streamer choices for live video
Model groupWAN inputsProduction requirements
Streamer 4000i4G LTE; four embedded modems, with three-/two-modem options, plus wired WAN.Your encoder/switcher, activated SIMs, antennas and configured video relay.
Streamer 4000i 5G5G with 4G LTE fallback; four, three or two embedded modems, plus wired WAN.Verify modem/carrier compatibility and the encoder input, protocol and relay service.
Streamer 1UWired Ethernet WANs and two USB ports for external cellular modems.Rack power/network installation, Ethernet encoder input and the receiving-side or cloud video relay.

Portabella can use the optional Streamer software add-on for live video optimization. Streamer PRO and Teleporter are End-of-life historical designs; they are not the current embedded-modem Streamer models. Compare the current family brochures.

Set up the complete broadcast path

  1. Verify the encoder and destination. Confirm the video/audio format, bitrate, stream protocol, destination URL and any stream credentials against the chosen server/CDN and relay service.
  2. Bring each WAN online. Activate and test each cellular or wired path independently. Check antennas, carrier plans, wired WAN addressing and available uplink capacity.
  3. Connect the encoded stream. Connect the encoder/switcher through the supported Ethernet or Wi-Fi input. Keep the encoder and transport LAN settings consistent with the supplied configuration.
  4. Configure and verify the video relay. Confirm the Streamer-to-relay connection and the relay-to-destination path. The Streamer VOM reference uses “Connected to BPA: YES” as a connection check; use the applicable firmware/status view.
  5. Select the bitrate and delay policy. Leave adequate usable uplink capacity for the stream and transport overhead, including the expected surviving paths. Set the play-out delay for the acceptable production latency and path variability.
  6. Validate at the receiver. Observe the stream at the actual CDN/player or studio endpoint, checking audio/video sync, continuity, delivered bitrate and end-to-end delay.

Understand adaptive transport, capacity and latency

Video Armor uses the relay and its buffering/transport configuration to handle the encoded stream over changing WAN paths. The bonding algorithms adapt path use as capacity, delay, loss and outages change.

A larger permitted play-out delay can provide more time to handle path variation, at the cost of added production latency. The older support reference explains that a sender delay approaching or exceeding the configured play-out delay can produce an uneven output stream. Use the values approved for the exact model, firmware and production workflow.

If usable uplink capacity falls below the stream’s needs for too long, reduce the encoded bitrate or revise the connection mix and delay policy. Total path loss, relay unavailability or a failed encoder/CDN can interrupt the production; the transport is not a guarantee against every failure.

Rehearse the production before going live

  • Record the transport model, modem/carrier mix, firmware, encoder, codec, protocol, bitrate, relay, play-out delay and receiver/player.
  • Run a representative stream for the planned production duration and monitor both the transport and receiving endpoint.
  • In a test setup, disconnect a WAN and introduce reduced capacity, loss or changing delay. Observe receiver continuity, sender/play-out delay and the bitrate supported by the surviving paths.
  • Test competing network traffic, encoder restart and relay/destination reachability, with the expected recovery procedure documented.
  • For a studio workflow, confirm the receiver/decoder, audio/video format and end-to-end production latency.
Can I plug an SDI camera directly into a current Streamer?

The current Streamer models transport an already encoded IP stream and do not include a video encoder. Use an appropriate encoder or switcher for the camera signal. Direct camera inputs belonged to specific historical Streamer PRO/Teleporter configurations.

Do all kinds of bonding use the same relay and settings?

Data bonding and live-video transport have different service/profile and endpoint requirements. Confirm the selected video relay, protocol and delay configuration; do not assume a data-tunnel status proves the complete video path is working.

Configuration references

Discuss your deployment

“Outstanding product. I highly recommend Streamer to anyone who is looking to add quality and reliability to their video streaming capability”

Dirk Dusharme, Editor in Chief Quality Digest

dirkheadshot

Trusted by our clients:

logos all 2

Any personal information you provide by filling out any form on Mushroom Networks website will only be used to provide information and services to you regarding our solutions and products, and will not be shared with any 3rd party. At any point you can completely opt out of future emails, phone calls or other direct communications by simply sending us an email at info@mushroomnetworks.com with that request.

© 2026 Mushroom Networks Inc. All rights reserved.