ANONYMIZED CLIENT / HEALTHCARE DEVICES / REAL-TIME AUDIO + VIDEO

Real-time audio and video for connected care devices.

I built resilient shared communications infrastructure connecting wearable, bedside, wall-mounted, mobile and browser devices across care facilities — with MQTT-triggered calls, SIP endpoints, FreeSWITCH audio and Janus video.

ROLEVOICE + VIDEO INFRA ENGINEER

CUSTOMERS~30 CARE FACILITIES

DEVICES~200K REGISTERED

PEAK~10K CONCURRENT SESSIONS

THE SITUATION

Care teams and patients needed one communication layer across radically different devices.

Wearables initiated calls through MQTT, while stationary units spoke SIP directly. The same shared infrastructure had to support patient-to-staff, staff-to-staff, emergency escalation, broadcasts and group audio/video while preserving tenant-aware routing for dozens of facilities.

ARCHITECTURE

Two device protocols enter one tenant-aware communications fabric.

Wearable events become calls through MQTT orchestration; stationary endpoints register through SIP. Database tenancy selects routing while FreeSWITCH/RTPengine and Janus provide shared audio and video media.

01 WEARABLESMQTT call triggerstaff + patients
→ 02 STATIONARYSIP devicesrooms + wards
→ 03 TENANT ROUTINGOpenSIPS + databasefacility isolation
→ 04 AUDIO MEDIAFreeSWITCH + RTPenginebridges + NAT
→ 05 VIDEOJanus WebRTCcalls + groups

WHAT I BUILT / HARD PROBLEMS

Two signaling models, shared media and healthcare workflows that cannot simply fail.

MQTT → SIP CALL CONTROL

Wearable events were converted into tenant-aware call sessions, destinations and escalation flows without requiring a full SIP endpoint on the device.

SHARED TENANT MEDIA

Database isolation kept facilities separate while common signaling and media infrastructure supported calls, groups and broadcasts.

RELIABLE AUDIO + VIDEO

FreeSWITCH, RTPengine and Janus were deployed with monitoring that exposed registration, routing, NAT and media failures at customer sites.

OUTCOME

One communications platform serving devices across ~30 care facilities.

Patients and staff could reach each other through wearable, stationary, mobile and browser endpoints using audio, video, groups and escalation workflows. Shared infrastructure remained operable at high device and session counts without losing tenant-aware routing.

~30 FACILITIES / ~200K REGISTERED DEVICES / ~10K PEAK SESSIONS / ~500 PEAK CPS

OPENSIPS · FREESWITCH · RTPENGINE · JANUS · SIP.JS · EMQX / MQTT · RABBITMQ · REDIS · POSTGRES / TIMESCALEDB

All scale figures are approximate production values; facility and customer identities are withheld.

Discuss your project