Connecting your telephony (SIP trunk) to Dapta

Choose how a Voice Agent makes and receives calls: a Dapta-managed number, your own Twilio trunk, another SIP provider, or a guided enterprise setup.

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.

Connect a Dapta-managed number

You can also review the existing phone number purchase guide:

Buying Phone Numbers through Dapta

---

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.

Connect your own SIP trunk (custom / BYO)

---

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.

Connect your own SIP trunk (custom / BYO)

---

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.

Custom telephony for enterprise and large companies

---

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

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.