Receive
Ingest live video from supported cameras, remote sites, drones, mobile sources, applications and streaming platforms.
Direct answer
ORBNET Streaming Engine can receive supported video streams and redistribute them using another supported streaming protocol.
This allows workflows such as RTSP to SRT, SRT to RTSP, RTSP to WebRTC, RTMP to HLS or HLS to RTSP. The engine can operate as a protocol converter, streaming gateway or distribution layer between Milestone XProtect, external video sources, browsers and third-party platforms.
Ingest live video from supported cameras, remote sites, drones, mobile sources, applications and streaming platforms.
Translate supported incoming streaming protocols into the protocol required by the receiving system or viewer.
Route video to one or more destinations, including XProtect workflows, external systems, web applications and compatible viewers.
Compatibility note: The precise configuration depends on the source stream, codec, resolution, audio requirements, security settings and intended output. ORBNET can confirm the appropriate workflow for a specific deployment.
Protocol conversion
Receive a supported stream, route it through ORBNET Streaming Engine and deliver it using the protocol required by the destination.
Control how video enters, leaves and moves between XProtect and external systems without restricting every source and destination to the same protocol.
StreamForce architecture
Streaming Engine, ORB Driver and StreamLink perform different roles. They can operate individually or be combined to create an end-to-end workflow spanning remote video contribution, protocol conversion, XProtect ingestion and external distribution.
Bring edge video back securely
StreamLink is a lightweight edge application that collects compatible video from a remote or distributed location and contributes it to Streaming Engine using SRT.
Use StreamLink for:
Convert, route and distribute video
Streaming Engine is the central protocol-conversion and distribution layer. It receives supported streams and publishes compatible outputs for XProtect, browsers, mobile workflows and external platforms.
Use Streaming Engine for:
Present more video sources inside XProtect
ORB Driver presents supported video streams to Milestone XProtect, helping external or non-standard sources operate as manageable video sources within the VMS.
Use ORB Driver for:
Components are selected around the workflow: not every deployment requires all three components, and they do not always operate in a fixed sequence.
Example configurations
Video gateway selection
The best video gateway depends on where the video is coming from, where it needs to go and what each system can receive.
A suitable gateway should support the required video direction, streaming protocols, live or playback access, network conditions and operational-resilience requirements. These six questions provide a practical starting point.
Determine whether the gateway must bring external video into XProtect, distribute XProtect video externally or support workflows in both directions.
Confirm the protocol used by every source and destination, including requirements for RTSP, SRT, RTMP, HLS, WebRTC or other supported formats.
Some workflows require live video only, while others also need authorised access to recorded or playback video from Milestone XProtect.
Browser and mobile delivery may require WebRTC, HLS or LL-HLS rather than the protocols normally used by cameras and video-management systems.
Remote, mobile or variable network connections may benefit from SRT and an edge-contribution component such as ORBNET StreamLink.
Consider API control, monitoring, concurrent workflows, load balancing and high-availability requirements before selecting the final architecture.
ORBNET Streaming Engine is designed for workflows that require protocol conversion, bidirectional video movement, external source ingestion, XProtect live or playback distribution, browser delivery, API-controlled routing or resilient multi-destination deployment.
Deployment models
Streaming Engine can be positioned around the sources, networks and receiving systems involved in the deployment. It can operate as a central service, receive contribution from distributed locations or form part of a more resilient streaming architecture.
Central deployment
Position Streaming Engine close to Milestone XProtect or the main video infrastructure when several systems need a shared conversion and distribution layer.
Typical applications
Distributed deployment
Combine Streaming Engine with ORBNET StreamLink when compatible video must be collected at a remote, mobile or temporary site and contributed back using SRT.
Typical applications
Resilient deployment
Use load-balancing and high-availability deployment options where the streaming service requires increased resilience, capacity or operational continuity.
Typical considerations
XProtect ingestion
Add ORB Driver when compatible external streams need to be presented and managed as video sources inside Milestone XProtect.
Edge contribution
Add StreamLink when video needs to be collected at a remote location and contributed securely to Streaming Engine using SRT.
Complete workflow
Combine the components when the deployment spans remote contribution, protocol conversion, XProtect ingestion and external video distribution.
Sizing note: Final architecture and capacity should be determined from the number of sources, destinations, viewers, protocols, codecs, resolutions and resilience requirements involved in the deployment.
ORBNET Streaming Engine is the protocol-conversion and video-distribution layer within the StreamForce ecosystem. It receives supported video streams and redistributes them to XProtect workflows, external systems, browsers and compatible viewers.
Yes. Streaming Engine can receive a supported RTSP or RTSPS stream and provide an SRT or WebRTC output as part of a configured streaming workflow.
Streaming Engine supports conversion and redistribution between supported input and output protocols, including workflows that provide an RTSP or RTSPS output. Compatibility should be confirmed against the source codec, security settings and intended destination.
Yes. Streaming Engine can distribute authorised live or playback video from Milestone XProtect to compatible external platforms, applications and viewers.
Yes. Streaming Engine can receive external video sources and can operate with ORB Driver when those sources need to be presented and managed inside Milestone XProtect.
Streaming Engine can provide compatible browser-delivery workflows using protocols such as WebRTC, HLS or LL-HLS, subject to the requirements and configuration of the deployment.
No. Streaming Engine can operate as a video-conversion and distribution layer for supported external streams. Milestone XProtect integration is one of the workflows available within the wider StreamForce ecosystem.
Streaming Engine supports deployment options that include load balancing and high availability for workflows requiring increased resilience or scale.
The best video gateway depends on whether the deployment needs external ingestion, video distribution, protocol conversion, browser delivery, playback access, API control or high availability. ORBNET Streaming Engine is designed for XProtect deployments that require several of these capabilities in one video-routing layer.
Compatibility and final architecture depend on the source stream, codec, destination, network conditions, security settings and deployment requirements.