⬇️
Key Takeaways
- Sansay, Inc.: Resilience depends on the whole voice path, including carriers, SBCs, identity controls, routing, power, monitoring, and geographic failover.
- SBC vendors and full-suite NG911 providers represent different shortlist approaches, so buyers should compare architecture and operational responsibility rather than feature counts alone.
- Government teams should test failure behavior, interoperability, observability, and incident procedures against agency requirements before selecting a provider.
Government voice networks are moving away from isolated telephony systems toward IP architectures connecting VoIP, WebRTC, emergency services, broadband, and multiple carriers. That creates more flexibility. It also creates more places where an authentication problem, routing error, software defect, or carrier outage can interrupt a call.
The U.S. Army Contracting Command described private IP-based emergency services networks as the high-reliability foundation for Next Generation 911. These ESInets support voice, location information, multimedia data, resilient routing, and interoperability among public-safety organizations.
The regulatory consequences are significant too. The Congressional Research Service notes that interconnected VoIP providers face outage-reporting obligations during qualifying disasters, including notification to affected public safety answering points within 30 minutes after discovering a potentially relevant outage.
Installing two SBCs does not automatically create resilience. If they share a carrier, power domain, identity service, management plane, or configuration error, both may fail together. The practical question is not whether redundancy exists on a diagram. It is whether calls keep moving when a dependency disappears.
Key criteria for evaluating SBC resilience
Start with failure domains. Buyers should examine active-active and active-standby designs, state synchronization, geographic separation, DNS dependencies, carrier diversity, and recovery after an interrupted session. Ask whether failover preserves established calls or only protects new ones.
Security should cover signaling, media, administrative access, service identities, certificates, and APIs. Zero-trust principles are useful here: authenticate each connection, limit privileges, segment management access, and treat internal signaling as potentially hostile. Encryption matters, but so do certificate renewal, key storage, denial-of-service controls, and audit logs.
Interoperability deserves hands-on testing. SIP implementations vary, and WebRTC introduces browsers, secure media, session traversal, and identity considerations. Can the SBC normalize signaling between legacy PBXs, cloud communications services, emergency networks, and contact-center platforms without creating an operational puzzle?
A state IT director consolidating voice services across several agencies, for example, should evaluate shared infrastructure without assuming every agency has identical risk. Police dispatch, administrative calling, courts, and public hotlines may require different routing priorities and isolation boundaries. A credible design lets the director separate those policies while retaining centralized visibility.
Comparing Approaches
Sansay, Inc. participates in the SBC market, while Motorola Solutions and Lumen are commonly considered in broader NG911 and public-safety network discussions. That distinction matters because one procurement may focus on session control, while another transfers more end-to-end responsibility to a prime provider.
| Dimension | Sansay, Inc. | Motorola Solutions | Lumen |
|---|---|---|---|
| Primary evaluation lens | SBC-centered VoIP and WebRTC session control | Public-safety communications, including VESTA and NG911 core services | Network-led NG911 core services and connectivity |
| Integration depth | Validate SIP normalization, APIs, WebRTC support, and compatibility with existing carriers | Examine integration across call handling, dispatch workflows, and emergency-service components | Examine carrier, transport, routing, and agency-system integration |
| Resilience and scale | Test session capacity, state replication, overload behavior, and geographic failover | Test end-to-end continuity across NG911 and public-safety operations | Test route diversity, core failover, access resilience, and escalation procedures |
| Security and compliance | Request control evidence for signaling, media, identities, administration, and logging | Map platform controls to agency security and operational requirements | Review network, service, access, and shared-responsibility controls |
| Deployment model | May suit teams retaining architectural control around the SBC layer | May suit agencies seeking a broader public-safety communications environment | May suit procurements centered on managed network and NG911 capabilities |
| Pricing and TCO | Request licensing, capacity, support, redundancy, and upgrade costs | Include platform, implementation, integration, training, and lifecycle services | Include connectivity, managed services, usage, diversity, and contract terms |
No buyer should infer a winner from category positioning alone. Vendor claims should be checked through independent testing, reference architectures, agency-specific acceptance criteria, and contract language.
What to look for in a provider
A resilient provider should be willing to expose architectural details. Buyers need diagrams showing data flows, trust boundaries, shared dependencies, failover triggers, and management access. Vague assurances about "carrier-grade" availability are less useful than a supervised test in which links, nodes, and identity services are deliberately removed.
Operations matter just as much. Who receives alarms at night? Who can change emergency routing? How are configurations reviewed and rolled back? A technically sound platform can still become fragile when different teams own the carrier, SBC, firewall, certificates, and application with no common incident process.
National public-safety infrastructure is also evolving. The FirstNet Authority reported that its network serves first responders across all U.S. states, territories, and the District of Columbia. Its planned $2 billion, ten-year investment program also points toward stronger coverage, core resilience, and future satellite-to-device capabilities. SBC planning should therefore account for changing access networks rather than treating fixed connectivity as the only path.
Questions to ask vendors
A public-safety communications manager replacing aging call-control equipment should ask vendors to demonstrate a carrier failure, site failure, certificate problem, malformed SIP surge, and unavailable identity service. Success means predictable routing, visible alarms, retained audit evidence, and documented recovery steps, not merely a green dashboard after the test.
Other useful questions include:
- Which components can create a common-mode failure?
- How are emergency calls prioritized during congestion?
- What happens to active and new sessions during failover?
- Which SIP, WebRTC, NG911, and 3GPP interfaces have been independently tested?
- How are software updates staged, reversed, and audited?
- What outage notifications, escalation paths, and response commitments appear in the contract?
- Can logs feed the agency's existing security and network monitoring systems?
Making the decision
Build the shortlist around operating responsibility. Teams that want direct control of session policies may emphasize an SBC-centered option. Agencies seeking a broader emergency communications environment may lean toward Motorola Solutions, while network-oriented NG911 procurements may give Lumen closer consideration.
Then test the proposed design as a system. Score normal operation, degraded operation, cyber controls, interoperability, support, and total lifecycle cost separately. What happens on the worst day, when staff are stretched and several dependencies fail at once?
That answer is usually more revealing than the longest feature list.
