Current Location ：
The Four-Hour Question: How Long Can Your Business Be Without Phones
Continuity discussions stall because the question is asked in the wrong form. Would an outage be serious. Of course it would. The useful form is a number: how long can the business operate without inbound and outbound calls before the loss becomes unacceptable, and what would be lost hour by hour. That number determines how much resilience is justified, and it is almost always smaller than the infrastructure spend assumes and larger than the risk register admits.
Build the Hour-by-Hour Cost
The cost of a voice outage is not uniform. The first hour may be absorbed by backlog and goodwill. By the third hour, customers are calling a competitor, deliveries are missed, and staff are improvising on personal mobiles. By the end of a day, the recovery work itself becomes a cost. Writing that sequence down produces a defensible number and, more usefully, identifies which hours matter most and what would protect them.
| Window | Typical impact | What helps |
|---|---|---|
| First 30 minutes | Little external impact, internal confusion | A known procedure and one communication owner |
| One to two hours | Customers notice; some call elsewhere | A tested fallback number |
| Half a day | Operational backlog, missed commitments | Redirect to an alternate site or answering service |
| Full day | Revenue loss, reputational damage | Full failover capability |
| Beyond a day | Contractual and regulatory exposure | Recovery site and a documented plan |
Resilience Should Match the Number
Designing for zero downtime is expensive and often misallocated: money spent on a redundant platform that nobody has failed over is worth less than a tested fallback number and a clear procedure. Where the tolerable window is two hours, the right investment may be a diversion arrangement and a rehearsal rather than a duplicate data centre. Where the window is fifteen minutes, the platform has to fail over automatically, and that requirement should be explicit in the design.
- Express the requirement as a time, not a severity adjective
- Identify which hours are most costly and protect those first
- Separate platform resilience from connectivity resilience
- Include the human procedure in the design, not only the equipment
- Test the arrangement against the stated window, and record the result
The Failover Nobody Has Used
An untested failover is a plan, not a capability. The common finding after an outage is that the redundant path existed and did not work: a licence had expired, a route was never configured, or the secondary site had no one present to answer. Testing should be scheduled, disruptive enough to be meaningful, and followed by a written record of what happened and what changed.
Continuity Includes the Small Things
The details decide whether the arrangement works: whether staff know the fallback number, whether the published number is updated, whether the answering service has current information, whether the emergency contacts are reachable from a mobile. These cost almost nothing and are routinely missing, because continuity planning focuses on infrastructure and stops before it reaches the desk.
Redstone Approach
Redstone deployments begin with the customer's tolerable outage window and design resilience to match it, whether that means redundant paths, automatic failover, or a documented diversion arrangement. We test the arrangement during commissioning and record the measured behaviour, so the plan reflects a demonstrated capability.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
