Your dial plan stays in charge
The AI is a destination. Which calls reach it, and under which conditions, remains a VitalPBX routing decision.
VITALPBX + VOXLINK
Add AI Voice Agents to Your VitalPBX System
VitalPBX gives you Asterisk-level control over the dial plan, and that control is the point - not something to trade away.
Most AI voice products expect you to move numbers to them and inherit their routing. For a team that has deliberately built its own PBX, that is a downgrade.
In a compatible deployment, VoxLink is reached through a dedicated SIP/PJSIP endpoint, so the AI becomes a destination your dial plan chooses - not a layer above it.
Your trunks, numbers, contexts and routing logic stay yours. The configuration follows your actual PJSIP design; nothing is hard-coded.
Answer calls, book appointments, qualify leads, handle enquiries and connect customers with your team - 24/7.
Connection
VitalPBX + VoxLink
- Connection type
- SIP
- Routing
- Selected call flows
- Direction
- Inbound + outbound
- Validation
- Tested before go-live
Keep your phone system. Keep your numbers. Add AI to the conversations you choose.
Why add AI
Add AI to a Compatible VitalPBX / PJSIP Environment
The VitalPBX model is deliberately conservative: a dedicated compatible SIP/PJSIP endpoint or trunk is configured, VoxLink authenticates against it, and your dial plan decides when to send a call that way. Everything upstream of that decision - inbound routes, contexts, time conditions, queues - is untouched.
Because endpoint technology and Asterisk version differ between deployments, the exact architecture is confirmed against your system rather than presumed. Some environments suit an extension-style endpoint; others suit a trunk. Both keep PBX control where it already sits.
Endpoint technology confirmed, not assumed
VitalPBX and Asterisk versions and PJSIP configuration are reviewed so the endpoint or trunk matches your actual design.
Security and NAT handled explicitly
Strong authentication and correct network/NAT handling are part of the setup, and no server addresses or credentials are ever published.
What VoxLink adds
What You Can Automate With VitalPBX
AI as a dial-plan destination
Send any route you choose to the AI endpoint and keep the rest of the dial plan unchanged.
After-hours and holiday cover
Use existing time conditions to reach the AI instead of voicemail outside working hours.
Overflow from queues
Where a queue fails over, that destination can be the AI endpoint rather than a dead end.
Enquiry handling
Answer common questions from your configured knowledge base without occupying an agent.
Return transfer into the PBX
Hand callers back to a context, extension or queue where transfer routing is configured and tested.
Outbound over permitted routes
Approved reminders and follow-ups where outbound route permissions allow the workflow.
In practice
Example Call Flow
The customer-facing view of a VitalPBX route that ends at the AI endpoint.
- 01
A customer calls a number terminating on your existing trunk.
- 02
VitalPBX applies your inbound route and dial-plan logic as usual.
- 03
The selected condition sends the call to the dedicated AI endpoint.
- 04
VoxLink answers, handles the conversation and records the outcome.
- 05
The call ends, or transfers back into your PBX where that routing is configured.
CallerAre you open today? I need to arrange a service visit.
VoxLink AIThe office is closed over the holiday period, but I can arrange the visit request now. What's the address?
CallerIt's the same site you attended last month.
VoxLink AIUnderstood - I'll note that and your contact number, and the service team will confirm a time when they return.
Outcome: request logged during closure, no missed work and no voicemail backlog.
Positioning
Keep VitalPBX. Add AI.
Use a dedicated compatible SIP/PJSIP endpoint or trunk configuration so VoxLink can become part of your existing VitalPBX call flow.
You keep the self-hosted control and cost model you chose VitalPBX for. VoxLink is priced on its own usage, independent of your PBX.
See VoxLink pricing and plans →Your VitalPBX dial plan, contexts and routing logic.
Your existing trunks, numbers and carrier arrangements.
Your extensions, queues and internal call handling.
Full control over which conditions send a call to the AI endpoint.
Use cases
VitalPBX Use Cases
Typical patterns in a compatible PJSIP environment.
- Use a PJSIP extension-style endpoint as an AI destination in your dial plan.
- Route selected inbound routes or DIDs to the AI while the rest are unchanged.
- Send after-hours and holiday conditions to AI instead of voicemail.
- Use the AI endpoint as a queue overflow or failover destination.
- Transfer callers back into a context, extension or queue once details are captured.
- Run approved outbound workflows where outbound route permissions allow.
Technical model
How the Connection Works
VoxLink requires a SIP server address and matching authentication details. Configure a dedicated compatible SIP/PJSIP connection in VitalPBX, then route selected inbound calls to the AI and permit outbound routing where required.
Existing Number
VitalPBX
SIP/PJSIP Connection
VoxLink AI Agent
Customer / Team
The configuration always follows your actual PJSIP/SIP design. Nothing is hard-coded, and no server addresses or credentials are published.
Requirements
What You'll Need
For whoever maintains your VitalPBX. Server addresses, endpoint names and secrets are exchanged privately, never displayed.
- Administrative access to your VitalPBX system.
- Your VitalPBX and Asterisk version and the endpoint technology in use.
- The ability to create a dedicated compatible SIP/PJSIP endpoint or trunk.
- Strong authentication and correct NAT/network handling for that endpoint.
- Agreement on which inbound routes or dial-plan conditions send calls to the AI.
- Outbound route permissions if outbound AI workflows are in scope.
- A VoxLink account and an authorised administrator for validation testing.
Setup
Connecting VitalPBX
Our team works through this with you. No configuration details, credentials or server addresses are ever published.
- 1
Confirm the VitalPBX and Asterisk version and endpoint technology.
- 2
Create a dedicated compatible SIP/PJSIP endpoint or trunk.
- 3
Set strong authentication and correct network/NAT handling.
- 4
Enter the matching SIP server and credential details in VoxLink.
- 5
Route selected inbound calls.
- 6
Configure outbound route permissions.
- 7
Test registration, audio, DTMF, transfers and caller ID.
Before go-live
Every Connection Is Tested First
Compatibility and call quality are confirmed on your environment before customers reach the AI.
- SIP registration or trunk connectivity
- Inbound and outbound audio in both directions
- DTMF handling
- Transfers back to your team
- Caller ID presentation
- Firewall and NAT behaviour
- Failover when the AI path is unavailable
Use it with
What to Set Up After Connecting VitalPBX
Other phone systems
Connect a Different System
Not sure what you have?
Send us your phone system details and we'll confirm whether a supported SIP connection is available.
Request a compatibility check →FAQ
VitalPBX Questions
Your VitalPBX. Now With AI Voice Automation.
Connect VoxLink to your compatible VitalPBX environment and automate inbound and outbound customer conversations.