Understanding VoIP Overbooking: Why Cheap Trunks Are Cheap

Every industry has its version of overbooking. Airlines sell more seats than the plane has. ISPs advertise speeds they cannot deliver to every customer simultaneously. Hotels accept more reservations than they have rooms. The economics are the same everywhere: if you can predict that not everyone will show up at the same time, you can sell more capacity than you have and pocket the difference.

VoIP trunk providers do this too. And understanding how they do it explains why the per-channel pricing between providers can vary by 3x or more for what appears to be the same service.

What overbooking actually means

A SIP trunk provider has a finite amount of infrastructure: session border controllers (SBCs) that handle signaling and media, bandwidth at peering points where their network connects to upstream carriers, and capacity on those upstream carriers for terminating calls to the PSTN.

When a provider sells you 50 concurrent call channels, they are making a commitment that your system can have up to 50 simultaneous calls transiting their network. The question is whether they have provisioned enough infrastructure to honor that commitment to every customer at the same time.

A provider with 1,000 customers who each bought 50 channels has sold 50,000 channels of concurrent capacity. If they actually built out infrastructure to handle 50,000 simultaneous calls, their costs would be enormous and their pricing would reflect that. Instead, they look at their traffic patterns and see that the aggregate peak across all customers is more like 15,000 concurrent calls. So they build for 20,000 — some headroom above the observed peak, but well below the total sold capacity. This is overbooking.

The ratio between sold capacity and actual infrastructure capacity is the overbooking ratio. A conservative provider might run at 1.5:1. An aggressive one might run at 4:1 or higher. The more aggressive the ratio, the lower the cost to serve each customer, and the lower the price they can charge.

The economics behind the price gap

Trunk pricing is under constant downward pressure. Customers shop on price. Comparison sites list providers by cost per channel or cost per minute. Providers who charge more need to justify the premium, and "we don't overbook as aggressively" is a hard sell when the customer has never experienced the consequences of overbooking.

This creates a race to the bottom. Providers cut costs wherever they can: more aggressive overbooking ratios, least-cost routing that sends calls through the cheapest available upstream carrier regardless of quality, and lean operations with minimal engineering staff. The result is a provider that works fine 90% of the time and fails during the 10% that matters most — peak business hours when call volume is highest and quality matters the most.

The providers charging a premium are not necessarily making higher margins. They are often spending more on infrastructure per customer: lower overbooking ratios, direct interconnects with major carriers instead of routing through aggregators, redundant SBCs, and enough engineering staff to monitor and respond to capacity issues before they affect customers.

How it works at a technical level

Overbooking can occur at every layer of the provider's infrastructure.

SBC session limits. The SBC is the front door. It handles SIP signaling (call setup, teardown, authentication) and often proxies or relays media. Each SBC has a maximum number of concurrent sessions it can handle, determined by CPU, memory, and licensing. When an SBC hits its session limit, new calls get rejected — typically with a SIP 503 (Service Unavailable) response. A well-run provider distributes load across multiple SBCs, but the aggregate capacity of their SBC farm is still finite.

Media processing. If the provider performs any media manipulation — transcoding between codecs, recording, SRTP-to-RTP conversion — that consumes CPU. Media processing is far more resource-intensive than signaling. A system that can handle 10,000 signaling sessions might only be able to transcode 2,000 simultaneous calls.

Bandwidth at peering points. Where the provider's network connects to other networks (upstream carriers, internet exchanges, other providers), there is a fixed amount of bandwidth. Each G.711 call consumes roughly 85-90 kbps in each direction. At 10,000 concurrent calls, that is nearly 1 Gbps of media traffic in each direction. If the peering link is saturated, packets queue up and get delayed or dropped. The symptoms are jitter and packet loss — the classic markers of degraded call quality.

Upstream carrier capacity. The trunk provider is often not the one actually connecting your call to the PSTN. They buy termination from upstream carriers. Those upstream carriers have their own capacity limits and their own overbooking ratios. A call that traverses two or three overbooked networks accumulates quality degradation at each hop.

What happens when an overbooked provider hits its limits

The failure modes depend on which resource is exhausted first.

Failed call setups. When SBC capacity or upstream carrier capacity is exhausted, new calls simply fail. Your PBX sends an INVITE and receives a 503 response, or worse, the INVITE times out with no response at all. The user hears silence, then eventually a fast busy or an error tone. If your PBX is configured with failover to a secondary trunk, it may retry on another provider — adding several seconds of post-dial delay but eventually completing the call.

