The Softswitch Era

What Is a Softswitch?

A softswitch is a software-based call control system that performs the routing and signaling functions of a traditional telephone switch, but runs on standard commercial servers rather than specialized hardware. The term emerged in the late 1990s to describe a new architectural approach that separated two functions that traditional circuit switches always combined:

In a traditional 5ESS or DMS-100, these functions are inseparable — the same physical system both decides where the call goes and physically switches the voice circuits. In the softswitch model, a software controller (running on a Dell or HP server) sends instructions to media gateways (hardware devices that convert between TDM and IP), which physically handle the voice. The softswitch itself doesn't touch the audio at all.

This separation created enormous flexibility. The softswitch could run on redundant commodity hardware at a fraction of the cost of proprietary switch hardware. It could be updated with new features via software releases rather than hardware upgrades. And it could scale horizontally — adding servers to add capacity, rather than buying a new switch chassis.

From SS7 to SIP: The Signaling Revolution

Traditional PSTN switches use SS7 (Signaling System 7) — a dedicated out-of-band signaling network that carries call setup, teardown, and features information separately from the voice circuits. SS7 is robust and reliable but requires specialized, expensive equipment and expertise.

Softswitches introduced SIP (Session Initiation Protocol) as an alternative signaling protocol. SIP is an internet protocol — it runs over IP networks using standard software stacks. A SIP call setup message looks very similar to an HTTP request. SIP dramatically lowered the barrier to entry for new carriers, as it required no specialized signaling hardware or deep knowledge of SS7 internals.

The transition from SS7 to SIP has been gradual and is still ongoing. Most carrier networks today support both: legacy TDM interconnections still use SS7, while new IP interconnections between carriers use SIP. Session Border Controllers (SBCs) sit at the network edge and bridge between SIP networks and the remaining SS7 infrastructure.

Key Softswitch Platforms

How CLECs and VoIP Providers Use Softswitches

Competitive Local Exchange Carriers (CLECs) entering the market after 1996 found softswitches transformative. Instead of investing tens of millions of dollars in a 5ESS or DMS-100, a new CLEC could deploy a Metaswitch or BroadWorks platform for a fraction of the cost and be operational within weeks rather than months.

A typical CLEC softswitch deployment looks like this:

• Softswitch / Call Agent — runs in a carrier data center or colocation facility, handles call routing logic for all served numbers
• Media Gateways — deployed at points of interconnection with the PSTN, convert between TDM (SS7/T1) and IP (SIP/RTP)
• Session Border Controllers — manage SIP peering with other carriers and protect against attacks
• Number Portability Interface — connects to the NPAC (Number Portability Administration Center) via a Local SMS (Service Management System) for LNP queries
• Provisioning systems — web-based admin interfaces to add, change, and delete subscriber services

VoIP-native carriers (Vonage, Lingo, MagicJack, Google Voice, and thousands of smaller providers) skipped the TDM infrastructure entirely — they deployed softswitches as their core infrastructure from day one, interconnecting with the PSTN only through digital gateways at the edges.

The Softswitch Industry Timeline

Implications for Number Lookups

The softswitch era creates significant complexity for carrier and switch-type lookups. Because softswitches run on generic hardware, many softswitch deployments reuse CLLI codes that were originally assigned to TDM switch installations. A CLLI code showing 5E or DM1 might actually be served by a Metaswitch that was deployed to replace the original hardware — but the routing databases haven't been updated.

Additionally, softswitches often aggregate multiple NPA-NXX blocks from geographically dispersed areas onto a single platform. This makes the physical location implied by a CLLI code less meaningful — the number might be routed to a softswitch in a data center hundreds of miles from the subscriber's actual location.

Number portability (LNP) adds another layer: a number originally assigned to a 5ESS might have been ported to a CLEC running BroadWorks, but the Telcordia LERG routing tables may still show the original 5ESS CLLI for the NPA-NXX. This is why carrier lookup results always carry a caveat — they reflect the assigned carrier for that number block, which may differ from the actual serving carrier post-port.