SIGN UP arrow-white-right LOGIN

The SIP trunk built for LiveKit Agents

Connect LiveKit Agents to local numbers in 130+ countries. Sub-20ms media latency on 80% of calls. No per-channel fees. First test call the same day you sign up. Works with LiveKit Cloud and self-hosted deployments.
Start free arrow-white-right Setup guide

A neutral telephony partner for your LiveKit stack

LiveKit gives you the agent runtime, the WebRTC media plane, and the SDKs. What it does not give you is phone numbers, carrier peering, or a global PSTN footprint. That is the layer underneath.

didlogic only sells voice infrastructure. Our own Autonomous System (AS13006), 12 physical PoPs, 240+ carrier agreements, and direct Tier 1 peering exist to carry your calls, not to compete with LiveKit. You keep the agent stack you already built. We handle the numbers and the network underneath.

That neutrality matters when you scale. Many SIP providers in the AI voice space also push their own agent platforms or LLM tooling, which puts them in conflict with the open-source stack you chose LiveKit to avoid being locked into. We do not have an agent product. We will not have one.
A neutral telephony partner for your LiveKit stack

Connect LiveKit to a didlogic number in three steps

1
Buy a DID
Buy a local or toll-free number in any of 130+ countries from the didlogic portal. Provisioned in seconds.
2
Configure the SIP trunk
Create a SIP account in didlogic, then add inbound and outbound trunks in LiveKit Cloud using your SIP credentials and nearest didlogic gateway.
3
Point the number to LiveKit
In didlogic, forward your number to your LiveKit SIP URI. Place a test call. Most teams go live the same day.
Read the full LiveKit setup guide →

What LiveKit teams get with didlogic

Global number coverage
Global number coverage
Local and toll-free DIDs in 130+ countries, with licensed local voice in 17 of them. Your LiveKit Agent answers as a local number anywhere it should sound native.
Carrier-grade media path
Carrier-grade media path
Sub-20ms added media latency on 80% of calls, measured across our 12 PoPs. Direct Tier 1 peering with PCCW, GTT, Telia Carrier, and NTT Communications keeps the audio path short. Latency you cannot afford to lose to a long PSTN hop before LiveKit even sees the audio.
LiveKit-compatible SIP
LiveKit-compatible SIP
UDP, TCP, and TLS transports. SRTP media encryption available on request. G.711 and G.722 codecs supported. Digest and ACL authentication on both inbound and outbound trunks. Wildcard inbound matching so one trunk handles your full number pool.
Inbound and outbound calls
Inbound and outbound calls
Your LiveKit Agent handles both directions. CLI rotation keeps outbound pickup rates healthy on high-volume campaigns. Custom SIP headers pass through to LiveKit participant attributes for your dispatch logic.
No per-channel fees
No per-channel fees
Pay per DID and per minute. No charges per concurrent channel, no seat licenses, no tier gates on CPS for AI-native accounts. Scale concurrency without renegotiating.
MCP server included
MCP server included
Provision numbers and configure trunks from Claude Code, Cursor, or any MCP client at mcp.didlogic.com. Useful when you are already coding LiveKit Agents and want one less portal to switch into.

Full compatibility with LiveKit SIP

LiveKit SIP requirement didlogic support
UDP, TCP, and TLS signaling transport Supported
SRTP media encryption Supported (per-number activation on request)
G.711 (PCMU/PCMA) and G.722 codecs Supported
Digest authentication on outbound trunks Supported
IP-based / ACL authentication Supported
Inbound trunks with wildcard number matching Supported via SIP URI forwarding
Outbound trunks for agent-initiated calls Supported
E.164 number format Required, enforced
Custom SIP headers passed to participant attributes Supported
DID porting to didlogic Paperless LNP in 8 countries
Get started free

The numbers that matter for AI voice

< 20ms
Added media latency on 80% of calls, measured across our 12 PoPs
99.99%
Network availability target, backed by owned infrastructure (not third-party cloud)
< 60 seconds
Median DID provisioning time from portal checkout to SIP-ready
17 countries
With licensed local voice, not just pass-through

Pay for what you use. No channel fees.

France
France
Per month
$3
Channels
20
Inbound per minute
$0.01
Switzerland
Switzerland
Per month
$2
Channels
20
Inbound per minute
$0.01
Singapore
Singapore
Per month
$5.83
Channels
2
Inbound per minute
$0.01
New Zealand
New Zealand
Per month
$3.99
Channels
10
Inbound per minute
$0.009
Register to see all countries

Deploy in the EU, UK, and APAC without regulatory friction

