Hybrid Cloud PBX with Dual Registration and Automatic Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
VoIP-based PBX systems are vulnerable to reliability issues due to reliance on Internet connectivity and mains power, leading to potential service disruptions and increased points of failure.
Innovation Solution
A hybrid onsite and cloud PBX system that synchronizes configuration data and media files between local and remote locations, enabling failover mechanisms to ensure continuous operation by routing calls through the PSTN when Internet service fails and allowing automatic forwarding to mobile phones or remote PBX systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If a VoIP-based PBX system is used to reduce costs, then the cost of telephone service is reduced, but the reliability of the system deteriorates due to dependence on Internet connectivity and mains power
Solution Approach 1:
The system is divided into two independent PBX instances: a local PBX and a remote cloud-based PBX. Each can operate autonomously, and phones are registered with both instances simultaneously. This segmentation allows the system to maintain functionality even when one instance becomes unavailable, resolving the reliability issue while keeping VoIP cost benefits.
Solution Approach 2:
The system pre-establishes a backup PBX instance and pre-registers phones with both local and remote PBXes before any failure occurs. Configuration data and media files are synchronized in advance between both instances. This beforehand preparation ensures that failover can occur immediately without service interruption, cushioning against potential Internet or power failures.
2Device complexity
If a single primary PBX system is used to simplify system architecture, then the device complexity is reduced, but the reliability deteriorates due to single point of failure
Solution Approach 1:
The single primary PBX is segmented into two functional instances: local PBX and remote PBX. Both instances maintain identical configuration data and can independently handle calls. This segmentation eliminates the single point of failure while keeping the architecture relatively simple through automated synchronization and failover mechanisms.
Solution Approach 2:
The system merges the functionality of primary and backup PBXes into a unified failover system. Phones are simultaneously registered with both local and remote PBXes, and the system automatically switches between them based on availability. This merging approach provides redundancy without requiring complex manual failover procedures, maintaining operational simplicity.
3Adaptability or versatility
If Internet connectivity is required for PBX operation to enable VoIP functionality, then the adaptability to modern communication protocols is improved, but the reliability worsens due to additional points of failure
Solution Approach 1:
The system introduces an intermediary PSTN connection as a mediator between the PBX system and the public telephone network. When VoIP over Internet is unavailable, the system automatically routes calls through the PSTN intermediary, ensuring continuous service. This intermediary approach maintains adaptability to modern VoIP protocols while providing a reliable fallback path that doesn't depend on Internet connectivity.
Data Source
AI summary
Disclosed is a system for telephones by providing an improved and streamlined user experience and enhanced fail over mechanisms. A decentralized system managed through a web site which allows for continued operation even when the primary systems fail includes a mechanism for restoring the primary systems automatically when they become available again. Phones connect to two PBX systems at the same time, one local and one at a remote location. The two PBX systems synchronize configuration data and media files between them. The website can also be used to manage any number of systems allowing any size organization to manage every phone system in their organization from a single interface.


