The CPaaS and Aggregator Stack

Every A2P SMS message sent through a programmable API traverses a multi-layer routing chain before reaching a recipient's handset. The chain typically spans four or five distinct entities — each with its own commercial relationship, technical interconnect, and full visibility into message content. Understanding this stack is critical for evaluating delivery performance, cost structure, privacy exposure, and vendor lock-in.

The Full Routing Chain

An SMS sent through a CPaaS API follows this path:

Application (your code)
   │  REST API / webhook
   ▼
CPaaS Platform (Twilio, Telnyx, Sinch, Bandwidth, Vonage)
   │  SMPP or proprietary internal protocol
   ▼
Aggregator / DCA (Syniverse, Iconectiv, or CPaaS-owned path)
   │  SMPP to carrier SMSC
   ▼
Carrier SMSC (AT&T, Verizon, T-Mobile)
   │  SS7 MAP: mt-ForwardSM
   ▼
Recipient Handset

Some CPaaS providers hold direct carrier connections and skip the aggregator layer entirely. Others use aggregators for some carriers but not others, depending on traffic volume, geographic coverage, and commercial agreements. The presence or absence of the aggregator layer is rarely visible to the developer calling the API.

What Is CPaaS?

Communications Platform as a Service (CPaaS) is a cloud-based model that provides programmable APIs for voice, messaging, and video without requiring the developer to operate telecom infrastructure. CPaaS providers abstract the complexity of carrier interconnection, number provisioning, protocol translation, and regulatory compliance behind REST endpoints and webhook-driven event models.

A CPaaS provider typically:

• Provisions phone numbers from carrier inventory and exposes them through a number management API
• Maintains SMPP sessions with carrier SMSCs or aggregators for outbound and inbound SMS traffic
• Translates protocols — accepting HTTP REST requests from applications and converting them to SMPP submit_sm PDUs for carrier injection
• Handles delivery receipts — receiving deliver_sm PDUs from carriers and translating them to webhook callbacks or status API responses
• Enforces compliance — validating sender registration (10DLC campaigns, toll-free verification, short code approval) before allowing traffic to flow

The CPaaS model replaced the earlier requirement for enterprises to negotiate direct SMPP interconnects with carriers — a process that historically required months of carrier onboarding, dedicated infrastructure, and telecom engineering expertise.

Major CPaaS Providers

Twilio

The largest CPaaS provider by revenue and developer adoption. Twilio offers SMS, MMS, voice, email (via SendGrid acquisition), WhatsApp Business API, and a broad range of programmable communication services. Twilio holds direct connections to major US carriers and operates its own Super Network for routing optimization. Its pricing is straightforward per-message, but carrier surcharges are passed through as separate line items.

Bandwidth

Bandwidth is unique among CPaaS providers because it is also a facilities-based carrier — it owns and operates its own voice and messaging network infrastructure registered with the FCC. This means Bandwidth can originate and terminate traffic without relying on third-party aggregators for US domestic routes. Bandwidth also serves as the underlying carrier for several other CPaaS platforms, including the messaging infrastructure that previously powered Twilio's US traffic.

Telnyx

Telnyx operates a private IP network with direct carrier interconnects and its own SIP trunking infrastructure. It positions itself as a carrier-grade alternative to Twilio with lower per-message pricing and more transparent routing. Telnyx exposes SMPP connectivity as a first-class option alongside its REST API, making it attractive to high-volume senders migrating from legacy aggregator setups.

Sinch

Originally focused on mobile messaging and operator integrations in Europe, Sinch has grown through aggressive acquisition — including MessageBird (2024), SAP Digital Interconnect, and Inteliquent. Sinch has direct operator connections in over 60 countries and handles significant global A2P volume. The MessageBird acquisition brought a developer-friendly API and omnichannel platform (SMS, WhatsApp, email, voice) under the Sinch umbrella.

Vonage (Nexmo)

Acquired by Ericsson in 2022, Vonage offers a CPaaS platform with strong voice, video (via the Vonage Video API, formerly TokBox), and messaging capabilities. Vonage's SMS API supports global delivery with adaptive routing, but its messaging focus has shifted toward conversational commerce and the Vonage Communications Platform for enterprise customers.

What Are Aggregators and DCAs?

A Direct Connect Aggregator (DCA) is an intermediary that maintains SMPP connections to carrier SMSCs on behalf of CPaaS providers and enterprise senders. Aggregators exist because carriers limit the number of direct interconnects they support — onboarding a new SMPP partner requires carrier engineering resources, compliance review, and ongoing relationship management.

Rather than onboarding thousands of individual senders, carriers connect to a small number of trusted aggregators who then resell that connectivity upstream.

How Aggregators Work

1. Carrier onboarding — The aggregator negotiates SMPP interconnection agreements with each carrier, establishing persistent TCP sessions to the carrier's SMSC.
2. Traffic consolidation — Multiple CPaaS providers and enterprise senders funnel their outbound messages through the aggregator's platform.
3. Campaign compliance — For US 10DLC traffic, aggregators register brands and campaigns with The Campaign Registry (TCR) and propagate that registration to carriers.
4. Routing and failover — Aggregators maintain routing tables that direct traffic to the appropriate carrier SMSC based on the destination number's home network. If a primary route fails, the aggregator can reroute through an alternative path.

Notable Aggregators

The boundary between CPaaS provider and aggregator is blurring. Bandwidth operates as both. Twilio has invested in direct carrier connections to reduce aggregator dependency. Sinch's acquisition strategy has brought DCA-level connectivity in-house for many routes.

How Routing Decisions Are Made

When a CPaaS provider or aggregator receives an outbound SMS, it must select a route — the specific carrier SMSC and interconnect path through which the message will be delivered. This decision involves several factors:

