Media server compatibility
RBT uses a media server to provide live camera video, previews and archive playback to resident and operator clients. The media server is deployed separately from the intercom backend, so an operator can select the implementation that matches an existing video platform or a new Sesameware installation.
Supported media servers
| Media server | When to choose it |
|---|---|
| SesameDVR | Recommended for a new Sesameware deployment that needs a first-party DVR, live HLS/WebRTC, archive playback, ONVIF events, monitoring and flexible storage |
| Flussonic Media Server Basic | Suitable when an operator already uses Flussonic and needs to connect RBT to the existing media infrastructure |
| Nimble Streamer | Suitable for deployments that already use Nimble for camera delivery and have validated the required live and archive endpoints |
| Macroscop | Available for projects built around an existing Macroscop video surveillance deployment |
| Forpost | Available for compatible deployments that already use the Forpost media platform |
Compatibility means that RBT can use the configured media server for supported camera workflows. Exact live playback, archive depth, authorization and event capabilities depend on the media server version, license and integration configuration. Do not assume that every server provides the complete SesameDVR feature set.
What to validate before deployment
- Confirm that every required camera codec and stream profile can be played by the target mobile and web clients.
- Test live video, preview images and archive playback for a real camera through RBT.
- Verify user authorization, public TLS, time synchronization and archive retention.
- Check how the server behaves when a camera, network path or storage volume becomes unavailable.
- Measure concurrent playback and recording load with the planned number of cameras.
For a new installation, start with the SesameDVR overview and system requirements. For an existing third-party media platform, contact Sesameware with its product version and the required live/archive workflows before rollout.