SIP Trunk Setup for a BYOC Dialer: Step-by-Step Walkthrough

Bringing your own carrier (BYOC) lets an outbound dialer route calls over your own SIP trunks at your negotiated rates instead of a vendor's marked-up telephony. This walkthrough is the hands-on companion to our conceptual BYOC predictive dialer guide: where that explains why and how much you save, this one is the step-by-step setup.

It's written to be carrier-neutral. Exact field names differ between the dialer's admin panel and your carrier's portal, but the parameters and the order of operations are the same everywhere.

Before You Start: What to Gather

A SIP trunk connection needs a handful of parameters from your carrier. Collect all of them before touching the dialer — hunting for one mid-setup is what stretches a 30-minute job into an afternoon.

• SIP endpoint — the carrier's signaling host (IP address or domain) and port (commonly 5060 for UDP/TCP, 5061 for TLS).
• Authentication method — either IP-based (the carrier whitelists your dialer's IPs) or credential-based (a SIP username and password / registration).
• Channel count — the number of simultaneous calls the trunk allows.
• Calls-per-second (CPS) limit — how fast the carrier lets you originate new calls.
• Allowed codecs — typically G.711 (a-law/µ-law) and often Opus or G.729.
• DTMF mode — RFC 2833 / telephone-event is the common default.
• Your DIDs — the numbers authorized on the trunk to present as caller ID.
• The dialer's IPs — the signaling and media (RTP) IP addresses your carrier must allow.

Step 1 — Choose the Authentication Method

Carriers support two ways to trust your traffic. Pick one with your carrier:

IP authentication (recommended where possible). The carrier whitelists your dialer platform's signaling and media IP addresses, and calls from those IPs are trusted without registration. It's simpler and more robust for server-to-server trunks. You'll need the dialer's static IPs — DialerBee provides these for your carrier's allow-list.

Credential authentication. The dialer registers to the carrier with a SIP username and password. Use this when your carrier requires registration or when your dialer's IPs aren't static. Store the credentials securely in the dialer's trunk configuration.

Step 2 — Add the Trunk in the Dialer

In the dialer's telephony/trunk settings, create a new trunk and enter the carrier's endpoint and port, the authentication details from Step 1, the transport (UDP, TCP, or TLS — prefer TLS where the carrier supports it), and the channel/CPS limits your carrier gave you. If the dialer supports multiple trunks, name them clearly by carrier and region so routing rules stay readable.

At the same time, give your carrier the dialer's IPs to whitelist (for IP auth). Both sides must trust each other before any call will complete.

Step 3 — Provision Caller-ID DIDs

Your outbound caller IDs live on the carrier's trunk, not inside the dialer. Confirm every DID you intend to present is authorized on your carrier account, then configure the dialer to present the right DID per campaign or per destination.

Carriers commonly reject calls whose caller ID isn't provisioned on the trunk, so this step and Step 2 must agree. If you rotate numbers to protect answer rates, manage that alongside caller-ID intelligence so reputation and local presence are handled deliberately rather than by accident.

Step 4 — Size Capacity: Channels and CPS

Predictive and power dialing place many simultaneous calls, so capacity planning is not optional.

Channels. A predictive dialer running a 3:1 over-dial ratio for 50 agents can open up to 150 concurrent calls. Your trunk's channel count must cover your expected peak concurrent calls plus roughly 20% headroom. Under-provision and calls fail at peak; over-provision and you may pay for unused capacity on some contracts.

Calls per second. Carriers often cap new-call origination at 5–30 CPS. A dialer can burst above that at campaign start or mass agent login. Either raise the carrier's CPS limit or configure the dialer to throttle outbound CPS to match — otherwise you'll see bursts of failed calls that look like a routing problem but are really a rate limit.

Step 5 — Confirm Codecs and DTMF

Agree at least one codec in common with your carrier. G.711 is uncompressed (about 87 kbps per call) and needs no transcoding — the safe default for quality. Opus or G.729 save bandwidth but add processing. If the dialer offers only G.711 and the carrier requires G.729, calls will fail on codec negotiation, so verify overlap up front.

Set DTMF to the mode your carrier expects (usually RFC 2833). Wrong DTMF handling is invisible until an agent can't navigate an IVR or a keypress-based opt-out doesn't register — so test it explicitly (Step 6).

Step 6 — Test Before You Go Live

Never point a live campaign at a brand-new trunk. Run this test sequence first:

1. Basic connectivity: place a single outbound test call and confirm it completes.
2. Two-way audio: verify both parties hear each other. One-way audio is the most common SIP issue and almost always points to NAT/firewall or an RTP port-range problem.
3. DTMF: call an IVR or test line and confirm keypresses register.
4. Caller ID: confirm the number you provisioned is what actually displays.
5. Recording: if you record calls, verify the recording captures audio end-to-end — some BYOC setups miss recordings when media doesn't traverse the recording server.
6. AMD behavior: place calls to a known voicemail and a known live answer to confirm answering-machine detection classifies correctly over your trunk.
7. Failover: if you configured a secondary trunk, disable the primary and confirm calls reroute.
8. Load: run a small burst of concurrent calls to confirm channel and CPS limits behave as expected.

Step 7 — Add Redundancy

A single trunk means a single point of failure: if it goes down, outbound stops. Where the dialer supports it, configure a primary and secondary carrier with automatic failover on health-check failure, and consider least-cost or regional routing (for example, route UAE numbers through one carrier and Saudi numbers through another). Multi-trunk setups also let you spread load under CPS limits.

Multi-Tenant BYOC

For BPOs and resellers, each client can bring their own trunk. DialerBee's BYOC architecture keeps per-tenant trunk credentials, routing rules, and DID assignments isolated, so one tenant's carrier configuration never affects another's. That lets each client keep existing carrier contracts, use local carriers per country, and manage caller-ID reputation independently.

Troubleshooting Quick Reference

• Calls fail immediately (403/407): authentication mismatch — check IP whitelist or SIP credentials on both sides.
• Calls connect but no audio / one-way audio: NAT or firewall blocking RTP; open the media port range and confirm the dialer's media IPs are reachable.
• Calls rejected with caller-ID error: the presented DID isn't authorized on the trunk — provision it with your carrier.
• Bursts of failed calls at campaign start: exceeding the carrier's CPS limit — throttle the dialer or raise the limit.
• IVR/opt-out keypresses ignored: DTMF mode mismatch — align on RFC 2833.
• Codec negotiation failure: no shared codec — add G.711 or the carrier's required codec.

Go-Live Checklist

1. Trunk authenticated (IP or credentials) and confirmed on both sides.
2. DIDs provisioned and caller ID verified on a live call.
3. Channel count covers peak concurrency plus headroom; CPS within carrier limit.
4. Shared codec confirmed; DTMF tested against an IVR.
5. Recording verified end-to-end (if used); AMD validated over the trunk.
6. Failover tested; secondary trunk ready.
7. Start with one campaign, monitor, then scale.

Frequently Asked Questions

What do I need from my carrier to set up a SIP trunk?

The SIP endpoint (host and port), authentication method (IP whitelist or username/password), channel count, calls-per-second limit, allowed codecs, DTMF mode, and the DIDs authorized as caller ID. You'll also give the carrier your dialer's signaling and media IPs to whitelist.

IP authentication or credentials — which is better?

IP authentication is simpler and more robust for server-to-server trunks when your dialer has static IPs, so it's the recommended default. Use credential (registration) authentication when the carrier requires it or your IPs aren't static.

How many channels does a predictive dialer need?

Cover your peak concurrent calls plus about 20% headroom. A 3:1 over-dial ratio for 50 agents can open up to 150 simultaneous calls, so the trunk needs at least that many channels — sizing to average concurrency will cause failures at peak.

Why do I have one-way or no audio on SIP calls?

Almost always a NAT or firewall issue blocking the RTP media stream. Open the carrier's RTP port range and make sure the dialer's media IPs are reachable from the carrier's network. Signaling can succeed while media is blocked, which is why the call connects but has no audio.

What is a CPS limit and why does it matter?

Calls-per-second is how fast the carrier lets you originate new calls, often 5–30 CPS. Dialers can burst above it at campaign start, causing a wave of failed calls. Either raise the limit or throttle the dialer's outbound CPS to match.

Can I use more than one carrier at once?

Yes, if the dialer supports multiple trunks. Run a primary and secondary with automatic failover, and optionally route by region or least cost. Multi-trunk setups improve resilience and help you stay within per-trunk CPS limits.

Does DialerBee support BYOC SIP trunks?

Yes. DialerBee supports BYOC with IP or credential authentication, multiple trunks with failover and routing, per-tenant trunk isolation for multi-tenant deployments, and provides the platform IPs your carrier needs to whitelist.

SIP trunk setup is methodical, not mysterious: gather the parameters, agree authentication, size capacity honestly, and test every path before a live campaign touches the trunk. Pair this walkthrough with the BYOC predictive dialer guide for the cost and architecture side. To connect your carrier to DialerBee, book a demo and we'll help you plan the trunk, capacity, and test cycle.