SS7 Link Capacity
Calculate signaling capacity of an SS7 link based on link speed and message size.
About SS7 Link Capacity
SS7 link throughput in Message Signal Units per second is the raw link bandwidth divided by the average MSU size in bits — but standards bodies (ITU-T, ANSI) recommend operating signaling links well below their theoretical maximum, commonly around 40% fill factor, so that if a link or linkset fails, traffic rerouted onto surviving links doesn't overload them. This headroom is a deliberate resilience design choice specific to signaling networks, where a congested or failed signaling path can disrupt call setup for an entire trunk group even if the voice/bearer channels themselves are fine.
Formula
MSU throughput
MSU_per_sec = link_speed_bps / (avg_MSU_bytes × 8) × fill_factor
Worked example
With the default values below, SS7 Link Capacity returns Recommended Sustained MSU Rate of 160.0. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Link Speedminimum 1 kbps
- 64 kbps
- Average MSU Sizeminimum 1 bytes
- 20 bytes
- Recommended Fill Factoraccepts 1–100
- 40
Results
- Recommended Sustained MSU Rate
- 160.0 MSU/sec
- Theoretical Max MSU Rate (100% fill)
- 400.0 MSU/sec
Step by step
- 1Values used
- 2MSU throughput
- 3Recommended Sustained MSU Rate= 160.0 MSU/sec
- 4Theoretical Max MSU Rate (100% fill)= 400.0 MSU/sec
Assumptions and limits
- The result is derived only from the 3 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 1 decimal place, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Why does SS7 recommend only ~40% link utilization instead of running near capacity?
SS7 signaling links form linksets where traffic automatically reroutes to surviving links if one fails — running normal traffic at 40% means the remaining links can absorb a failed link's traffic (roughly doubling load on survivors in an A-B linkset) without exceeding capacity, since signaling congestion can disrupt call setup network-wide, not just for the failed link's calls.
Why does average MSU size vary and how does it affect capacity?
MSU size varies by message type — ISUP call setup/teardown messages, TCAP transaction messages (e.g. for SCCP/database queries), and SCCP management messages all differ in payload size — a network with a heavier proportion of large database-query-style transactions will have a higher average MSU size and correspondingly lower MSU-per-second capacity for the same link speed.
How does SIGTRAN (SS7 over IP) change this calculation?
SIGTRAN (M3UA/M2PA over SCTP/IP) decouples signaling from the traditional 64 kbps TDM link, allowing much higher-speed IP links to carry SS7 signaling — the same MSU-per-second math still applies, but with link speed potentially in the Mbps range rather than 64 kbps, vastly increasing capacity while retaining the SS7 message-level protocol semantics.