Build Your First AI Project This Weekend
Stop consuming tutorials. Start creating. Get the free step-by-step guide.
Do not install OpenVBX.
Twilio abandoned the project in 2017. The old openvbx.org domain redirects to Twilio Studio. The last official code sits on GitHub as a museum piece. PHP 5.2-era software on a 2026 server is a security problem, not a “bootstrap hack.”
I used to teach a full install here. That was the wrong advice to keep publishing.
If you need call tracking, go to the CallRail setup guide. That is the default for local businesses, agencies, and pay per call.
This page stays up for people searching “OpenVBX” so they get a straight answer instead of a 2017 tutorial.
What OpenVBX Was
OpenVBX was Twilio’s open-source, self-hosted phone panel. Buy numbers through Twilio. Build a simple call flow. Forward to a client. Record the call.
For a minute, that was a cheap way to prove a pay-per-call offer before paying for CallRail.
Then Twilio stopped shipping it. No security patches. No modern PHP support. No dashboard you can trust. Community forks exist, including gegere/OpenVBX. Forks do not make it a product.
The “you only pay Twilio usage” pitch is still true for Twilio. It is not true for OpenVBX. You also pay in broken installs, missing recordings, and a number that dies when your shared host upgrades PHP.
What To Use Instead
Default: CallRail.
You get tracking numbers, recordings, dynamic number insertion, call flows, and Google Ads conversion upload. CallRail sunset Lead Center (their VoIP/softphone) on January 27, 2026. Tracking still works. Calls forward to a real phone or a separate VoIP. Read the CallRail guide and start the trial.
If you sell calls, not just track them: Ringba.
Ringba is built for routing to buyers. CallRail is built for attribution. Different jobs.
If you are actually building a phone product: Twilio Studio + Voice API.
That is what Twilio wants you on. US local numbers are $1.15/month. Inbound local is $0.0085/min. Outbound is $0.014/min. Studio is $0.0025 per flow execution. You write the tracking logic. You own the maintenance.
If you need a self-hosted PBX, not a call tracker:
These are real, maintained phone systems in 2026. They are not a drop-in OpenVBX replacement for “which Google Ads keyword rang the plumber.”
- FreePBX (Asterisk GUI, Sangoma)
- FusionPBX (FreeSWITCH GUI, still shipping commits)
- VitalPBX (Asterisk-based, commercial + self-host)
I am not going to walk you through installing any of them here. If you do not already know you need a PBX, you do not need a PBX.
Why The Old Install Guide Is Gone
The 2017 walkthrough told you to unzip PHP onto shared hosting, paste Twilio credentials, and drag a Dial applet.
That stack is how you get:
- A tracking number that stops ringing after a host PHP upgrade
- Recordings you cannot find when a client disputes a lead
- An unpatched web app sitting on the public internet with your Twilio auth token in a config file
Call tracking exists so you can prove which ad produced which call. If the system is flaky, you have no proof. Then you saved $45/month and lost the client.
For a local service business, pair CallRail with AI missed-call capture so the lead does not die in voicemail. That combination beats a dead open-source panel every time.
Take Away
Do not use OpenVBX. Twilio left it in 2017. There is no good 2026 reason to install it.
Use CallRail unless you have a specific reason to be on Ringba (call buying) or Twilio Studio (you are building software).
Have questions? Contact me. If you are still on an old OpenVBX box, migrate the numbers and shut it down.