didlogic is now a documented SIP provider in the LiveKit telephony docs

We are pleased to announce that didlogic is now included in LiveKit’s official telephony documentation.

The new quickstart, Create and configure a didlogic SIP trunk, takes developers through inbound and outbound call setup step by step. It joins LiveKit’s provider-specific quickstarts alongside Twilio, Telnyx, Plivo, Wavix and Sinch.

For teams building voice AI on LiveKit, this means the path from a didlogic phone number to a running agent is now documented on both sides of the connection.

What the integration enables

LiveKit provides the real-time media infrastructure and the agent framework. didlogic provides the carrier connectivity that carries each call to and from the public telephone network.

Together they cover a complete production voice path:

Inbound calls to a didlogic number, routed into a LiveKit room and answered by your agent
Outbound calls placed by LiveKit through the didlogic network, with your purchased number as the caller ID
Global reach through didlogic numbers in 130+ countries and A-Z termination

Because the setup is now written into LiveKit’s own documentation, teams can move from account creation to a working call path without reverse-engineering the configuration.

How the setup works

The quickstart covers both call directions and takes only a few steps in each console.

Inbound calls

Inbound routing begins in the didlogic portal. Under Numbers → Purchased, you edit the number you want to connect, set Forward to as SIP URI, and enter the destination in the format +[number]@[LiveKit SIP endpoint];transport=tcp. If the number has several destinations configured, the LiveKit destination should sit at the top of the list.

On the LiveKit side, you create an inbound trunk with your number in E.164 format, then add a dispatch rule that determines which room incoming callers are placed into. Once an agent is running, calls to your didlogic number are answered automatically.

Outbound calls

Outbound calling is configured entirely in LiveKit Cloud. You create an outbound trunk pointed at a didlogic SIP gateway domain, for example sip.nl.didlogic.net, add your purchased number in E.164 format, and supply your SIP credentials. Calls are then placed through the CreateSIPParticipant API.

LiveKit’s guide recommends selecting the didlogic gateway closest to your region and using the gateway domain rather than an IP address, since addresses can change dynamically.

Built-in troubleshooting guidance

The quickstart also includes a troubleshooting reference covering the most common configuration questions, which should shorten the setup process considerably:

Calls failing immediately. This is typically a formatting issue. Numbers should be in full E.164 format, and the LiveKit forwarding destination should be set as the top priority on the number.

Authorization errors on outbound calls. Outbound trunks require your 5-digit didlogic SIP login rather than your account login email, together with the matching SIP account password.

603 Declined responses. This response can appear when a destination’s per-minute rate exceeds the maximum call rate configured on your account. Our support team can adjust that limit on request.

Additional diagnostics are available in the call logs within the LiveKit Cloud dashboard, and our support team is available for anything the guide does not cover.

Why teams choose didlogic for AI voice workloads

Conversational AI places different demands on a carrier than traditional VoIP. Our infrastructure is built with those requirements in mind:

Scalable calls per second. We offer flexible CPS limits designed to support large outbound campaigns and sudden inbound volume without throttling.

Native SIP REFER support. Agents can hand a live call to a human colleague as a standard signalling event, making warm and cold transfers straightforward to implement.

Regional SIP gateways. Our gateways across the United States, Europe and Asia keep the distance between the caller and your processing region as short as possible, which helps preserve the conversational pacing that voice agents depend on.

Flexible termination. Tier 1 and Tier 3 routing options allow you to match call quality and cost to the use case, whether that is customer support or high-volume outreach.

LiveKit is one of four platforms covered in our AI gateways documentation, alongside ElevenLabs, Retell and Vapi. Teams working with other platforms or in-house systems can connect to didlogic as well, provided the platform supports SIP trunking or SIP URI forwarding.

Getting started

Everything needed to connect the two platforms is now available in one place:

We are glad to see didlogic included in LiveKit’s documentation, and we look forward to supporting the voice applications our customers build on it.

Maksim Dzialendzik

Head of Marketing

Maksim Dzialendzik is a telecommunications and voice infrastructure expert and Head of Marketing at didlogic. He writes about SIP trunking, international phone numbers, global call routing, and carrier connectivity for AI voice agents.

BACK TO LIST