> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/connecting-your-sip-trunk.md).

# Connecting your telephony (SIP trunk) to Dapta

Use this guide to choose how your Voice Agent should make and receive phone calls. Dapta supports a managed path where Dapta provisions the phone number for you, and bring-your-own paths where your company keeps its existing Twilio account, SIP carrier, PBX, or contact center.

***

## Choose your connection path

**Step 1:** Decide who should manage the phone number and carrier connection.

If you want the simplest setup, choose a **Dapta-managed number**. If your company already has Twilio, another carrier, a PBX, a contact center, or SIP routing that must stay in place, choose **bring your own SIP trunk**.

***

**Step 2:** Choose **Dapta-managed number** if you want Dapta to handle the carrier setup for you.

This is the default self-serve path. You buy a phone number inside Dapta, assign it to a Voice Agent, and Dapta provisions the telephony behind the scenes. You do not need to configure anything in Twilio or another carrier.

{% content-ref url="/pages/lOn5ZSMh2lswJ2DrpMhm" %}
[Connect a Dapta-managed number](/ai-voice-agents/connecting-your-sip-trunk/connect-a-dapta-managed-number.md)
{% endcontent-ref %}

You can also review the existing phone number purchase guide:

{% content-ref url="/pages/we5zspVTGdlh8PjAmZVe" %}
[Buying Phone Numbers through Dapta](/ai-voice-agents/buying-phone-numbers-through-dapta.md)
{% endcontent-ref %}

***

**Step 3:** Choose **Bring your own Twilio SIP trunk** if your company owns the Twilio account or phone numbers.

Use this path when Twilio is your carrier. Your telephony admin configures Twilio Elastic SIP Trunking, Dapta connects to that trunk, and your Voice Agents can use your Twilio routing for inbound calls, outbound calls, or both.

{% content-ref url="/pages/yqW1PzIwjbcUeE6a1XFU" %}
[Connect your own SIP trunk (custom / BYO)](/ai-voice-agents/connecting-your-sip-trunk/connect-your-own-sip-trunk-custom-byo.md)
{% endcontent-ref %}

***

**Step 4:** Choose **Bring your own SIP trunk** if Dapta needs to use another existing telephony provider.

Use this path when your carrier, PBX, compliance process, caller ID, billing, or routing must stay under your control. Your telephony admin provides the SIP credentials, Dapta connects to that trunk, and your Voice Agents can use it for inbound and outbound calls.

{% content-ref url="/pages/yqW1PzIwjbcUeE6a1XFU" %}
[Connect your own SIP trunk (custom / BYO)](/ai-voice-agents/connecting-your-sip-trunk/connect-your-own-sip-trunk-custom-byo.md)
{% endcontent-ref %}

***

**Step 5:** Choose **enterprise custom telephony** when the setup needs guided implementation.

Large companies often need fixed signaling, custom header handling, routing policy, multiple trunks, human queue transfers, or more concurrent channels. Dapta Success and Support can guide this setup.

{% content-ref url="/pages/yq0L9f5Vq1iFRZOVZpm0" %}
[Custom telephony for enterprise and large companies](/ai-voice-agents/connecting-your-sip-trunk/custom-telephony-for-enterprise-large-companies.md)
{% endcontent-ref %}

***

## Which path should I use?

| If you need...                                                                             | Use this path                                 |
| ------------------------------------------------------------------------------------------ | --------------------------------------------- |
| A fast setup with a number purchased in Dapta                                              | **Dapta-managed number**                      |
| No carrier, Twilio, or PBX configuration                                                   | **Dapta-managed number**                      |
| Your company already uses Twilio and wants to keep its Twilio account or phone numbers     | **Bring your own SIP trunk - Twilio example** |
| Dapta to use your existing carrier, PBX, or contact center                                 | **Bring your own SIP trunk**                  |
| Your own caller ID and telephony routing rules                                             | **Bring your own SIP trunk**                  |
| Dedicated routing, SIP proxy support, warm transfer to human queues, or higher concurrency | **Enterprise custom telephony**               |

{% hint style="info" %}
If you are not sure which path applies, start with **Dapta-managed number** unless your telephony or compliance team has already told you that calls must go through your own Twilio account, carrier, PBX, or contact center.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/ai-voice-agents/connecting-your-sip-trunk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.