Bring your carrier
SIP trunking: keep your numbers
Connect your carrier via SIP trunk or LiveKit BYO telephony — keep every number, respect your dial plan, and run the same VoiceForge agent spec globally.
Bring your own carrier
Connect Twilio, Telnyx, Plivo or any SIP provider as a trunk. Keep existing DIDs, preserve caller ID reputation, and avoid porting risk — the agent spec is carrier-agnostic.
LiveKit BYO telephony
VoiceForge runs on LiveKit. Plug your SIP trunk into LiveKit, and calls route to the same AI pipeline (Azure or OpenAI Realtime) with no spec change.
Global routing & compliance
Route by country, keep data in region, and apply compliance gates (consent, recording disclosure) per trunk — HIPAA-aware logging per workspace.
No port, no lock-in
No number port required. Test one number on VoiceForge, keep the rest on your carrier, and migrate gradually — extensions and hunt groups carry over.
Cost control at scale
Use your negotiated per-minute rates, keep flat VoiceForge plans for the agent, and see telephony vs AI cost separated — predictable margin for agencies at scale.
Frequently asked questions
- Do I have to port my numbers to use VoiceForge?
- No. SIP trunking keeps numbers on your carrier. Route calls via trunk to VoiceForge — no port, no downtime, no caller ID change.
- Which SIP providers are supported?
- Any SIP-compliant provider: Twilio Elastic SIP, Telnyx, Plivo, Vonage and more via LiveKit SIP. If it speaks SIP, it connects.
- How does SIP trunking compare to Vapi telephony?
- Vapi bundles telephony or requires per-provider setup. VoiceForge is BYO-first: same agent spec runs on your trunk, VoiceForge numbers, or hybrid — no rewrite.