Cloud service
The calling platform can remain available even when one office has lost its route to the internet.
Reliability & Continuity
Design for the failure before it happens.
RabbitRun is the managed network-edge product at the center of Heritage reliability designs. Heritage matches the hardware, wired and cellular paths, and alternate call routing to the workload and failure behavior each location requires.
Configuration boundary: A capability listed by RabbitRun is not automatically included in every Heritage configuration. Heritage confirms the hardware, compatible feature combination, connectivity, capacity, activation behavior, monitoring, support ownership, and charges for each location.
Cloud calling platformMay be healthy while a location is disconnected
RabbitRun managed edgeHardware and path design selected for the workload
Primary wired path
Designed backup path
Phones, applications, and users at the location
Different layers, different failures
Cloud availability is not the same as office reachability.
A call depends on more than the cloud platform. The local internet path, network edge, power, equipment, and call routing each affect what employees and callers experience.
Local connection
One wired provider leaves one local path. A second path changes the design only after delivery and independence are confirmed.
Power and equipment
Internet diversity does not keep unpowered local equipment operating. Power dependencies and local devices need a separate review.
Inbound routing
When a location cannot answer, eligible inbound calls may need a defined route to another location, team, or business calling application.
The principal continuity product
Select RabbitRun hardware for the work it must perform.
Heritage has identified three hardware options. Model choice is not a simple good-better-best ladder: the required workload, path design, and feature combination must be validated together.
RRT-200-LTE
An older, slower option intended for smaller offices.
It can support the same broad feature categories as the other RabbitRun hardware, but not all features at once. Heritage validates the workload and required concurrent feature combination before recommending it.
Still to verifyExact performance, concurrent-feature limits, cellular specifications, availability, and price.
RRT-300-LTE
Positioned by RabbitRun for SMB and branch offices.
- Up to 1 Gbps
- Wi-Fi 6
- 4G LTE multi-carrier cellular
- Voice survivability and POS continuity
- Attack Shield cybersecurity
- Cloud management
These are vendor-listed capabilities, not a statement that Heritage includes or enables every feature in every configuration.
RRT-600-5G
Positioned by RabbitRun for small and medium enterprise branches.
- Up to 2.5 Gbps
- Wi-Fi 7
- 5G/4G dual-mode multi-carrier cellular
- Voice survivability and POS continuity
- Attack Shield cybersecurity
- Cloud management
RabbitRun explicitly marks this model Coming Soon. Heritage does not present it as currently orderable.
Vendor specifications and positioning checked August 4, 2026. Review RabbitRun’s current product page. Heritage confirms the selected model and enabled configuration separately.
Configure the RabbitRun path
“Cellular backup” is not one behavior.
After hardware selection, the connectivity configuration determines whether a path is managed for quality, activated during recovery, or maintained as an additional available connection.
Managed Edge
RabbitRun can add voice-aware quality of service, remote management, and network visibility while the one wired connection remains a single path.
- One wired internet connection
- Managed network edge
- Optional provisioned cellular recovery
A manually activated cellular recovery option does not create automatic failover.
Dual-Wired SD-WAN
With two appropriately designed wired connections, RabbitRun monitors the paths and can move active traffic when the primary path fails.
- Primary and secondary wired connections
- Live failover between wired paths
- Quality of service and remote management
Path delivery, independence, available capacity, and configuration still need confirmation.
Persistent Cellular Backup
A provisioned cellular link can be maintained as an additional path according to the selected configuration.
- Ongoing cellular service
- Availability defined by the configuration
- Another connection type when wired paths are disrupted
Cellular signal, local conditions, capacity, and the selected service affect what the path can support.
Manual recovery is deliberately separate
With provisioned manual cellular recovery, Heritage activates the compatible cellular option remotely when requested and needed. Activation and usage charges may apply. It is a recovery process—not continuous or automatic failover.
Failure scenarios
Start with what should happen, then select the path.
Primary wired path failsDual-wired design
RabbitRun can move active traffic to the second wired path when the confirmed configuration supports live failover.
Single wired path failsManual cellular recovery
Heritage can remotely activate a provisioned compatible cellular option. This requires intervention and is not automatic failover.
Local calling paths are unavailableAlternate inbound routing
A continuity plan can define where eligible inbound calls should go when the location cannot answer normally.
Office stays connected but voice degradesQoS and visibility
Voice-aware quality of service and remote management can help manage and investigate local network contention.
Reliability design worksheet
Identify the open decisions at each location.
This worksheet gives a useful starting point without pretending that an unverified circuit or cellular path is ready for service.
Review the Design with HeritageCurrent paths
How many wired internet connections serve the location? How are they delivered? Is a cellular option already provisioned?
Required behavior
Is a manual recovery process acceptable, or must another path remain available without waiting for activation?
Call destination
If local users cannot answer, should eligible inbound calls follow a defined alternate route?
Local dependencies
Which network edge, switches, phones, and other equipment require power, and what power planning exists?
Hardware and capacity review
What traffic and concurrent feature combination must RabbitRun support? Heritage validates the workload before selecting a model or relying on an alternate path.
Common questions
Know what each option does—and what it does not do.
Is provisioned cellular recovery automatic failover?
No. The manual option requires Heritage to activate the compatible cellular path remotely when requested and needed. It must not be treated as a continuously available automatic path.
Does a second wired connection remove every single point of failure?
No. The delivery paths, local edge, power, equipment, configuration, and upstream dependencies still need review. A second service is useful only as part of a confirmed design.
Will cellular support all normal office traffic?
That cannot be assumed. Signal conditions, selected service, available capacity, and competing traffic affect suitability. Heritage confirms the intended workload for the location.
What happens to inbound calls if the office is unreachable?
The continuity plan can define an alternate inbound route for eligible calls, such as another location, team, or business calling application. The exact route is designed and tested for the customer.
Does connectivity diversity address a power failure?
Not by itself. Local equipment needs power to operate, so power and equipment dependencies must be evaluated separately from internet paths.
How is reliability service priced?
The billing shape depends on the location and confirmed configuration, plus applicable wired connectivity, cellular provisioning, activation, usage, and service charges. Heritage confirms the actual design before quoting it.
Does Heritage offer every feature RabbitRun lists?
Not by default. Vendor-listed capabilities describe the hardware platform. Heritage confirms which model, services, and compatible features belong in the selected configuration.
Plan the exception path