What is Immix and what does central-station software do?
Central-station software is the working surface of a monitoring center. Alarms arrive from many sites, each one is placed in a queue, and an operator handles it according to instructions written for that customer. Immix is a central-station and alarm-monitoring software platform of this kind. Its value to a monitoring operator is consistency: every event, whether from a door contact, a panel or a camera, lands in the same place and follows a defined procedure, so response quality does not depend on which operator happens to be on shift.
Video changes the job. A bare alarm says that something triggered; attached video lets the operator see whether a person is actually present and decide what to do. A surveillance trailer suits this model well, because it is often placed at exactly the kind of site where a human cannot cheaply stand watch. VDS works with Immix, which means trailer events and video can be arranged to flow into that workflow. How they flow depends on the deployment, your monitoring provider's setup and the cameras involved.
How do trailer alarms and video reach a central station?
There are two things to move: the alarm and the picture. The alarm is a small message that says which site, which camera or zone, what kind of detection and when. Standard ways to send it include a webhook, an alarm-style signal, or a message through a platform API. The picture is made available separately, as a live stream or a recorded clip, typically through ONVIF or RTSP or through a video platform that republishes it. Keeping the two apart keeps the alarm fast and light.
The central station then ties the two together. When the alarm arrives, the software can present the matching camera so the operator sees what happened around that moment. That link only works if the identifiers match: the site, camera and zone names in the trailer must correspond to what the monitoring center has configured. Many integration problems are really naming and mapping problems. Agree on a naming scheme before deployment, record it in a shared document, and test each zone end to end with a person walking through it.
Why does video verification matter for response?
Verification is the step between a trigger and a decision. Motion, shadows, animals, insects near the lens and blowing debris can all trigger a simple detector. If every trigger became a dispatch request, responders would learn to distrust the site. Video lets a human or an analytics layer confirm that a real person or vehicle is where they should not be, so only meaningful events escalate. Verified alarms also give police a clearer account of what is happening, which is useful for deciding how urgently to respond.
Analytics at the trailer can reduce noise before it reaches the station by filtering for people and vehicles inside defined zones and schedules. The VDS operations center also verifies alerts and can talk down intruders and send video to police. If you add a separate central station, decide who verifies first, who may speak over the speakers, and who contacts responders, so two parties do not act on the same event or both assume the other has. Clear ownership prevents duplicate dispatches and gaps.
How much bandwidth does alarm-driven video need?
Alarm-driven monitoring is gentler on bandwidth than continuous viewing, which makes it a good match for cellular. Most of the time nothing is requested. When an alarm fires, the operator pulls a live view, a short recorded clip or a few still frames. Total usage then depends on how many alarms occur and how long operators watch, not on how many cameras exist. The planning risk is the opposite one: a noisy site that triggers constantly turns an efficient setup into a heavy one.
Latency matters as much as volume. An operator needs the picture quickly, and a cellular path introduces variable delay. Ask how long it takes from a detection to video appearing in front of an operator, and test it at different times of day. Features such as a short pre-event buffer, recorded on the trailer, can show what happened just before the trigger. Check whether your cellular plan limits data, and tune detection zones so alarms represent events worth watching.
Who owns action plans, records and accountability?
Action plans are the written instructions that tell an operator what to do for each type of event at each site: who to call, whether to use a speaker, when to dispatch, and what to log. Good plans are specific, such as naming the gate, the contact order and the escalation conditions. They should be reviewed whenever the trailer moves, because a new location changes the neighbors, the access routes and the responders. Treat a relocation as a trigger to update the plan.
Records matter too. Each alarm should leave a trail: when it arrived, what the operator saw, what was done and when it was closed. Decide where the evidence video is stored, who can export it and how long it is kept. The trailer records on the unit and the VDS cloud provides two weeks of recording as standard, but your contract with the monitoring provider may require longer retention elsewhere. Settle that before an incident, because after one is a bad time to discover a gap.
What should you ask before connecting a trailer to Immix?
Ask your monitoring provider how they accept alarms from new sources and what they need to see for a trailer to be accepted. Ask the VDS team which events the trailer can send, which camera models and firmware are involved, and which integration method will be used. Confirm who configures each side, who tests, and who is on call when alarms stop arriving. Also ask what happens if the cellular connection drops: is there a heartbeat or supervision signal that tells the center a site has gone quiet?
Common pitfalls are mismatched names, unrealistic expectations about speed, and detection that is too sensitive. Start with one trailer, a small number of zones and a clear success test, then expand only once alarms arrive reliably and operators trust what they see. Treat each new site as a fresh test of naming, timing and response. Always confirm the exact camera model, firmware and integration method with the VDS team before committing. All product names, including Immix, are trademarks of their respective owners; mention here does not imply endorsement or affiliation.
Key terms
- Central station
- A monitoring center where trained operators receive alarms from many customer sites and respond by following written procedures for each one.
- Alarm event
- A short message from a site that something triggered, usually carrying the site, zone, type of detection and time so an operator can act.
- Video verification
- Using live or recorded video to confirm whether an alarm is a real person or vehicle, so only genuine events escalate to dispatch.
- Action plan
- A written, site-specific set of instructions telling operators who to contact and what to do for each kind of event.
- Webhook
- An automatic HTTP message one system sends to a chosen address when an event occurs, commonly used to forward alarms between platforms.
- Supervision signal
- A regular check-in message from a site that lets the receiving center know the connection is alive and flag when it goes silent.
- Pre-event buffer
- A short stretch of video kept just before a trigger, so reviewers can see what led up to an alarm and not only the moment itself.
VDS integrates with Immix using ONVIF and RTSP for camera video, and AI VisionStream sends alarms to it. A trailer like this records on the unit, with two weeks of cloud recording as standard, and the VDS operations center can verify alerts, talk down intruders and send video to police. Many sites use their own monitoring provider instead, which receives the same alarms and video. Confirm the details for your deployment with the VDS team.
Common questions
Can alarms from a surveillance trailer go to Immix?
VDS works with Immix. A trailer can forward detection events using standard methods such as webhooks or alarm signals and make video available over ONVIF or RTSP. The exact path depends on the deployment, so confirm the camera model and method with the VDS team.
Do I need both the VDS operations center and a central station?
Not always. Some owners use one, others combine them, with the operations center screening events first. What matters is that responsibilities are written down: who verifies, who speaks to intruders and who contacts responders, so nothing is duplicated or missed.
How fast will video appear when an alarm fires?
It depends on the cellular signal, the stream settings and the integration method. Delay is variable on cellular links, so test detection to video-on-screen at different times of day, and ask for a pre-event buffer if you want to see what led up to the trigger.