What is Genetec Security Center and how does a trailer fit in?
Genetec Security Center is a unified security platform used by organizations that want video surveillance, access control and related systems presented in a single operator interface. For a buyer who already runs it, the appeal is simple: operators keep working in the tools they know, and every site, including a temporary or remote one, appears alongside the permanent cameras. A mobile surveillance trailer is just another source of video and events. The real question is not whether a trailer can join, but which path carries its data and who maintains that path.
A trailer is a self-contained site with its own cameras, power, router and recording. To a video management system, each camera is a network device that offers a video stream and, ideally, a standard way to be discovered and controlled. Because VDS builds around open standards and is camera-agnostic, the trailer side presents ONVIF and RTSP interfaces that a platform like Security Center can consume. VDS works with Genetec and has fed trailer camera video into a client's Security Center, though the right design for your site still depends on your network and policies.
How does video travel from a remote trailer into a VMS?
Video usually travels in one of two ways. In the first, the VMS connects to each camera directly: you enter the camera's address and credentials, the VMS discovers its streams through ONVIF or opens an RTSP address, and it pulls video across the network. In the second, a cloud video platform sits in the middle, collects video from the trailer, and relays or republishes it to your system. Both are common. The direct model is simple but needs a reachable network path, while the relay model avoids opening the trailer to inbound traffic.
Cellular links complicate the direct model, because carrier networks typically do not give a device a public, reachable address. Port forwarding is often impossible, and exposing cameras straight to the internet is poor security practice anyway. A secure tunnel, a private network arrangement or a cloud relay solves the reachability problem. Which one fits depends on your IT policy, your existing Security Center architecture and how many trailers you expect to add over time. Treat this as a design decision to make with the VDS team and your own network administrators before the first unit ships.
How much cellular bandwidth should you plan for?
Bandwidth is the planning item most often underestimated. Each camera stream consumes data in proportion to its resolution, frame rate, scene complexity and compression setting. Newer codecs such as H.265 generally carry the same picture in less data than H.264, though a busy scene always costs more than a quiet one. If your VMS pulls every camera continuously at full quality, the total is the sum of all the streams, and that sum must fit within the uplink the cellular connection can actually sustain, not its best case.
A practical approach is to separate what you watch from what you store. Cameras can offer more than one stream: a lighter sub-stream for live viewing and thumbnails, and a heavier main stream for recording or investigation. Recording can also happen on the trailer itself, so full-quality footage stays local while only live views, events and requested clips cross the cellular link. Because uplink capacity varies with signal strength, tower load and time of day, design for the weak moments rather than the average, and ask whether your plan has caps or throttling.
How do alerts and events reach Security Center?
Video is only half of an integration; the other half is events. A trailer's analytics can detect a person or a vehicle in a zone and raise an event. Those events can reach another platform in a few standard ways: a webhook, which is an HTTP message sent to an address you specify; an alarm-style signal; a message through a platform API; or an event published by the camera itself over ONVIF. Which path is used depends on how the deployment is built, and the same trailer can support more than one.
Decide early what an event should do once it arrives. It might raise an alarm to an operator, bookmark a video segment, start a higher-quality recording or simply log a record for later review. Each of those needs the event to carry enough context, such as which camera, what time and what kind of detection, for the receiving system to act on it. Test with real scenes, including wind, headlights and animals, so you learn how many events your operators will see before the system is live rather than after.
Who monitors the trailer and where is video kept?
An integration changes who can see the video, not the need for someone to act on it. Some owners watch trailers from their own control room through Security Center. Others use a monitoring partner or the VDS operations center, which verifies alerts and can talk down intruders and send video to police. Many run a mix: the operations center screens events first, and your team receives the verified ones. Write down who responds, at what hours and what each person is allowed to do, because ambiguity here costs more than any technical flaw.
Retention deserves the same clarity. Footage can live in three places: on the trailer's own storage, in the VDS cloud, which provides two weeks of recording as standard, and in your own recording system, where your policy sets the duration. Keeping a copy in your system gives you control and a single place to search, but it multiplies bandwidth use if every stream is pulled continuously. Decide which copy is the record of evidence, who may export it, and how you will show that an exported clip is unaltered.
What should you ask before connecting a trailer to Security Center?
Start with the camera: model, firmware, and which streams and events it exposes. Standards reduce risk but do not remove it, and small firmware differences can change how a stream behaves. Ask which integration method will be used, who configures each end, and who is responsible when a stream drops. Confirm how credentials are stored and rotated, how clocks are synchronized so footage lines up across systems, and what happens to events if the cellular link goes down for a while.
Then plan the rollout. Begin with one trailer and a short list of success criteria: video appears within an acceptable time, events arrive reliably, operators can find footage, and bandwidth stays within plan. Expand once those hold, and treat the first unit as a test of process as much as technology. Always confirm the exact camera model, firmware and integration method with the VDS team before committing to a design. All product names, including Genetec and Security Center, are trademarks of their respective owners; mention here does not imply endorsement or affiliation.
Key terms
- Unified security platform
- Software that brings video surveillance, access control and other security systems into one operator interface so staff can monitor and investigate from a single place.
- VMS
- Video management system: software that connects to cameras, shows live video, records footage, and lets operators search and export video.
- ONVIF
- An open industry standard that lets cameras and software from different makers discover each other, stream video and exchange events without custom work.
- RTSP
- Real Time Streaming Protocol: a common way for software to request a live video stream from a camera using a network address.
- Webhook
- An automatic HTTP message one system sends to another address when something happens, such as a detection event, so the receiver can react.
- Sub-stream
- A lower-resolution, lighter-bandwidth copy of a camera's video, used for live viewing over limited links while the main stream is saved elsewhere.
- Edge recording
- Storing video on the device or trailer itself, so full-quality footage is kept locally and only selected clips or live views cross the network.
VDS provides a plugin for Genetec Security Center, so a trailer can do more than stream plain ONVIF and RTSP video, and AI VisionStream sends alarms to it. A trailer like this reaches the network through a dual-SIM 4G/5G router plus eSIM and records on the unit, with two weeks of cloud recording as standard. VDS has fed trailer camera video into a client's Security Center. Confirm the scope for your deployment with the VDS team.
Common questions
Can a surveillance trailer send video to Genetec Security Center?
Yes. VDS works with Genetec and has fed trailer camera video into a client's Security Center. The trailer presents open ONVIF and RTSP interfaces, and the exact connection method depends on your network, camera model and firmware, so confirm it with the VDS team.
Do I need a public IP address or port forwarding for the trailer?
Not necessarily. Cellular carriers often do not provide a reachable address, and opening cameras to the internet is risky. A secure tunnel, private network arrangement or cloud relay can carry video instead. Your IT policy and design decide which is used.
Will every camera stream constantly use my cellular data?
Only if you configure it that way. Trailers can record locally and send live views, events and requested clips on demand. Using sub-streams and event-driven pulls keeps traffic modest, so plan bandwidth around your actual viewing pattern.