Increased latency. When bandwidth at peering points is saturated, packets queue in buffers before being forwarded. This adds latency to every call transiting that link. One-way latency above 150ms makes conversation awkward. Above 250ms, it becomes actively difficult to hold a natural conversation because both parties talk over each other.

Jitter. Congestion does not add a constant amount of latency. It adds variable latency — some packets get through quickly, others wait in queues. This variation is jitter. The receiving end has a jitter buffer that absorbs some variation, but when jitter exceeds the buffer's capacity, packets arrive too late to be played and are effectively lost. The result is choppy, broken audio.

Packet loss. When buffers overflow, packets get dropped. Even 1-2% packet loss is audible as clicks, gaps, or robotic-sounding audio. At 5% loss, conversation becomes difficult. At 10%, it is essentially unusable. The MOS score drops rapidly with even small amounts of packet loss.

Quality degradation without total failure. This is the insidious case. The provider is not so overloaded that calls fail outright, but overloaded enough that every call is slightly worse than it should be. MOS scores drop from 4.2 to 3.5. Users do not report it as a problem — they just perceive the phone system as "okay" rather than "good." Over time, this becomes the new normal, and nobody realizes the system should sound better than it does.

Recognizing the pattern

The signature of overbooking is predictability. The problems follow the provider's aggregate traffic patterns, not yours.

Time-of-day patterns. Quality degrades during peak business hours — typically 9 AM to 12 PM and 1 PM to 4 PM in the provider's primary time zone. If you are in a different time zone than most of the provider's customer base, you might experience peak congestion at unusual times relative to your own business hours. Calls at 7 AM or after 6 PM sound noticeably better.

Day-of-week patterns. Weekdays are worse than weekends. Monday mornings and Friday afternoons may be particularly bad because of higher-than-average call volumes across the provider's customer base.

Monthly patterns. Some businesses see spikes at month-end (collections, billing, sales closing). If your provider serves a lot of customers in industries with month-end surges, you might see degradation during the last few days of every month even if your own volume is flat.

The on-net vs off-net test. This is the most diagnostic check you can run. During a period when you suspect quality degradation, make an on-net call (internal extension to extension, not traversing the trunk) and an off-net call (through the trunk to the PSTN) at the same time. If on-net sounds perfect and off-net sounds degraded, the problem is not your local network. It is somewhere between your PBX and the far end — and the trunk provider's infrastructure is the most likely culprit.

Intermittent problems the provider cannot reproduce. You open a ticket. The provider investigates during off-peak hours, finds nothing wrong, and closes it. You experience the problem again the next morning. This cycle repeats. If the provider's investigation never happens during the exact times you experience the issue, they will never see the congestion because it only exists during peak load.

Concurrent call limits: contract vs reality

Your contract might say 50 concurrent channels. But that number can mean different things depending on how the provider structures their service.

Hard limits. Some providers enforce a strict session limit at the SBC. Call 51 gets rejected. You always get your 50, and the 503 is your signal to add capacity. This is clean and predictable.

Soft limits. Other providers allow bursting above your contracted limit. You bought 50 channels but can actually use 60 or 70 during a burst. This sounds generous until you realize the burst capacity is shared. When the provider's overall network is not busy, everyone can burst. When the network is congested, burst capacity disappears and you are back to your contracted limit — or worse, you cannot even reach your contracted limit because the shared infrastructure is overwhelmed.

Committed vs burst capacity. Some providers make this explicit. They sell "up to 100 channels" with a "committed" rate of 50. The committed rate is what they guarantee. The burst rate is best-effort. During off-peak, you get 100. During peak, you might only get 50 — and if the overbooking is aggressive enough, you might not even get that.

Read the contract carefully. "Up to" is doing a lot of work in "up to 100 concurrent calls."

Quality tiers and route selection

Not all calls follow the same path. Many providers maintain multiple route categories.

Direct routes. The provider has a direct interconnect with the terminating carrier. The call goes from your provider to the destination carrier with no intermediaries. Fewest hops, lowest latency, most predictable quality.

Standard routes. The call goes through one or two intermediate carriers. Quality is generally acceptable but less consistent than direct routes.

