Telehealth & live education
ConnectRoom
Real-time video, chat and Q&A that holds up
A WebRTC video stack with synchronised presence and connection resilience, used where a dropped call is a missed consultation rather than an inconvenience.
This example comes from the technical delivery experience behind AussieSync. It does not necessarily represent a project contracted directly through AussieSync.
Have a process like this one? Tell us about it.
01 Problem
Live video is unforgiving: presence must stay synchronised and connections must survive the networks people actually have.
- Participants saw stale presence, with people shown in a room they had already left.
- A brief network change dropped the call rather than recovering it.
- Room fan-out had to scale without broadcasting every event to every connection.
- Chat and Q&A had to stay consistent alongside the media stream, not drift from it.
02 The solution
WebRTC signalling paired with WebSocket messaging and pub/sub room fan-out.
- A signalling service negotiates peer connections and re-negotiates after a drop.
- Chat, Q&A and presence run over a persistent connection alongside the media session.
- Rooms fan out through pub/sub, so a message reaches only that room’s subscribers.
- The same backbone is packaged as an embeddable SDK for drop-in rooms elsewhere.
03 Technical approach
Every choice earns its place.
- WebRTCPeer media transport with renegotiation after connection loss.
- Node.js signallingNegotiates and repairs peer connections.
- Redis pub/subRoom-scoped fan-out for chat, Q&A and presence.
- Flutter & ReactClients across web and mobile on one session model.
04 Outcome
Face-to-face reach without travel, and live audiences that stay engaged.
- No travelrequired for face-to-face consultations
- Engagedaudiences through live chat and Q&A
- Reusableas a drop-in SDK for other products