Business voice in a power or broadband outage

Start at the person making the call and work towards the voice service. A desk phone may depend on power from a network switch, which depends on mains power and connects through a router to an optical network terminal or another access device. A softphone also depends on its computer or mobile device, audio equipment and connection. Record the real arrangement at each site.

Mark which components share power circuits, cabinets and access connections. A spare handset on the same unprotected switch does not remove that switch as a dependency. A second access circuit may still use the same router or building entry. Describe the failure each proposed safeguard addresses rather than counting devices and assuming the total represents resilience.

Ofcom's digital-landline guidance explains that digital landlines need power and discusses arrangements for reaching emergency services during power cuts. Use that guidance when discussing requirements with the provider. A business design still needs assessment against its own equipment, users and operational risks.

Netavo provides hosted telephony and SIP trunking, together with fibre, Ethernet and private WAN connectivity. These service categories establish the components available for discussion, not a particular backup behaviour or an assurance that a site will keep calling under every failure.

Separate incoming customer calls, outgoing staff calls and emergency-calling needs. An arrangement that keeps a published number answered elsewhere may not let a person in the affected building make an outgoing call. A mobile phone may provide another option, but check coverage, available charge, staff access and the effect of a wider local incident before relying on it.

Describe the required operating state for each failure. During loss of the primary broadband connection, must all users continue working or only a small response team? During a power cut, will the building remain occupied? Who needs a usable calling method, where will it be kept and how will staff know what to do? Turn these answers into testable requirements.

If battery-backed power is part of the design, include every necessary component and assess runtime under the actual load. Record battery maintenance, replacement responsibility and the method for checking health. A label on an uninterruptible power supply does not establish how long the complete voice path will remain usable, especially after equipment changes or battery ageing.

On Netavo's hosted voice, failover routing is set in the visual call-flow editor, so calls to an unreachable site can go to mobiles or another site, and the softphone apps keep working over mobile data.

On Netavo's platform the emergency address for each number or user is registered, and kept current, by the customer in the portal. Do not assume a softphone automatically supplies its current physical location.

Plan controlled tests with the responsible suppliers and site owner. Begin with an agreed failure scenario and identify what may be affected. Test loss of access separately from loss of local power so the result shows which dependency mattered. Where testing could affect safety-related equipment, arrange the procedure with its maintainer and keep the required alternative arrangements in place.

Make ordinary test calls in both directions through the agreed surviving path. Check the destination, two-way audio, caller identification where relevant and the practical ability of staff to answer. Measure how long recovery takes and record what action is manual. Never make an unarranged emergency call to test service; agree an appropriate verification process with the provider.

Restore normal service and verify that the intended routing and equipment state return. Recovery is part of the design: temporary arrangements can remain active unintentionally, and devices may reconnect at different times. Keep a short runbook explaining who declares the incident, who changes the service and who confirms the return to normal operation.

For healthcare and care organisations, align voice continuity planning with the responsible operational team rather than treating it as an isolated IT exercise. Review the plan whenever a site, endpoint, access service or staffing arrangement changes. The useful output is a tested account of what continues, what stops and who acts under each agreed scenario.