Telnyx voice integration: connect the carrier and verify the call
A Telnyx setup guide focused on account readiness, numbers, LiveKit SIP routing, telephone acceptance and recurring costs.
Table of Contents▼
Telnyx supplies telephone connectivity; the assistant runtime supplies the conversation. A valid Telnyx account or rented number does not by itself connect callers to the right assistant. Account eligibility, number routing, SIP configuration and the selected application's readiness must all be verified.
For carrier concepts and configuration, start with the official Telnyx SIP Trunking guide. Burki's current voice path uses LiveKit rather than its retired custom audio pipeline.
Establish the account and number state
Confirm that the account can use the required countries, number types and call direction. Check whether the number is active, paused, pending verification or routed elsewhere. Record who owns the resource and who pays its recurring rental.
If a number is paused or the account is restricted, changing the LLM or speech provider will not restore the telephone route. Resolve the carrier state before investigating conversation behavior.
Configure the intended route
| Direction | What must be correct |
|---|---|
| Inbound | Number connection, receiving SIP route and assistant dispatch |
| Outbound | Allowed destination, outbound route and permitted caller ID |
| Transfer | Destination behavior, caller continuity and billing for every leg |
Use the exact configuration supplied by Burki and the carrier. Do not reuse a historical media-stream webhook or assume a generic API URL is a SIP destination. Never paste SIP secrets into assistant instructions or publicly shared troubleshooting material.
Burki's Telnyx path and other carriers have separate readiness requirements. A successful Telnyx call does not establish equivalent acceptance for Twilio or Vonage.
Run a bounded acceptance call
Use a number you control or a destination whose owner has authorized the test. Verify that the expected assistant answers, both directions of audio work, a caller correction is preserved, and hangup clears the resources.
Test inbound and outbound separately if both are required. For transfers, include an answered destination and an unavailable destination. Inspect what the original caller hears and whether recovery works; a provider status alone does not prove that experience.
Review the expense afterward
Reconcile the application call with carrier legs and settled provider usage. Include number rental even in a month without calls. Keep a small inventory of numbers, routing purpose and owner so unused resources can be identified deliberately.
Cancel only after checking dependencies such as forwarding, fallback routes and ongoing migration. A number with no recent completed calls may still serve an intentional route.
Move into real use gradually
Keep the previous route available until the new path is accepted. Monitor early calls for routing failures separately from instruction or integration failures so the correct layer gets fixed.
See BYO SIP prerequisites, the Telnyx integration page, and current pricing for the applicable setup and commercial context. This guide does not claim universal Telnyx feature support or a fixed percentage saving over another carrier.
Ready to try Burki?
Create an assistant and check your available browser practice allowance.
Create your assistantTrial eligibility and available practice are shown in your workspace.