Least-cost routes. The provider uses a least-cost routing (LCR) engine that sends the call through whichever upstream carrier is cheapest at that moment. The path changes call by call. Quality varies because the cheapest route is not always the best route. Some LCR providers dynamically reroute calls through lower-quality carriers during peak periods because the higher-quality carriers are full or more expensive at that time.

Some providers sell these as explicit tiers. A "premium" trunk product uses direct routes and a "standard" product uses LCR. The premium product costs more but delivers consistently better quality. Others do not tell you which routing they use — they just sell you trunks and route your calls however is most profitable for them at that moment.

If your provider offers quality tiers, consider putting your highest-value traffic on the premium tier and your less critical traffic on standard. A sales floor where every call is a revenue opportunity warrants premium routing. An internal dial tone for a warehouse where people check voicemail twice a day does not.

What to ask a prospective trunk provider

Before signing a trunk contract, ask these questions. The answers — and how the provider responds to being asked — tell you a lot.

"What is your overbooking ratio?" Most providers will not answer this directly, and that is fine. What you are really looking for is whether they understand the question and can articulate their capacity management approach. A provider that says "we provision to handle 100% of sold capacity at all times" is either very expensive or not being truthful. A provider that says "we monitor aggregate utilization and add capacity when we reach 70% of peak" is telling you something useful about their operations.

"What is my concurrent call limit, and is it hard or soft?" You need to know whether your limit is enforced at the SBC or is a contractual number that depends on shared infrastructure.

"What routes will my calls take?" Ask specifically about PSTN termination. Do they have direct interconnects with major carriers? Do they use LCR? Do they offer different quality tiers? A provider that cannot or will not describe their routing is a red flag.

"Can you provide quality metrics for my calls?" Providers who monitor quality and make metrics available to customers are more likely to be managing their network proactively. Providers who have no quality reporting are flying blind — or they have the data and do not want you to see it.

"What happens during peak periods?" Ask about their busiest times and what capacity management looks like during those periods. Ask for historical uptime and quality statistics if available.

Red flags: Reluctance to discuss capacity or routing. Extremely low pricing with no clear explanation of how they achieve it. No quality reporting or monitoring tools. Support that is only reachable by email. Contract terms that disclaim quality obligations entirely.

When cheap is fine and when it isn't

Not every business needs a premium trunk provider. The impact of overbooking depends on your call volume relative to the provider's peak load.

A five-person office making 20 calls a day, with maybe two or three calls concurrent at peak, is statistically invisible on the provider's network. They will almost never be the ones who get a 503 because they are using so little capacity. For this office, a budget provider is a rational choice. The savings are real and the risk is low.

A 100-seat call center running 60-80 concurrent calls during business hours is a completely different situation. They are a meaningful share of the provider's peak load. They will feel every capacity constraint. They need a provider whose infrastructure can handle their peak demand reliably, which means paying for that infrastructure. For this operation, saving $2 per channel per month by using a budget provider is a false economy when one bad hour costs more in lost productivity and lost deals than a year of the price difference.

The middle ground — a 20-50 person office with moderate call volume — is where the decision gets interesting. If the business is not particularly sensitive to voice quality (internal calls, low-stakes conversations), a mid-tier provider is fine. If voice is revenue-critical (sales teams, customer support, professional services where client perception matters), pay for quality.

The irony is that businesses in the middle ground are the ones most likely to get burned by overbooking, because they have enough volume to be affected but not enough visibility into their own quality metrics to diagnose the problem when it happens. They just know that "the phones sound bad sometimes" and attribute it to their internet connection or their PBX.

Measure it

The only way to know for certain whether your trunk provider is delivering the quality you are paying for is to measure it. Track MOS scores over time. Compare quality during peak and off-peak hours. Run a VoIP quality test during both peak and off-peak periods to quantify the difference, and use the bandwidth calculator to verify your connection has enough capacity for your concurrent call volume. Run the on-net vs off-net comparison during periods when you suspect degradation. If you see a pattern, you have data to bring to the provider -- or data to justify moving to one that does not overbook as aggressively.

For more context on related topics, see our posts on SIP trunking fundamentals, why call quality degrades in the afternoon, capacity planning for MSPs, and working effectively with trunk providers. If you are evaluating a new provider, our guide to trunk configuration covers the technical setup side.