What is Milestone XProtect and what does it expect from a camera?
Milestone XProtect is a video management system, or VMS. Its job is to connect to many cameras, show live video to operators, record footage, and make it easy to search and export later. A VMS does not make pictures; it depends on cameras that speak a language it understands. In practice that means an open standard such as ONVIF, which lets the software discover a camera and its streams, or a direct RTSP address that simply delivers video. Cameras that support these standards are the easiest to add.
This is why a trailer built on open standards fits comfortably. VDS is camera-agnostic, supports ONVIF and RTSP, and works with Milestone, so the trailer's cameras can be treated by the VMS like any other network cameras. What differs is the journey: instead of a short cable run inside a building, the video crosses a cellular network from a remote site. That journey, not the camera protocol, is where most of the design effort belongs, as the sections below explain.
How does video get from a remote trailer into XProtect?
Typically the VMS needs a path to each camera, or to a gateway that presents the cameras. You add a device by entering its address and credentials, and the VMS asks it what streams it offers. On a private building network that is simple. On cellular it usually is not, because carriers rarely give devices an address that outsiders can reach, and exposing cameras directly to the internet is a security risk. So the path is generally built with a secure tunnel, a private network or a cloud relay.
A relay approach has a practical advantage: the trailer makes an outbound connection, which cellular networks allow, and the platform republishes the video in a form your VMS can pull. The trade-off is one more component to understand and monitor. Whichever route you use, ask who owns each hop, how it is secured, how credentials are protected, and what happens when the link drops and returns. The correct design depends on your IT policy and your current XProtect setup, so settle it with the VDS team before ordering.
How much cellular data do camera streams use?
Streams consume data according to resolution, frame rate, compression and the busyness of the scene. A higher-resolution camera at a high frame rate costs far more than a modest one, and a scene full of moving trees costs more than a still yard. H.265 generally needs less data than H.264 for similar quality. Add the streams together to see the load, then compare it with what the cellular uplink can reliably sustain at the site, which is often lower than the headline speed.
A VMS can record from the main stream while operators watch a lighter sub-stream, which saves bandwidth when many people look at once. Better still, record on the trailer and bring video across only when needed. VDS trailers record on the unit and add two weeks of cloud recording as standard, so you need not pull every stream continuously into your own servers. If your policy does require a copy in XProtect, budget the bandwidth for it and confirm that your data plan has no caps that would interfere.
How do detection events and alarms reach the VMS?
Many VMS platforms can act on events as well as record video: bookmarking a moment, raising an alarm, or changing the recording mode. For a trailer, events usually originate in its analytics, which detect people or vehicles in defined zones. They can be passed along by standard methods such as webhooks, alarm-style signals, platform APIs or ONVIF events, depending on how the deployment is built. The same detection might be sent by more than one route, so be clear which one your operators are meant to act on.
Quality of events matters more than quantity. A site that raises an alarm for every swaying branch teaches operators to ignore alarms. Define zones, schedules and object types carefully, and trial the setup under real conditions such as wind, rain, headlights and wildlife before relying on it. Decide too what an event should carry, for instance camera name, time and type of detection, so that a person looking at the VMS can understand it without hunting for context.
How should you plan retention, sites and monitoring?
Plan where footage is kept. A trailer holds video locally, the VDS cloud keeps two weeks as standard, and your XProtect system can keep its own copy for as long as your policy requires. More copies add resilience and convenience for search, but they also add bandwidth and storage cost. Choose which copy is the evidence of record, who may export it, and how you will show that nothing was altered. Write retention periods down per site so the answer is clear when someone asks.
Think also about scale and watching. If you will add many trailers, standardize camera names, time settings and credentials, so each new unit looks like the last. Decide who monitors: your own operators, a monitoring partner, or the VDS operations center, which verifies alerts, can talk down intruders and can send video to police. Operators who see fifty trailers need a clear way to tell which is which, so use consistent site names and, where useful, map positions.
What should you ask before connecting a trailer to XProtect?
Ask the VDS team for the camera model and firmware, the streams and events it provides, and the integration method proposed. Ask who configures the VMS side, who tests, and who responds if video stops. Confirm time synchronization, credential handling, and behavior during link loss, since cellular connections drop from time to time and the recording location determines whether footage is lost or merely delayed. Ask about any cap or throttling on the data plan.
Roll out in stages. Connect one trailer, check that video appears reliably, that search and export work, that events arrive and that bandwidth matches the plan, then add more. Treat the first unit as a rehearsal for the whole program. Always confirm the exact camera model, firmware and integration method with the VDS team before committing. All product names, including Milestone and XProtect, are trademarks of their respective owners; mention here does not imply endorsement or affiliation.
Key terms
- VMS
- Video management system: software that connects to many cameras, displays live video, records footage and supports searching and exporting evidence.
- ONVIF
- An open standard that lets cameras and management software from different makers discover each other, stream video and exchange events.
- RTSP stream
- A live video feed requested from a camera at a network address, supported by most IP cameras and accepted by many management platforms.
- Secure tunnel
- An encrypted connection between two networks that lets software reach a remote device without exposing that device directly to the internet.
- Cloud relay
- A platform in the middle that receives video from a remote device and republishes it, avoiding the need for inbound connections to the device.
- Main stream and sub-stream
- A camera's full-quality video and its lighter copy; the lighter one suits live viewing over limited links, the full one suits recording.
- Evidence of record
- The single copy of footage your organization treats as authoritative, with defined retention, access and export rules.
VDS integrates with Milestone using ONVIF and RTSP for camera video, and AI VisionStream sends alarms. A trailer like this connects through a dual-SIM 4G/5G router plus eSIM and records on the unit, with two weeks of cloud recording as standard and unlimited data with no overages, so XProtect need not carry every stream continuously. Confirm the details for your deployment with the VDS team.
Common questions
Does Milestone XProtect work with VDS trailers?
VDS works with Milestone. The trailer supports open ONVIF and RTSP interfaces, and the platform is camera-agnostic. The exact connection method depends on your deployment, so confirm the camera model, firmware and integration approach with the VDS team before you design the system.
Do I have to record everything inside my own XProtect system?
No. The trailer records on the unit and the VDS cloud keeps two weeks as standard. Keeping a copy in your VMS is a policy choice that adds bandwidth and storage, so decide which copy is your evidence of record.
How do detection events get into the VMS?
Events from the trailer's analytics can be forwarded by standard methods such as webhooks, alarm-style signals, platform APIs or ONVIF events. Which one is used depends on how the deployment is built, and testing under real conditions shows how many events operators will see.