Choosing a SIP trunk provider is a carrier-layer decision — one that affects call quality, spam labeling on your outbound calls, the cost of number porting, and what happens when your primary SIP endpoint goes down. This guide covers what SIP trunk providers actually do, how to evaluate them, and what to ask before signing up.
What SIP Trunk Providers Do
A SIP trunk provider connects your IP-PBX or cloud phone system to the public switched telephone network (PSTN) over the internet. The provider owns or leases carrier interconnects and uses them to deliver SIP signaling and RTP media between your platform and the rest of the telephone network.
In practice, the provider handles several things you would otherwise have to manage yourself: provisioning DID (Direct Inward Dialing) numbers, applying STIR/SHAKEN call authentication before calls leave their network, managing carrier-layer routing for least-cost or quality-based path selection, and absorbing the complexity of interconnecting with multiple downstream carriers.
It is worth being precise about what a SIP trunk provider is not. A SIP trunk provider is not a UCaaS provider. UCaaS delivers a fully managed phone system — extensions, auto-attendants, voicemail, meetings — as a service. A SIP trunk provider gives you a carrier connection. You are responsible for the phone system sitting above it. If you want someone else to manage the entire phone system, UCaaS is the right product. If you are running your own IP-PBX, contact center platform, or communications infrastructure, SIP trunking is what gives it access to the PSTN.
Retail vs Wholesale SIP Trunking
SIP trunking is sold in two broad models: retail and wholesale. The distinction matters because they are designed for different buyers.
Retail SIP Trunking
Retail SIP trunking is designed for businesses. The provider manages the platform, the customer portal, and direct support. Configuration is handled through a self-service interface. DIDs, channel counts, and call features are all provisioned and managed from a single account. Pricing is typically structured per channel, per DID, and per minute of usage, with modest minimum commitments. This is the right model for most businesses running an IP-PBX or cloud phone system.
Wholesale SIP Trunking
Wholesale SIP trunking is designed for carriers, resellers, and platforms building on top of voice infrastructure. Per-minute rates are lower than retail, but volume commitments are higher and the buyer is expected to handle their own platform management, number management, and end-customer support. Wholesale does not make sense for a business buying trunking for internal use — it is a product for companies that resell or embed voice services.
High-volume contact centers sometimes operate in a grey zone: their traffic volumes approach wholesale territory, but they are consuming the capacity themselves rather than reselling it. In that case, negotiating a volume-based retail agreement or moving to a wholesale relationship may both be viable options. See: MCC Wholesale Voice.
What to Look for in a Provider
Not all SIP trunk providers offer the same capabilities. These are the factors that matter most when evaluating options.
STIR/SHAKEN Attestation
STIR/SHAKEN is the framework US carriers use to authenticate the calling number on outbound calls. When a call is signed at attestation A, the provider is asserting that the caller is authorised to use the number being presented. Calls signed at A are treated more favorably by carrier-side spam analytics than calls signed at B or C — or unsigned calls.
To sign at attestation A, a provider must hold a registered Operating Company Number (OCN) with NANPA. Ask any prospective provider directly whether they hold an OCN and sign outbound calls at attestation A. If they sign at B or cannot answer the question, factor that into your assessment of outbound call quality and the risk of spam labeling on legitimate calls.
Codec Support
The two codecs that matter for most deployments are G.711 and G.729. G.711 is uncompressed and delivers high audio quality but uses more bandwidth — roughly 64 kbps per active call leg. G.729 compresses the audio stream to around 8 kbps, which reduces bandwidth requirements significantly but introduces some audio quality loss through compression. Both should be supported by any competent provider. Problems arise when a provider's supported codec list does not match what your PBX is configured to offer, causing negotiation failures or fallback to an unintended codec. Confirm codec support and DTMF signaling mode (RFC 2833 is standard; confirm in-band and SIP INFO if your IVR depends on it).
Authentication Method
SIP trunk authentication is typically handled by one of two methods: IP-based authentication (the provider allows traffic only from your registered IP address or range) or username/password digest authentication. For static deployments where your PBX sits at a fixed IP, IP-based authentication is simpler and removes a credential management burden. For deployments where the originating IP changes — remote workers, cloud environments with dynamic addressing — username/password or registration-based authentication is necessary. Check which methods the provider supports and which your platform is configured to use.
Failover and Redundancy
A SIP trunk with a single point of failure is a risk. Good providers offer at least two SIP endpoints — a primary and a failover — in separate geographic locations. When you configure your PBX or SBC (Session Border Controller), you point it at both. If the primary endpoint becomes unreachable, traffic fails over to the secondary automatically. Ask whether the provider supports multiple SIP endpoints per trunk, what the failover mechanism is, and what their historical uptime looks like for the SIP signaling layer.
Geographic DID Coverage
DIDs (telephone numbers) are provisioned by area code or geographic region. If you need local presence numbers in specific markets, verify that the provider has inventory in those areas before you commit. Some providers have strong national US coverage but thin international inventory. If your operation spans multiple countries, confirm DID availability in each market separately — availability varies significantly by provider and by country.
Channel Limits and Burst Capacity
Channels define how many simultaneous calls your trunk can carry. If you exhaust your channel count, additional calls are rejected at the carrier layer — callers receive a busy signal or an error. Understand your peak concurrent call volume, build in a buffer above it, and check whether the provider offers elastic burst capacity (temporary channel expansion during peaks) or requires you to pre-provision a fixed ceiling. For unpredictable inbound volumes, elastic burst capacity is a material advantage.
Support and SLA
A SIP trunk outage directly affects your ability to make and receive calls. Ask what the provider's SLA is for trunk incidents — what response time is committed, what remediation looks like, and what credits (if any) apply if the SLA is missed. Also check support channel availability: is there a 24/7 emergency line for trunk outages, or is support limited to business hours? A provider that is unreachable when a trunk goes down on a Saturday morning is a different risk profile from one with round-the-clock technical support.
Questions to Ask Before Signing Up
Use this list when evaluating any SIP trunk provider before committing to a contract.
- Do you hold a registered OCN, and do you sign outbound calls at STIR/SHAKEN attestation A? This determines your outbound call authentication level and spam-labeling exposure.
- What codecs do you support, and what DTMF signaling modes? Confirm G.711 and G.729 at minimum; confirm RFC 2833 if your IVR or contact center platform depends on DTMF.
- Can I authenticate by IP address instead of username and password? IP authentication reduces credential management risk for static deployments.
- What is your uptime SLA for SIP signaling, and what credits apply if it is missed? Get the SLA in writing before signing.
- How do you handle failover if your primary SIP endpoint goes down? Ask for the specific failover architecture — secondary endpoint location, detection mechanism, and failover time.
- Are DIDs included in the base price or billed separately? DID pricing models vary — some providers include a DID with each channel, others bill per number independently.
- What is the minimum commitment, and what are the porting-out terms? Understand what it costs to leave before you sign up. Porting-out terms and any contractual lock-in should be reviewed before committing.
Switching SIP Trunk Providers
Switching SIP trunk providers is operationally straightforward if planned carefully. The main tasks are number porting, configuration migration, and cutover testing.
Number Porting (LNP)
Local Number Portability (LNP) allows you to move existing telephone numbers from your current provider to a new one. In the US, the porting process for standard DID numbers typically takes two to four weeks. The timeline depends on the responsiveness of the losing carrier and the accuracy of the information submitted in the port order. Toll-free numbers and numbers on complex business accounts can take longer.
During the porting window, your existing trunk must remain active. Numbers that have been ported away from a provider cannot receive calls until the port completes — if you decommission the old trunk early, calls to those numbers will fail. Maintain both trunks in parallel until the port completes and you have verified inbound routing on the new trunk.
Testing Before Cutover
Before cutting over production traffic to a new provider, test inbound and outbound call quality thoroughly. Make calls to mobile numbers, landlines, and international destinations. Test DTMF delivery through your IVR. Simulate a primary endpoint failure to verify failover works. Confirm that call detail records on the new trunk match your platform's CDRs. Only cut over production traffic once you are satisfied that all tested scenarios work correctly on the new trunk.
Keeping the Old Trunk Active
Keep the old trunk provisioned and active until all numbers have ported and you have completed cutover testing. The cost of running two trunks in parallel for two to four weeks is low compared to the cost of a disrupted cutover. Only decommission the old trunk after the new one has been running production traffic for a period you are comfortable with — a few days of clean operation is a reasonable minimum.
SIP Trunking for Contact Centers
High-volume contact centers have requirements that differ from standard business SIP trunking deployments. The scale and traffic patterns of a contact center put different demands on a SIP trunk provider.
Concurrent Channel Capacity
A contact center with 50 agents handling live calls simultaneously needs at least 50 inbound channels, plus capacity for outbound calls if the operation runs blended. A center that also runs outbound campaigns in parallel with inbound queues needs to account for both simultaneously. Undersized channel counts result in calls being rejected at the carrier layer — not queued, rejected — which means callers receive a busy signal rather than waiting.
Burst Capacity
Contact centers experience traffic peaks that can significantly exceed the average concurrent call count. A product recall, a system outage notification, or a marketing campaign can generate a surge of inbound calls within minutes. A provider that supports elastic burst capacity — temporary expansion beyond the provisioned channel ceiling without manual intervention — is materially more suitable for contact center use than one that requires advance provisioning of a fixed ceiling.
Low-Latency Routing
Call quality in a contact center depends on consistent low-latency audio delivery. High latency introduces perceptible delay in conversation; jitter causes audio chopiness. A provider whose network routing results in high or inconsistent latency to your platform location will degrade the call experience for every agent and every caller. During evaluation, test call quality from the actual network location where your contact center platform runs — not from an office desktop on a different connection.
Wholesale SIP for Large Contact Centers
At sufficient volume, wholesale SIP trunking becomes the more cost-effective option for contact centers. The lower per-minute rates available at wholesale can represent significant savings at scale, and the flexibility of a wholesale relationship allows traffic engineering that is not available on standard retail trunks. The tradeoff is that wholesale requires more internal technical management. See: MCC CC Routes and MCC Contact Center.
Looking for SIP trunking built for contact center traffic?
Explore MCC CC RoutesFAQ
What is the difference between a SIP trunk provider and a UCaaS provider?
A SIP trunk provider supplies a carrier-layer connection between your IP-PBX or cloud phone system and the PSTN. It delivers SIP signaling and RTP media but does not manage your phone system or user experience. A UCaaS provider delivers a fully managed communications platform — phones, meetings, messaging, and calling — as a service. UCaaS platforms often use SIP trunks underneath, but that detail is abstracted away from the customer. If you are building or managing your own phone system, you need a SIP trunk provider. If you want a complete managed solution with no telephony infrastructure to run, UCaaS is the more appropriate fit.
How many SIP channels do I need?
The number of SIP channels you need equals the maximum number of simultaneous calls your organisation expects to handle. A channel supports one active call leg — one inbound call or one outbound call. For most businesses, the right starting point is to match channel count to the number of agents or phone users who could all be on a call at the same time. Contact centers should also provision additional burst capacity above that baseline to absorb peak traffic without calls being rejected. If your provider charges per-channel, start conservative and expand; if the provider offers elastic or metered capacity, peak concurrency over a rolling period is the more relevant figure.
What is STIR/SHAKEN and why does my provider's attestation level matter?
STIR/SHAKEN is a framework for authenticating the calling number on a call before it is delivered to the recipient. When a provider signs a call, they assert one of three attestation levels: A (full attestation — the provider is certain the caller is authorised to use the number), B (partial attestation — the call is known to originate from the provider's customer but the number cannot be fully verified), or C (gateway attestation — the call arrived from outside the provider's network). Calls with attestation A are less likely to be flagged as spam or robocall by carrier-side analytics. If your provider cannot sign at attestation A because they do not hold a registered Operating Company Number (OCN), your outbound calls may carry a higher spam-label risk regardless of your intent.
Can I keep my existing numbers when switching SIP trunk providers?
Yes. Local Number Portability (LNP) allows you to transfer telephone numbers from one provider to another. In the US, the porting process typically takes two to four weeks for standard DID numbers, though the timeline can vary. You submit a port-out request to the new provider, who coordinates with your current provider. During the porting window, keep your existing trunk active so calls continue to reach you. Once the port completes and you have verified inbound routing on the new trunk, you can decommission the old trunk. Number porting is a standard process and providers are legally required to support it — refusal or deliberate delay by the losing provider is a regulatory violation.
What should I test when evaluating a new SIP trunk provider?
Before committing to a new SIP trunk provider, test inbound and outbound call quality by running calls to a range of destination types — mobile, landline, international if relevant — and listening for latency, jitter, and audio degradation. Test DTMF delivery, particularly if you use IVR systems, since RFC 2833 and in-band DTMF behave differently across providers and platforms. Confirm that your preferred codecs (G.711, G.729) are supported and correctly negotiated. Test failover by simulating a primary SIP endpoint outage to verify that traffic shifts to the secondary endpoint. Check whether DIDs port in cleanly and that inbound calls on ported numbers route correctly. Document call detail records from the test period and verify they match your platform's CDRs before going live.