From BRP and PRI to SIP
Earlier in the environment, business recovery depended on predefined Business Recovery Plan (BRP) procedures and local PRI connectivity. When a circuit failed, the response required confirming the outage with the business, engaging the carrier, implementing the prescribed recovery procedure, and communicating status and ETA to leadership.
As the architecture evolved, the organization gained greater control over toll-free routing through its RespOrg capability and moved toward a more resilient SIP model with multiple carriers and geographically separated recovery capability.
THE ARCHITECTURE EVOLVEDPRI and BRP procedures → RespOrg-controlled toll-free routing → multi-carrier SIP → geographically separated recovery → faster, more controlled failover.
When the design was tested
When primary Verizon SIP circuits failed, Ian opened the carrier incident, established that the problem was part of a broader area outage, and manually failed traffic to the recovery circuits. The transition took roughly ten minutes and produced little meaningful customer or end-user impact.
~10 minFAILOVER
2 CARRIERSRESILIENCY MODEL
~60LOCATIONS IN THE ENVIRONMENT
THE RESULTThe system did exactly what it was designed to do: absorb a carrier failure and keep the business operating.
More than disaster recovery
The geographically separated primary and recovery environments also supported a distributed service model, including follow-the-sun thinking for users and operations across different regions. The objective was not simply to have another data center — it was to design an operating model that could continue serving people when the primary path was unavailable.
SOLLUNA PRINCIPLEDesign for failure before failure becomes the business's problem.