Data processed on regional infrastructure
didlogic routes calls through its own regional data centers. Voice traffic stays on domestic infrastructure where required, keeping call handling aligned with local data processing laws. Useful when your LiveKit deployment region needs to match the call origin region.
Domestic PSTN handover, every time
Direct connectivity to 80% of Tier 1 carriers and national operators worldwide. Calls always hand over to the recipient's local mobile network, not through foreign gateways.
Local calls recognized as local
EU and APAC DIDs are activated on domestic mobile networks. Outbound calls originate from in-country IPs with compliant caller IDs, so they arrive as domestic traffic rather than being flagged or blocked as foreign.
Regional experts monitoring every market
Our regional legal and telecom engineering teams track regulatory changes across the countries we serve. Call processing adjusts proactively when rules change, so your LiveKit Agents stay compliant without a ticket on your side.

What teams build on LiveKit + didlogic

AI receptionists
Route inbound PSTN calls into a LiveKit room with a single Dispatch Rule. The agent picks up on a local number in any market, with HD audio and SRTP-encrypted media.
Outbound AI sales and SDR campaigns
Local caller IDs that get answered. CLI rotation cycles your number pool to keep pickup rates healthy. Outbound trunk authentication uses your SIP credentials so multiple LiveKit projects can share or isolate trunks as you need.
Multi-party voice and human-in-the-loop
LiveKit's strength is multi-participant rooms. Bring multiple PSTN callers into the same room, or transfer the customer to a human agent when intent is high. didlogic provides the PSTN endpoints; LiveKit handles the room logic.
Voice + video deployments
Some LiveKit deployments pair voice agents with screen share or video. didlogic carries the PSTN side cleanly; LiveKit handles the rest of the modalities. Your stack does not change.
Multilingual support across regions
Pair LiveKit Agents and your TTS provider of choice with local numbers across 130+ countries. One centralized agent deployment, native-language coverage in every market.

Our clients

FAQ: SIP trunk for LiveKit Agents

Does didlogic work with LiveKit Cloud?

Yes. didlogic’s SIP trunks meet every requirement in LiveKit’s SIP integration, including TLS transport, SRTP encryption, G.711 and G.722 codecs, and digest and ACL authentication. You can connect a didlogic number to a LiveKit Agent in about 10 minutes.

Does didlogic work with self-hosted LiveKit?

Yes. Self-hosted LiveKit deployments running the LiveKit SIP service connect to didlogic exactly the same way as LiveKit Cloud. IP-based authentication is available if you prefer to allowlist your LiveKit cluster against our PoPs.

Is didlogic listed as an official SIP provider in LiveKit's docs?

LiveKit’s docs name a handful of SIP providers by example. The platform supports any provider that implements standard SIP correctly, and many teams are running production LiveKit traffic on didlogic today.

How does didlogic compare to Twilio for LiveKit?

Two main differences. First, no per-channel fees, so you pay only for numbers and minutes. Second, deeper global DID coverage with licensed local voice in 17 countries, versus Twilio’s smaller direct-coverage footprint. For a feature breakdown, see our Twilio alternative for AI voice page.

How does didlogic compare to Telnyx for LiveKit?

Telnyx is also pushing its own AI voice platform, which competes with the open-source LiveKit stack you chose for flexibility. didlogic does not sell an AI voice product. We only provide the telephony layer, so there is no conflict with your LiveKit stack.

Does LiveKit on didlogic support outbound calls?

Yes. LiveKit’s SIP integration supports both inbound and outbound calls. didlogic supports both directions on the same SIP account. You configure one outbound trunk in LiveKit pointed at your nearest didlogic regional gateway.

What audio codecs does LiveKit support on SIP trunks through didlogic?

LiveKit’s SIP service supports standard PSTN codecs. didlogic supports G.711 (PCMU/PCMA) and G.722 wideband. Codec selection happens during SIP negotiation; you do not need to configure it manually.

What latency should I expect on a LiveKit call through didlogic?

80% of calls routed on regional paths complete with under 20ms added media latency. Your end-to-end conversation latency also depends on LiveKit’s routing, your STT and TTS providers, and your LLM inference time, which sit above the voice transport layer.

Can I use one didlogic SIP account across multiple LiveKit projects?

Yes. A single didlogic SIP account can be used by multiple LiveKit outbound trunks. For inbound, each didlogic number forwards to the LiveKit FQDN of the project that should receive it, so you can route different numbers to different projects without sharing routing logic.

Does didlogic support SRTP for LiveKit?

Yes. SRTP media encryption is available and is enabled per number on request. Email [email protected] with the list of numbers you want encrypted.

Can I port my existing phone number to didlogic for use with LiveKit?

Yes. didlogic supports paperless LNP in 8 countries and manual porting in most others. Porting a number does not require downtime.

How long does setup take?

Most teams place a first test call within a few hours of signing up. Production rollout typically takes a few days depending on your markets. Regulated markets may require additional compliance verification.

Is there a free trial?

New accounts get free credits to start testing, with no payment required to sign up. You can provision a DID and connect it to LiveKit during the trial.

Where do I find setup documentation?

The LiveKit integration guide lives at docs.didlogic.com/docs/guides/bring-your-own-bot-byob/livekit. Our engineering team is reachable at [email protected] and active in relevant Discord and Slack communities during integration windows.

Get started free

Ship your LiveKit agent on production telephony this week