On-Premises Telephony Node for Survivable Cloud Call Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based telephony services are vulnerable to outages, which disrupt the provision of advanced telephony services such as automated receptionist, call queue, and shared line group services, necessitating a solution for survivable telephony services during outages or suboptimal network connections.
Innovation Solution
Implementing an on-premises telephony node that can provide telephony services independently during cloud-based telephony server outages or poor network connections, using stored data from the telephony server and integrating with a session border controller to route calls to survivable distribution groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud-based telephony server is used to provide advanced telephony services, then service functionality and accessibility are improved, but system reliability deteriorates during outages or poor network connections
Solution Approach 1:
The system performs preliminary actions by downloading and storing telephony service data, configuration information, and call routing details on the on-premises telephony node before outages occur. This cached data enables the node to provide survivable telephony services locally when cloud connectivity is lost, maintaining service availability without real-time cloud dependency.
Solution Approach 2:
The on-premises telephony node acts as an intermediary between the cloud-based telephony server and end-user devices. During normal operation, it forwards calls to the cloud server for advanced services. During outages, it mediates by routing calls locally using stored data, bridging the gap between cloud unavailability and user service needs.
2Reliability
If on-premises telephony node is implemented for survivable services, then service availability during outages is improved, but device complexity increases
Solution Approach 1:
The on-premises telephony node is designed with multi-functionality to reduce overall system complexity. It serves multiple purposes: acting as a call router during normal operation, caching service data for offline operation, providing backup routing during outages, and maintaining local telephony functionality. This consolidation reduces the need for separate dedicated components.
Solution Approach 2:
The system creates a simplified copy of essential telephony service data and routing logic on the on-premises node rather than replicating the entire cloud-based telephony server. This selective copying maintains survivable functionality while avoiding the complexity of full system duplication.
3Duration of action of stationary object
If on-premises telephony node stores data from telephony server, then service continuity during outages is improved, but data synchronization requirements increase
Solution Approach 1:
The system performs preliminary data synchronization by periodically downloading and caching telephony service data, configuration information, and call routing details on the on-premises node before outages occur. This cached data enables the node to provide survivable telephony services locally when cloud connectivity is lost, maintaining service availability without real-time cloud dependency.
Solution Approach 2:
The system implements feedback mechanisms where the on-premises telephony node monitors cloud connectivity status and automatically updates stored data when connectivity is restored. This ensures data synchronization through feedback loops, maintaining accuracy while preserving continuity during outages.
Data Source
AI summary
An on-premises telephony node of a premises where telephony services are accessed obtains, from a telephony server, stored data associated with a network-based telephony service. The network-based telephony service includes at least one of an automated receptionist service, a call queue service, or a shared line group service. The on-premises telephony node receives an indication that the telephony server is unable to provide the network-based telephony service. The on-premises telephony node provides, in response to the indication, the network-based telephony service based on the stored data.