Platform · BYOC
Bring your own carrier. Keep your rates, contracts, and numbers.
Most voice AI platforms treat SIP trunking as an enterprise upsell or a grudging workaround. Rayvoc treats it as a first-class feature: point your trunk at us, attach an agent, and pay no SIP surcharge — ever.
Why teams keep their carrier
If you already run telecom at any scale, your carrier relationship is an asset. Negotiated per-minute rates that took years to get. Contract commitments you can’t walk away from. A number inventory that took months of regulatory paperwork to build — and in some countries, numbers that legally cannot move to a foreign platform. Compliance teams that have already vetted the carrier.
“Rip out your telecom and buy our minutes” is not a reasonable ask for these teams. BYOC — bring your own carrier — lets you keep all of it and add the AI layer on top: your carrier delivers calls to Rayvoc over a SIP trunk, and Rayvoc runs the agent. We wrote a longer treatment in the BYOC voice AI guide.
How BYOC works on Rayvoc
You create a trunk in the dashboard, authenticate it by IP allowlist or SIP registration, and point your carrier or SBC at the trunk’s SIP URI. Inbound calls on the trunk route to the agent you choose; outbound calls from agents egress through your carrier with the caller ID you configure. Media is negotiated over standard codecs — G.711 and Opus — so any standards-compliant carrier, telco, or enterprise PBX works without custom integration.
{
"trunk": {
"name": "acme-primary",
"direction": "bidirectional",
"auth": {
"mode": "ip_acl",
"allowed_ips": ["203.0.113.10", "203.0.113.11"]
},
"codecs": ["opus", "g711u"],
"inbound": { "agent": "support-tier1" },
"outbound": { "caller_id": "+14155550142" }
}
}Because Rayvoc’s media layer is co-located with inference, your trunk terminates as close to the models as physically possible — no relay through a separate carrier API on every call event. That is the same architecture that keeps native calls fast; read how the latency budget works. Every BYOC call still gets the full platform: transcripts, recordings, tool calling, and per-stage latency waterfalls.
First-class, not an afterthought
The competitive landscape is telling. Bland builds exclusively on Twilio, so “your carrier” means “Twilio, full stop.” Other platforms technically support SIP but gate it behind enterprise sales calls, charge a per-minute SIP surcharge that quietly erases your negotiated carrier rates, or document it so thinly that every deployment becomes a support ticket. BYOC on those platforms exists to check a box on an RFP.
On Rayvoc, BYOC is self-serve from day one, surcharge-free, and treated as a peer of our native telephony — because we run a real telecom stack either way. You can run both side by side: BYOC trunks for the markets where your carrier relationship matters, Rayvoc DIDs in 100+ countries for everywhere else, mixed freely on one account. And since the AI layer is equally open — bring your own LLM, TTS, and STT — you are never locked to our choices on either side of the call.
Running outbound campaigns over your own trunk works the same way, with the platform’s consent-list enforcement, calling windows, and warm transfer available regardless of who carries the call.
Frequently asked questions
What does BYOC mean in voice AI?
BYOC — bring your own carrier — means connecting your existing telecom provider to a voice AI platform over a SIP trunk, instead of buying minutes and numbers through the platform. You keep your negotiated rates, your contracts, and your number inventory, and the platform handles the AI layer. See the glossary entry for a fuller definition.
Does Rayvoc charge extra for BYOC?
No. There is no SIP surcharge and no per-minute penalty for using your own carrier. BYOC traffic is billed at the same platform rates as any other call — your carrier bills you for the telecom leg directly, at your rates. Details on the pricing page.
Which carriers and PBXs work with Rayvoc BYOC?
Any provider or system that speaks standard SIP: major carriers, regional telcos, SIP trunk providers, and enterprise PBX or SBC deployments. Authentication works via IP allowlisting or SIP registration, and media is negotiated over standard codecs including G.711 and Opus.
Can I mix BYOC trunks with Rayvoc-native numbers?
Yes, on the same account and even for the same agent. A common pattern is keeping a regulated home-market number inventory on an existing carrier via BYOC while buying Rayvoc DIDs for new international markets where you have no carrier relationship.
Keep your carrier. Add the agents.
Every account starts with a 14-day free trial — 1 concurrent channel, a real phone number, and full platform access.