How can people reach the right endpoint when calls cross browser, SIP, and gateway networks?
A Home Assistant telephony platform that routes calls among browser WebRTC clients, SIP desk phones, ATA-connected phones, and gateway-backed destinations.
Telephony & real-time systems / Work project · multi-site deployment
A call-routing platform connecting Home Assistant, browsers, and SIP endpoints.
BUILT FOR THE PLACE IT RUNS
Runs as part of a site’s Home Assistant telephony setup. The working application depends on the HAOS host and configured SIP / gateway equipment, so this is shown as an architecture study—not a public web app.
One site-aware call path can connect browser, SIP, and gateway endpoints.
Choose a control and see how the system’s ideas fit together.
Conceptual call flow · the original service and devices are not contacted here.
A Home Assistant telephony platform that routes calls among browser WebRTC clients, SIP desk phones, ATA-connected phones, and gateway-backed destinations.
Model each site’s endpoints and destinations, then route a call over its configured signaling and media path with clear fallback behavior.
This sequence summarizes the project’s core idea. The interactive panel is a local visual study; use the linked repository or live service for the implemented project.
Start from a browser client, a SIP phone, or a connected gateway.
Coordinate signaling and media through the configured call-routing infrastructure.
If a destination is busy or unavailable, continue through the site’s defined route policy.