BYO SIP trunking for voice AI: prerequisites and acceptance

A SIP trunk connects a telephone carrier with a voice service. Bringing your own trunk can preserve an existing carrier relationship, but it does not make an arbitrary carrier configuration compatible automatically. Numbers, authentication, routing and media behavior must all agree.

For the current runtime concepts, see LiveKit telephony. Carrier-specific instructions remain separate: Twilio Elastic SIP Trunking and Telnyx SIP Trunking describe their own configurations.

Understand the two directions

Inbound calls need a route from the purchased or ported number to the receiving voice service and then to the correct assistant. Outbound calls need an allowed destination, the correct carrier route and a permitted caller identity.

A working inbound path does not prove outbound calling, and the reverse is also true. A browser call exercises neither telephone route.

Gather the required information

Use the exact values supplied by your platform and carrier. Do not paste example domains, guessed ports or a generic webhook URL into production routing. Keep secrets in supported settings, not in assistant instructions.

In Burki

Burki's current voice path uses LiveKit media and SIP. Carrier-specific readiness determines whether a selected telephone configuration may run. A carrier integration or saved account does not imply that every SIP feature has passed acceptance.

Treat managed telephone setup and BYO setup as different account arrangements. Confirm the applicable route and current availability before purchasing or porting a number. Start with the relevant integration guide and the assistant's readiness information.

Test before routing customers

Use a destination you own or are authorized to call. Verify inbound and outbound separately where both are required. Confirm the expected assistant answers, both parties hear each other, caller corrections work, and hangup releases the call.

For handoff, test an answered destination, rejection and timeout. Inspect whether the caller can recover when the destination is unavailable. Reconcile all telephone legs and provider usage afterward.

Keep rollback and ownership clear

Preserve the previous route until the new path is accepted. Document which system handles callbacks and which account pays for telephone usage. If a number is paused, restricted or incorrectly routed, changing the language model will not repair the carrier path.

BYO can provide operational control, but it also creates responsibilities. Read BYO mode explained and the carrier cost guide before assuming that a direct trunk will reduce either effort or expense.