Dual Call Manager Registration for SIP Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing SIP call management systems experience prolonged unavailability and increased service delays due to the time-consuming process of detecting proxy unavailability and switching to backup proxies, which affects user phone service continuity and efficiency.

Innovation Solution

Implementing a dual-call manager registration system where endpoints connect to both primary and secondary call managers, sending keep-alive signals to ensure quick failover and failback processes, minimizing service disruptions and maintaining call session continuity through multiple call control and configuration management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the phone uses Domain Name Servers to detect proxy unavailability, then the system can provide backup proxy functionality, but the detection time is considerable and increases phone unavailability

Engineering Contradiction:
Improveproxy availability detectionVSAvoidphone unavailability time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by having the phone maintain continuous connections to both primary and backup proxies and sending periodic keep-alive signals to both. This preliminary setup and monitoring eliminates the need for time-consuming Domain Name Server queries when failure occurs, as the backup proxy is already identified and ready for immediate failover.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the phone attempts to connect to backup proxy when original proxy fails, then service continuity can be maintained, but the process takes additional time using Domain Name Servers

Engineering Contradiction:
Improveservice continuityVSAvoidfailover time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The phone performs preliminary action by pre-establishing connections to both primary and backup proxies and continuously sending keep-alive signals to both. When the primary proxy fails, the backup proxy is already identified and connected, enabling immediate failover without time-consuming Domain Name Server queries.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by having the phone continuously send keep-alive signals to both primary and backup proxies and monitoring their responses. This feedback mechanism enables real-time detection of proxy failures and triggers immediate failover to the backup proxy, significantly reducing service disruption time.

Inventive Principle:
Principle #23Feedback

3Reliability

If the phone maintains connection with multiple call managers, then failover capability is improved, but system complexity increases

Engineering Contradiction:
Improvecall manager availabilityVSAvoidregistration system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by having the phone simultaneously register with and maintain connections to both primary and backup call managers before any failure occurs. This pre-established dual connection architecture simplifies the failover process, as the phone only needs to switch registration between the two pre-configured call managers rather than performing complex discovery and registration procedures during failure events.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8223926B2Resilient registration with a call manager
Publication Date: 2012.07.17 CISCO TECHNOLOGY INC
  • US8223926B2 patent drawing
  • US8223926B2 patent drawing
  • US8223926B2 patent drawing

AI summary

Registering with a call manager includes connecting to a first call manager and a second call manager. The endpoints register with the first call manager and send keep-alive signals to the first call manager and the second call manager. If a failure is detected in the first call manager, the system initiates a failover process. The endpoints re-register with the first call manager when the first call manager regains operability.