Centralized PBX Configuration for Seamless Server Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current hosted PBX systems face challenges in providing cost-effective and high availability due to the need for redundant hardware and complex reconfiguration processes when a PBX server fails, leading to increased costs and significant downtime.
Innovation Solution
A system architecture where PBX systems retrieve configuration data from a central database, with telephony devices and PSTN gateways automatically updating their configurations based on customer-specific routing information, allowing seamless customer migration between PBX servers without manual reconfiguration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standby PBX servers are provisioned to take over failed servers, then system availability is improved, but hardware costs and operational costs double
Solution Approach 1:
The patent uses virtualization to create virtual copies of PBX server functions on shared physical hardware. Instead of provisioning physical standby servers, virtual PBX instances can be rapidly instantiated on available hardware resources, providing failover capability without duplicating physical hardware for each server.
Solution Approach 2:
The patent implements a pooled hardware infrastructure where physical servers can serve multiple virtual PBX instances simultaneously. A single physical server can host multiple virtual PBX functions, allowing the same hardware to serve multiple customers or service functions, thereby reducing the total quantity of hardware needed while maintaining availability through virtualization-based failover.
2Reliability
If customers are moved to other PBX servers upon failure, then system availability is maintained, but reconfiguration effort and downtime increase significantly
Solution Approach 1:
The patent pre-configures virtual PBX instances with standardized templates and profiles stored centrally. When failover is needed, the system can rapidly provision a replacement virtual instance using pre-defined configuration templates, eliminating the need for manual reconfiguration during the failover process and significantly reducing downtime.
Solution Approach 2:
The patent implements automated failover mechanisms where the system self-manages the migration of customer assignments from failed to standby virtual PBX instances. The centralized management system automatically detects failures, provisions replacement instances, and updates customer routing without human intervention, minimizing both downtime and reconfiguration effort.
3Reliability
If individual reconfiguration of PBX servers, telephony devices, and PSTN gateways is performed, then service continuity is restored, but operational complexity and cost increase
Solution Approach 1:
The patent consolidates the management of PBX servers, telephony devices, and PSTN gateways into a single centralized management system. This unified system can simultaneously update multiple components with a single configuration action, eliminating the need for separate individual reconfiguration of each device type and significantly reducing operational complexity.
Solution Approach 2:
The patent implements automated configuration propagation where the centralized management system automatically distributes configuration updates to all affected PBX servers, telephony devices, and PSTN gateways. The system self-manages the entire reconfiguration process across multiple device types without requiring manual intervention for each individual component, reducing both complexity and operational cost.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A hosted PBX system architecture comprising a number of PBX-systems (C.1) all running with an identical configuration loaded from the central database (C.8), one or more provisioning services (C.2) for the telephony devices (C.3), retrieving their data from the database (C.8), one or more broadband connections (C.4) to a customer (C.0), one or more telephony devices (C.3) at each customer site (C.0), retrieving their configuration data from the provisioning service (C.2), one or more name services (C5), loading their routing information from the central database (C.8), one or more PSTN-gateways (C.6), retrieving the routing information for an inbound call for a given customer from the name service (C.5), one or more broadband connections (C.7) between the PSTN-gateways (C.6) and the PBX-systems (C.1), and one central database (C.8), which can alternatively be represented by several replicated instances of one central master database.