Accessing a phone's web UI
Every desk phone has its own web interface, and normally reaching it means knowing the phone's IP, being on its network, and knowing its admin password. Exovo removes all three steps: Admin → Phones → ⋮ → Device Web Console opens the phone's UI in a new tab, logged in.
How it works
The console resolves where the phone actually is — its live registration IP on the LAN, its tunnel address for a VPN phone, or its LAN address at the remote site for a phone behind an SBC — and proxies your browser session through to it. Phones on a remote office's LAN are reachable this way even though nothing about them is exposed to the internet.
Where the phone supports it, the login happens automatically using the admin password the system generated at provisioning time (visible under Auth Info if you ever need it manually) — via a one-time login token, so the password never appears in a URL or your browser history.
Security properties
- Access requires your live admin session — the proxied connection is validated against it continuously, so logging out of the console cuts off phone-UI access immediately, and access windows expire after a few hours regardless.
- Phone web passwords are strong, random and per-device; you never set or share them.
- The path to the phone rides the same authenticated channels as calls (VPN tunnel, SBC mTLS tunnel) — no inbound ports on the phone's network.
When to use it
Provisioning covers the settings that matter day-to-day, so the phone UI is for the exceptions: Wi-Fi credentials on wireless models, uploading VPN certificates on Grandstream, vendor-specific tweaks Exovo doesn't manage, or just checking what a misbehaving phone thinks its state is. Anything Exovo does manage should be changed in the console — a reprovision will overwrite conflicting local edits.