Bring your own carrier for AI voice agents

Bring Your Own Carrier is a setup where the AI voice platform and the phone network underneath come from two different vendors. Instead of using the telephony bundled into Vapi, Retell, ElevenLabs or LiveKit, you connect the platform to your own SIP trunk and your own numbers. The usual reasons are per-minute cost, owning the numbers, and reaching countries the bundled inventory does not cover.

SIP trunking is the technology: a SIP connection between two systems that carries calls. BYOC is a deployment choice that uses it. When you bring your own carrier to a voice AI platform, what you are configuring is a SIP trunk between that platform and your carrier. didlogic provides the SIP trunk, which is what makes the BYOC setup work.

Twilio’s Bring Your Own Carrier feature lets you send voice calls from a Twilio number out over a third-party carrier instead of Twilio’s own voice network, using a termination SIP URI. Teams typically keep Twilio for messaging or for numbers they cannot move yet, and shift the voice minutes elsewhere. If you are weighing a fuller move, the Twilio alternative page covers the comparison properly.

On production volume, usually. The saving comes from the per-minute rate, because bundled telephony is resold with a margin on top. Be clear about what does not change: your platform still charges its own per-minute or per-session fee, and BYOC does not touch that. The break-even sits somewhere between test traffic and first real production load, and it moves depending on which countries you call.

Not as a line item on outbound. Concurrency is gated by account level instead: 5 channels on Core, 50 on Plus, and no limit on Premium and above. Raising the limit past the standard threshold requires 2FA and IP restrictions on your SIP accounts, and CPS increases are available on Premium and above once those are in place. Inbound channel increases on a specific number are quoted case by case, because they depend on the country and number type.

Numbers are a monthly rental plus a per-minute rate on the calls they receive, starting from $2.00 a month with inbound from $0.01 a minute. Outbound minutes are billed separately at voice rates by destination. Account levels carry a monthly commitment, which is a minimum spend rather than an extra fee: if usage does not reach it, the difference is charged. See phone number pricing, call rates and account levels.

Promo and Core accounts are billed per minute on outbound. Higher account levels get per-second billing. Certain countries apply fixed increments at any level because their telecom regulations require it. For agent calls, which are often well under two minutes, this is worth checking before you model your costs.

Vapi, Retell, ElevenLabs Conversational AI and LiveKit have step-by-step guides in our documentation. Beyond those, anything that speaks standard SIP will connect: UDP, TCP or TLS signalling, G.711 or G.729 codecs, SIP REFER for transfers, and either username and password or IP authentication.

No, but you should be comfortable following a technical guide. It is two configuration steps: create a SIP account on didlogic, then point your platform at it. Per-platform guides cover the specifics, and a voice engineer can join your first deployment on request.

Yes. Contact support and we will create a dedicated SIP account with IP authentication. Some platforms run their SIP signalling from shared addresses, in which case password authentication is the simpler and safer default, so check what your platform recommends before switching.

G.711 u-law (PCMU), G.711 a-law (PCMA), G.729 and GSM. You can force a specific codec on your side and our SBC will comply where possible. G.722 wideband is supported, but availability is limited and many carriers do not preserve wideband end to end, so design for G.711 quality. DTMF works in-band and as RFC 2833 / RFC 4733 RTP events.

Allow RTP audio on ports 10000 to 20000 from any IP. Our media addresses are numerous and change, so allowlisting them individually will break. For signalling, allow our gateways by DNS name rather than by static IP. If your security policy will not permit inbound RTP from any address, email [email protected] and we will provide a specific list to allowlist.

Yes, through SIP REFER, but it is disabled by default and has to be enabled on your account, so ask before you build against it. Once on, inbound calls can only be referred to another number purchased on your own didlogic account. Outbound transfers go to PSTN numbers. A failed transfer drops the call rather than returning it to the original party, so build a fallback path.

No. Visible inventory is filtered to what your account is cleared to buy directly, and some countries are restricted until verification is complete. Numbers outside that view are still available through the provisioning team, including bulk orders and number types that are not sold self-service. If the country you need is not showing, ask rather than assuming we do not have it.

Yes. Paperless porting in eight countries and porting in 60+ more, scheduled so the number stays live throughout. Porting is available on Business and Wholesale level accounts. Porting numbers to didlogic while keeping your existing vendor for SMS or other rails is a common pattern, and no AI platform’s BYO setup cares which carrier owns the number.

On calls that stay on a regional path, 80% add under 20 ms. End-to-end conversational latency is dominated by your STT, LLM and TTS providers, which sit well above the transport layer. Choosing the gateway closest to your traffic is the part of the budget you control at the carrier layer.

Yes. New accounts include free test credit and no card is needed to sign up. Two things to keep in mind: your account level carries a monthly commitment once it is active, and some individual numbers carry a minimum service term that is shown before purchase. Neither blocks testing, but both are worth reading before you buy numbers in a dozen countries.