An extension, not a re-architecture
Where the deployment supports remote SIP registration, the AI behaves like a familiar extension destination inside your existing P-Series routing.
YEASTAR + VOXLINK
Bring AI Voice Agents to Your Yeastar Phone System
Your Yeastar P-Series PBX already carries your extensions, users, inbound routes and time conditions.
Rebuilding a working call flow is the reason most teams never add automation at all - the risk of breaking what already routes correctly outweighs the missed calls.
In a compatible P-Series deployment, VoxLink can be reached like any other SIP extension, so selected inbound routes, after-hours destinations or overflow paths can point at AI using the routing model your PBX already uses.
No extension renumbering, no new numbers and no rebuilt dial plan. The existing call flow stays intact and one destination changes.
Answer calls, book appointments, qualify leads, handle enquiries and connect customers with your team - 24/7.
Connection
Yeastar + 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 Without Rebuilding Your Yeastar Call Flow
The advantage of the Yeastar model is that nothing conceptually new is introduced. A dedicated SIP extension is created in a compatible P-Series system, VoxLink registers to it, and from the PBX's point of view the AI is simply another destination that can be selected in an inbound route, time condition or queue.
That means your existing extensions, users and numbers stay untouched. You are not migrating a call flow - you are adding one destination to it, and you can point as little or as much traffic at that destination as you want.
Time conditions still decide
Your existing business-hours and holiday logic continues to control when calls reach people and when they reach AI.
Security policy comes first
Remote registration is security-sensitive, so transport, IP restrictions and firewall/NAT behaviour are confirmed before the extension is used.
What VoxLink adds
What You Can Automate With Yeastar
After-hours destination
Point the out-of-hours branch of a time condition at the AI extension instead of voicemail.
Queue and overflow handling
Where a queue is configured to overflow or fail over, that destination can be the AI extension.
Reception-style answering
Answer, identify the reason for the call and route it, without occupying a staffed extension.
Appointment booking
Capture and confirm bookings during the call rather than logging a callback request.
Transfer into your Yeastar environment
Hand qualified callers to the right extension or ring group where transfer routing is configured.
Outbound over the same SIP path
Reminders and approved follow-ups where the extension's outbound permissions and routes allow the workflow.
In practice
Example Call Flow
How a Yeastar inbound route reaches the AI extension, described without any configuration detail.
- 01
A customer calls a number that already terminates on your Yeastar PBX.
- 02
The existing inbound route and time condition are applied as usual.
- 03
The selected branch sends the call to the dedicated AI extension.
- 04
VoxLink answers, handles the enquiry and captures the details.
- 05
The call ends, or transfers back to an extension or ring group in your Yeastar environment.
CallerI've been holding a while - I just need to check on an order.
VoxLink AII can help with that now rather than keeping you waiting. Do you have the order reference?
CallerYes, it's on the confirmation email.
VoxLink AIThanks - I've noted the details and the status question. If you'd prefer a person, I can put you through to the team as soon as someone is free.
Outcome: the caller is handled instead of abandoning the queue, with a transfer path still open.
Positioning
Keep Your Yeastar. Add AI.
Create a dedicated SIP extension in a compatible Yeastar P-Series system and connect it to VoxLink so AI can become part of your existing call flow.
Your Yeastar licensing and carrier costs are unchanged. VoxLink is priced on its own usage, so you can start with one route and scale from there.
See VoxLink pricing and plans →Your existing Yeastar extensions, users and desk phones.
Your current numbers, trunks and carrier arrangements, where routing permits.
Your inbound routes, time conditions, queues and IVR structure.
Full control of which branch of the call flow reaches the AI extension.
Use cases
Yeastar Use Cases
Typical starting points in a compatible P-Series environment.
- Send selected P-Series inbound routes to a compatible AI extension.
- Use the AI extension as the after-hours destination on an existing time condition.
- Route queue overflow or no-answer paths to AI instead of voicemail.
- Transfer qualified callers back into your Yeastar environment once details are captured.
- Give one department or number an AI-first path while the rest of the PBX is unchanged.
- Run approved outbound reminders over the same authenticated SIP path where permissions allow.
Technical model
How the Connection Works
The PBX-extension model uses a dedicated SIP extension. Matching extension credentials and the PBX server information are configured in VoxLink. Selected calls can then be routed to the AI endpoint; outbound calling can use the same authenticated SIP path when routing and permissions allow.
Existing Number
Yeastar P-Series
SIP Extension
VoxLink AI Agent
Customer / Team
Remote SIP registration is security-sensitive. We confirm remote access policy, IP restrictions, transport, firewall/NAT behaviour and extension outbound permissions as part of the setup.
Requirements
What You'll Need
For your Yeastar administrator. Registration names, passwords and PBX addresses are exchanged privately and never published here.
- Administrative access to your Yeastar PBX.
- A compatible P-Series deployment where remote SIP registration is permitted by policy.
- The ability to create a dedicated SIP extension for VoxLink.
- Agreement on the inbound routes, time conditions or queue destinations that should reach that extension.
- Appropriate network, firewall, NAT and transport configuration for SIP.
- Outbound route permissions for the extension if outbound AI workflows are in scope.
- A VoxLink account and an authorised phone-system administrator for validation testing.
Setup
Connecting Yeastar
Our team works through this with you. No configuration details, credentials or server addresses are ever published.
- 1
Create a dedicated SIP extension in Yeastar.
- 2
Gather the PBX address or domain, SIP port and transport, extension number, registration name and registration password.
- 3
Confirm the remote SIP registration and security policy permits the connection.
- 4
Enter the matching SIP details in VoxLink.
- 5
Route selected inbound calls to the AI extension.
- 6
Configure outbound permissions and routes if required.
- 7
Test registration, audio, transfers, DTMF, caller ID and failover.
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 Yeastar
AI Receptionist for reception-style answeringAI Customer Support for service enquiriesAI Outbound Calling for reminders and follow-upsCall Transfer for handover to an extensionKnowledge Base for approved answers
Industries
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
Yeastar Questions
Make Your Yeastar Phone System AI-Ready.
Connect VoxLink to your compatible Yeastar environment and automate more customer conversations without replacing your existing phone system.