SIP Trunk Setup
Connecting your own carrier, and what the platform needs from it.
Neo Dialer is built around bring your own trunk. You hold the carrier relationship, you keep the rates you negotiated, and your numbers stay with your carrier — so moving dialers later does not mean renumbering.
What this means in practice
- We charge for the dialer. Your carrier bills you for minutes, at your rate.
- Any carrier speaking standard SIP works. Telnyx, Twilio, Bandwidth, Vonage,
SignalWire and Plivo are all in use; there is no allowlist.
- Platform-provided trunks exist as an alternative if you would rather not run
your own carrier relationship. Those are billed separately.
What you need before you start
| Requirement | Notes |
|---|---|
| SIP host | The carrier's SIP server hostname or IP |
| Authentication | Registration credentials, or an IP-authenticated setup |
| Outbound caller ID | At least one number you are authorised to present |
| Carrier-side allowlist | If your carrier authenticates by IP, it needs ours |
For IP authentication, ask us for the current media server addresses to allowlist rather than guessing — the platform can run across more than one media server.
Adding a trunk
Admin → Telephony → SIP Trunks → Add trunk.
- Enter the host and authentication details
- Save — the trunk is written into Asterisk through PJSIP realtime immediately
- Wait a few seconds and confirm registration shows as up
Trunks are provisioned per media server. If your deployment has more than one, the trunk endpoint is created on each enabled server, and outbound calls resolve to the endpoint on whichever server is handling the call.
Do not re-save a trunk from an environment that does not own it. Saving a platform-level trunk fans provisioning out to every enabled media server. If you have separate production and staging platforms sharing a registry, saving from the wrong one will rewrite the other's configuration.
Multiple trunks
A tenant can hold several trunks at once. Common reasons:
- A separate trunk per region or per carrier, for rate reasons
- A failover trunk
- A dedicated trunk for a specific campaign
Campaigns select the trunk they use, so you can route different outreach through different carriers without changing anything else.
Inbound
Adding a trunk does not by itself route inbound calls. You also need to add the number under Admin → Telephony → Phone Numbers and build a route for it. See Inbound Routing.
Provider notes
Telnyx
Create a SIP connection in the Telnyx portal, choose either credential or IP authentication, and set the connection's outbound voice profile. Take the SIP host from the connection and enter it in Neo Dialer. If you use IP authentication, add our media server addresses to the connection's allowlist.
Twilio
Create an Elastic SIP Trunk, add a termination URI, and either create credential-list credentials or add our addresses to the trunk's IP access control list. Use the termination URI as the SIP host.
Anything else
Any carrier that supports standard SIP registration or IP authentication will work. If you get stuck on a specific provider, contact us with the details from their portal and we will help you map them across.
Something here wrong or missing? Tell us — these pages describe the platform as it actually behaves, so a mismatch is a bug we want to know about.