Add a mobile app to your PBX, without changing your PBX
Spanvox registers to your existing PBX like an ordinary softphone, then hands your customers a branded mobile app. No SIP trunk. No dialplan edits. No firewall rules. And push that wakes the app so backgrounded calls still ring.
- No SIP trunk
- No dialplan edits
- No firewall rules
- Push that wakes
To your PBX, we look like a softphone
Spanvox holds a live registration to your PBX on each endpoint’s behalf, and a push-driven registration from the app. Your switch sees an ordinary phone, so the disruptive parts simply do not happen.
No SIP trunk
Spanvox is not a trunk. Dual SIP registration bridges the app to your PBX, so there is nothing to provision and no routing to configure.
No dialplan edits
Because we register as a normal endpoint, your dialplan, extensions and call flows stay exactly as they are.
No firewall rules
The app reaches Spanvox over 443; we hold the registration to your PBX. You never open inbound ports or expose the PBX.
Connect your PBX in three steps
Point an endpoint at your PBX
Give Spanvox the extension’s SIP credentials. It registers to your PBX exactly like a softphone, no trunk and no inter-PBX routing.
Brand and ship the app
Your colours, your store accounts, your APNs/FCM identity. Hand users a mobile app that is unmistakably yours.
Calls ring, push wakes
Spanvox holds the registration server-side and pushes to wake the app, so incoming calls ring through your PBX even when it is closed.
Bridges to the SIP PBX you already run
Adding a mobile app to your PBX
How do I add a mobile app to my existing PBX?
Point a Spanvox endpoint at your PBX and it registers exactly like a SIP softphone. You hand users a branded mobile app; calls route through your existing PBX with no trunk, no dialplan change and no firewall edit.
Do I need a SIP trunk to connect the app?
No. Spanvox is not a trunk. It uses dual SIP registration to bridge the mobile app to your PBX, so there is nothing to provision as a trunk and no inter-PBX routing to configure.
Do I have to change my dialplan or extensions?
No. Because Spanvox registers as a normal endpoint, your dialplan, extensions and call flows stay exactly as they are. Nothing on the PBX needs to be rewritten.
Will it work if my PBX is behind a firewall?
Yes. The app reaches Spanvox over 443 on a managed media proxy with TURN on an anycast edge, and Spanvox holds the registration to your PBX. You do not open inbound ports or expose the PBX to the internet.
Which PBX platforms are supported?
Any SIP PBX, including Asterisk, FreePBX, FreeSWITCH, 3CX, BroadWorks, FusionPBX, Kamailio and OpenSIPS. If it speaks SIP and accepts a registration, Spanvox bridges to it.
Why does my softphone not ring when the app is in the background?
Self-hosted apps usually lose their socket when backgrounded, so the PBX cannot reach them. Spanvox keeps the upstream registration server-side and pushes via APNs/FCM to wake the app, so incoming calls ring even when it is closed.
Put your PBX in your customers’ pockets
Tell us your PBX and your brand. We will bridge a test extension to a branded app, free, on one SIP domain.