Least-Cost Routing (LCR)

The platform evaluates available routes to the destination carrier and selects the one with the lowest per-message cost. Large providers maintain rate decks — tables mapping destination networks to per-message prices — and update them as carrier agreements change. LCR is the default optimization strategy for most aggregators.

Carrier Preference and Quality Routing

Some platforms weight routes by delivery performance rather than cost alone. Metrics include delivery rate, average latency to DLR, and carrier-reported error rates. Quality routing may prefer a more expensive direct route over a cheaper multi-hop path if historical data shows higher delivery rates.

Geographic and Regulatory Routing

International messages require routing through country-specific interconnects that comply with local regulations. Some countries mandate that A2P traffic pass through a licensed local aggregator. The routing engine must select paths that satisfy both regulatory requirements and sender ID rules (alphanumeric vs. numeric originator, pre-registration requirements).

10DLC Campaign Routing

For US domestic traffic, routing must account for the sender's TCR campaign registration status. Messages from registered campaigns are routed through carrier-approved 10DLC paths with higher throughput allowances. Unregistered traffic is either blocked or rate-limited severely.

Visibility at Each Layer

Every entity in the routing chain has full, unencrypted visibility into the message:

SMS is transmitted in plaintext at every hop. There is no end-to-end encryption, no envelope encryption between layers, and no mechanism in the SMPP or SS7 protocol to encrypt message content. Every intermediary — CPaaS provider, aggregator, carrier, and any lawful intercept system — can read the full message body, sender address, and recipient address.

This full-stack visibility is a fundamental architectural property of SMS, not a bug or misconfiguration. It is why SMS is unsuitable as a secure channel for sensitive data and why regulatory frameworks like CALEA require carriers to provide message content to law enforcement upon lawful request.

SMPP Connections and Carrier SMSCs

CPaaS providers and aggregators maintain persistent SMPP sessions with carrier Short Message Service Centers (SMSCs). These sessions are the injection point where A2P traffic enters the carrier network.

Session Architecture

• Bind type — Most A2P connections use bind_transceiver, allowing both message submission (submit_sm) and receipt of delivery reports (deliver_sm) on the same session.
• Windowing — SMPP supports asynchronous windowing, where multiple submit_sm PDUs can be in-flight before receiving responses. Window sizes of 10–50 are common; high-volume senders may negotiate larger windows.
• Throughput limits — Carriers impose per-connection and per-campaign throughput caps measured in messages per second (MPS). 10DLC campaigns typically receive 15–75 MPS depending on trust score; short codes may reach 500+ MPS.
• Connection redundancy — Production deployments maintain multiple SMPP sessions across geographically distributed endpoints for failover and load distribution.

Protocol Translation

The CPaaS platform performs protocol translation between its external API and the SMPP layer:

Developer sends HTTP POST to /Messages
   │
   ▼
CPaaS platform validates request, checks campaign registration,
selects route, constructs SMPP submit_sm PDU
   │
   ▼
submit_sm sent over persistent SMPP session to carrier SMSC
   │
   ▼
Carrier SMSC returns submit_sm_resp with message_id
   │
   ▼
CPaaS platform maps message_id to API-level SID,
returns 201 Created to developer

Number Provisioning

CPaaS providers acquire phone number inventory through several channels:

• Direct carrier allocation — Numbers leased in blocks from carriers (Bandwidth, as a carrier, allocates from its own number pool)
• Number portability — Numbers ported from other carriers or providers via the Local Number Portability (LNP) process
• Wholesale number brokers — Bulk number acquisition from wholesale providers who hold large inventories
• NANPA assignments — For North American numbers, allocation ultimately traces back to the North American Numbering Plan Administration

Provisioned numbers must be registered with the appropriate compliance bodies before they can carry A2P traffic. In the US, this means 10DLC registration through TCR, toll-free verification through the Toll-Free Numbering Administrator, or short code approval through the Common Short Code Administration (CSCA).

Delivery Receipts (DLRs)

Delivery receipts flow in the reverse direction through the routing chain, confirming whether a message reached the handset:

Recipient Handset → acknowledgment
   │
   ▼
Carrier SMSC generates DLR
   │  deliver_sm (receipt type)
   ▼
Aggregator / DCA forwards DLR
   │  deliver_sm
   ▼
CPaaS Platform maps DLR to original message SID
   │  HTTP POST to status callback URL
   ▼
Application receives webhook with status update

DLR Status Codes

DLR reliability varies by carrier and route. Some carriers provide handset-level confirmation; others only confirm acceptance at the SMSC. International routes frequently lack reliable DLR support, meaning a sent status may be the final update available.

Industry Consolidation

The CPaaS and aggregator landscape has undergone significant consolidation:

This consolidation collapses layers of the routing chain. When Sinch acquires an aggregator's carrier connections, messages that previously traversed CPaaS → Aggregator → Carrier can now travel CPaaS → Carrier directly, reducing latency, cost, and the number of entities with content visibility.

Cost Structure

Per-message costs accumulate at each layer of the stack:

The total per-message cost for a standard US A2P SMS through a major CPaaS provider typically falls between $0.01 and $0.03 per segment, inclusive of all surcharges. Short codes carry higher monthly fees ($500–$1,500/month) but lower per-message rates. International rates vary dramatically by destination country.

Pricing transparency varies. Twilio itemizes carrier surcharges separately. Telnyx publishes per-carrier rate decks. Some providers bundle all fees into a single per-message rate, making cost comparison difficult without testing actual delivery.

CPaaS Provider Comparison

Further Reading

• How SMS Works — PSTN, SS7, SMSC routing, and how messages travel from phone to phone.
• Carrier SMS Filtering — How AT&T, Verizon, and T-Mobile analyze and filter SMS traffic at the carrier level.