SS7 Performance Indicators for Reliable Signaling Links
Australia's PSTN and mobile core networks still rely on SS7 and SIGTRAN for inter-operator signaling, even as IP-based voice platforms expand across Sydney, Melbourne, and regional hubs. Engineers at Telstra, Optus, and TPG Telecom measure a small set of well-understood KPIs to keep call setup times, SMS delivery, and number portability queries within service assurance commitments, turning raw MTP2 and MTP3 counters into early warnings before customers in Brisbane or Perth notice a busy tone.
The shift toward hybrid TDM and IP signaling links, accelerated by the NBN rollout, has not removed the need for traditional performance indicators. The set of metrics collected from signaling links feeds both operational dashboards and regulatory reporting frameworks overseen by ACMA, with foundational reference material available through https://ss7-training.net/.
Selecting KPIs That Reflect Real Signaling Health
The most useful KPIs for Australian carrier environments fall into three families: link-level availability, message-handling performance, and protocol-state behaviour. Selecting indicators from each family prevents blind spots where one metric looks healthy while another quietly signals congestion.
Link availability covers uptime, changeover frequency, and out-of-service duration. Message-handling performance includes MSU throughput, MTP3 retransmissions, and buffer occupancy. Protocol-state behaviour adds processor occupancy, link oscillation counts, and unexpected acknowledgements, giving a balanced view of both the physical link and the protocol stack above it.
Common SS7 KPI Reference Values
The reference values below summarise typical healthy ranges used by Australian carriers when baselining SS7 signaling links. Values outside these bands usually trigger a service assurance review or a field escalation.
| KPI | Healthy Range | Concern Threshold | Likely Cause |
|---|---|---|---|
| Link availability | ≥ 99.95% | < 99.9% | Physical layer faults, fibre cuts |
| MSU throughput | 0.4–0.8 Erlangs per link | > 0.9 Erlangs | Peak load, misrouted traffic |
| MTP3 retransmissions | < 0.1% of MSUs | > 0.5% | Congestion, sequencing errors |
| Changeover events | ≤ 1 per week | ≥ 3 per week | Flapping link, hardware degradation |
| Processor occupancy | < 45% | > 70% | Software fault, traffic spike |
| Buffer occupancy | < 30% | > 60% | Backpressure, slow peer |
These thresholds are not universal. Operators in remote regions such as the Pilbara or the Kimberley sometimes accept lower availability targets due to long-haul transport realities. The numbers should always be tuned against twelve months of historical baseline data.
Interpreting MTP and ISUP Layer Metrics
MTP2 link error rates and signal unit errors form the foundation of SS7 link health monitoring. A sustained rise in signal unit errors often precedes link oscillation that forces a changeover. Engineers monitoring links between capital-city STPs in Sydney and Melbourne typically expect error rates near zero, while transit links to Cairns or Townsville may tolerate a slightly higher baseline.
ISUP indicators such as call setup success rate, answer-to-address-complete ratio, and IAM-to-ACM delay provide a higher-layer view of signaling health. A degrading setup success rate without corresponding MTP errors points to routing or destination faults. Tracking these alongside circuit group congestion alarms helps separate bearer-side issues from pure signaling faults.
Building Dashboards and Alerting Pipelines
Operational dashboards in Australian carrier NOCs combine SS7 KPIs with SIGTRAN SCTP association metrics, since both protocols frequently share transport in modern cores. Time-series visualisations of MSU throughput, link availability, and processor occupancy allow engineers to spot trends over weeks rather than reacting to individual threshold breaches.
Alerting pipelines should distinguish between paging alarms and dashboard-only indicators. Page-worthy events usually include sustained link outage, processor occupancy above 80%, or repeated changeovers within a short window. Lower-priority indicators are better suited to weekly review meetings, where trends can be correlated with planned maintenance or recent NBN fibre work.
Avoiding Common Monitoring Pitfalls
A frequent mistake is treating absolute MSU counts as a primary indicator. MSU volume varies by time of day, marketing campaigns that trigger mass SMS bursts, and seasonal events such as end-of-financial-year promotions in Adelaide and Perth business districts. Comparing absolute counts without context produces misleading alarms during entirely normal traffic peaks.
Another pitfall is ignoring the relationship between SCTP heartbeat metrics and SS7 retransmissions when links ride over IP. A sudden rise in MTP3 retransmissions on a SIGTRAN link often reflects SCTP path failure rather than an SS7 fault. Operators should correlate the two layers before opening a vendor ticket, since the corrective action may involve NBN transit providers rather than the signaling vendor.
Threshold Drift and Long-Term Trend Watch
KPIs are not static. A signaling link in Adelaide carrying ported-number queries for a growing VoIP provider will see its traffic mix shift year over year, and the original thresholds stop reflecting reality. Continuous baselining, ideally with rolling thirty-day averages, keeps alerts meaningful and avoids fatigue from chronic false positives.
Long-term trend watching also supports regulatory reporting and investment planning. ACMA's service quality frameworks and Communications Alliance operational standards both reference measurable performance commitments. Clean KPI history simplifies compliance reviews and provides evidence when justifying new signaling links or upgraded STP capacity in high-growth corridors around Brisbane or Melbourne's inner west.
Reporting Use Cases for Operations Leaders
Operational leaders often need KPIs translated into service language rather than protocol language. A board-level report might express performance as successful call setup ratio per million attempts, average post-dial delay, or SMS delivery success across the Optus and Telstra interconnect footprints. Mapping raw counters to business-facing indicators requires a stable KPI dictionary maintained by the network operations centre.
Quarterly reviews should compare actual performance against committed service levels, with explanatory notes for any month where indicators exceeded concern thresholds. This documentation supports both internal governance and external audit work, providing a defensible record when negotiating interconnect agreements with peer carriers under ACMA oversight.
A reliable SS7 monitoring setup starts with a small, well-understood KPI set, baselined against local operating conditions rather than generic vendor defaults. Teams that keep link availability, MSU throughput, retransmission rates, and changeover counts on a single dashboard catch most signaling problems before they escalate into customer-visible incidents. Continuous baselining, thoughtful correlation between SS7 and SIGTRAN layers, and periodic threshold reviews keep the monitoring system honest as Australian carrier cores evolve toward deeper IP integration.
