Working remotely with the web client
The zero-install remote option: because the web client makes calls with WebRTC in the browser,
anyone who can reach https://your-fqdn has their full extension — calls, chat, voicemail,
presence — from any machine, anywhere. No VPN, no client software, no per-user setup.
What works from anywhere
Everything the office web client does: making and receiving calls, hold/transfer/conference, the Team view and Panel, chat and SMS, voicemail and recordings. Calls ring the browser tab alongside the user's other registered devices; the browser must stay open to stay reachable.
How the audio gets through
Browsers behind home NAT can't receive media directly, so the system's built-in TURN relay carries call audio between the browser and the PBX. It was configured during installation — the TURN ports (3478 and the 16485–16584 relay range, the top half of the forwarded media block) must be open on your firewall for remote browser calling to work. Credentials are time-limited and minted per session; there's nothing to manage.
Requirements
- A valid HTTPS certificate on your FQDN (browsers refuse microphone access on insecure origins) — automatic if you chose ACME certificates at install.
- A current browser — Chrome, Edge or Firefox.
- Microphone permission — granted per browser on first call.
Emergency-calling caveat
A remote user dialing 911 through the web client presents the office's registered address to emergency services — see emergency calling for the policy implications.
When you need a desk phone instead
The web client covers any browser; the Exovo app for Windows gives frequent callers a dedicated desktop softphone over the same secure tunnel the SBC uses — global hotkeys, HID headset controls and a BLF key strip included. Physical phones at remote locations use the per-phone VPN or a site SBC. Mobile apps carrying the same extension are in development on the same foundation as the Windows app.