VoIP Fail-Safe Call Survival via Standby Component Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current VoIP systems face inefficiencies in call survival due to failure detection and recovery methods, which often result in long recovery times and user disconnection, as existing solutions either fail to detect the exact failure location or introduce additional components that can become points of failure.
Innovation Solution
Implementing a system with watchdog programs to continuously monitor and detect component failures, allowing for seamless call recovery by switching service from an active to a standby component without involving communication endpoints, ensuring uninterrupted call continuation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a monitoring server is inserted into the call path to detect and reroute calls, then call failure detection capability is improved, but system complexity increases and a new point of potential failure is introduced
Solution Approach 1:
The patent introduces a monitoring server as an intermediary component that sits between the endpoint and the call path, specifically monitoring signaling messages (SIP INVITE, 200 OK, ACK) without being part of the actual media path. This intermediary detects call failures by monitoring signaling exchanges and triggers endpoint reinitiation, thereby improving reliability while minimizing disruption to the call flow.
Solution Approach 2:
The monitoring server implements a feedback mechanism by continuously observing signaling messages between endpoints and servers, detecting when calls fail to establish or are dropped, and providing feedback to the endpoint to reinitiate the call. This closed-loop feedback system ensures automatic recovery without user intervention, resolving the contradiction between improved detection capability and system complexity.
2Reliability
If communication endpoints detect failure and reinitiate calls using backup servers, then call recovery is achieved, but recovery time increases and user experience deteriorates
Solution Approach 1:
The system performs preliminary actions by pre-configuring backup servers and pre-establishing monitoring capabilities before failures occur. The monitoring server is already in place and actively monitoring signaling messages, and backup servers are pre-positioned and ready to take over. When a failure is detected, the endpoint can immediately reinitiate the call to a backup server without delay for detection or configuration, significantly reducing recovery time.
Solution Approach 2:
The monitoring server provides immediate feedback to the endpoint when a call failure is detected, enabling the endpoint to quickly reinitiate the call. This feedback mechanism reduces the time loss by providing real-time failure detection and immediate notification, allowing the system to transition from active to standby server rapidly.
3Reliability
If standby servers are pre-positioned for failover, then call continuity is improved, but system complexity and resource requirements increase
Solution Approach 1:
The monitoring server acts as an intermediary that manages the complexity of having multiple servers. Instead of requiring complex distributed systems or peer-to-peer failure detection between multiple servers, the monitoring server centralizes the detection and coordination function. It monitors signaling messages, detects failures, and coordinates the switch from active to standby servers, thereby maintaining call continuity while managing system complexity through centralized control.
Data Source
AI summary
The present invention provides a system and method for fail-safe call survival by detecting failure of an active call serving component and switching the service over to a standby component. The system and method will prevent an existing call, whether established or to be established, from being dropped due to a single point of failure within a Voice over Internet Protocol system. The continuation of the call is based on the failed component as opposed to relying on communication endpoints to re-initiate or re-route the failed call. Call recovery is initiated independent from the call path of a call. The detection of a condition or need for call recovery and the determination to initiate call recovery procedures are made without involving endpoints or intermediate points of the call. The availability and sanity of all components are continuously monitored and are tailored specifically for the duties of each component.