Should a desk phone also act as a branch SBC?
A desk phone can be a sensible session border controller for a small branch, provided the site can tolerate that phone becoming shared infrastructure. The choice becomes less attractive as the number of dependent phones, operational importance or difficulty of remote recovery increases.
Some hosted-PBX platforms call this a router phone: a supported handset runs an embedded SBC and carries signalling and media for other local phones through its tunnel to the hosted system.
The decision is about failure domains
| Question | Router phone is reasonable | Dedicated SBC is safer |
|---|---|---|
| How many phones depend on it? | A small, documented group | A larger branch or platform limit is close |
| What happens when it reboots? | Brief loss is acceptable | Reception, emergency or operational phones depend on it |
| Who controls the handset? | It is fixed, labelled and protected | A user may unplug, move or factory-reset it |
| Is replacement straightforward? | A tested spare and recovery steps are onsite | Remote staff cannot rebuild the role |
| Does the site need redundancy? | No formal availability target | Failover and independent monitoring are required |
The hidden operational costs
The handset is no longer merely an extension. Firmware upgrades, power cycling, switch-port changes and desk moves can affect every phone behind it. A help-desk instruction to “factory-reset your phone” becomes a branch outage if the phone’s infrastructure role is not visible.
Document the router phone’s MAC address, switch port, power source, dependent phones and replacement procedure. Label it physically. Keep a supported spare or a prepared dedicated SBC where recovery time matters.
Test the failure, not just the installation
- Confirm internal, inbound and outbound calls through the router phone.
- Reboot it during a controlled window and time dependent-phone recovery.
- Disconnect its uplink and confirm alarms identify the correct cause.
- Replace it with the spare using the written procedure.
- Check whether local emergency-call arrangements behave as designed.
If nobody can explain what happens to the other phones when that handset is unplugged, the deployment is not ready. The saving is one small appliance; the trade-off is an infrastructure role attached to a user-facing device.
A practical rule
Use a router phone where simplicity is genuinely valuable: a small branch, supported models, modest call volume, accessible equipment and an acceptable recovery time. Prefer a dedicated SBC when the branch is operationally important, has many dependent endpoints, needs independent maintenance or cannot rely on a particular desk remaining untouched.
Related: what an SBC does, VoIP failover and phone provisioning.
Technical reference
Scheduled for 20 August 2026. Check the current platform limit and supported-device list before deployment.