IP Library Granted Patent US 10,623,238
Granted Patent B2
US 10,623,238 · App. 16/009,690 · Granted Apr 14, 2020

Failover system and method for IP telephony

Inventor: Kent A. Fritz (Mountain View, CA)
Assignee: Mitel Networks, Inc.
H04L41/0654H04L41/0659H04L41/0663H04L45/28H04L49/552H04L61/2007H04L65/1053H04L65/80H04L67/1034H04L69/40H04M7/0084H04M7/006
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,623,238
App. No.
16/009,690
Granted
Apr 14, 2020
Kind
B2
Abstract

A failover system includes a plurality of configuration controllers and a plurality of switches. The switches include a site proxy, a failover module and a routing table. A first site proxy of a first switch is designated as the active proxy and controls failover in the event a switch fails or otherwise becomes unavailable. A second site proxy of a second switch is designated as the backup proxy and controls failover in the event the first switch fails or otherwise becomes unavailable. In the event a switch fails or otherwise becomes available, the active proxy interacts with the configuration controller and reassigns the extensions associated with the failed switch to a different switch of the plurality of switches. If a configuration controller fails or otherwise becomes unavailable, another configuration controller becomes active and establishes communication with the plurality of switches to maintain the operational status of the IP telephony system.

Claims (48)

1. A method for failover in an IP telephony system performed by one or more computing devices, the IP telephony system comprising a plurality of networked switches each assigned to route calls and requests from different extensions, the method comprising:

attempting to route a call to an extension via a first switch;

detecting unavailability of an unavailable switch where the attempt to route the call fails because of the detected unavailability;

sending by the first switch a service request to a configuration controller, the service request including information identifying the extension and identifying the unavailable switch;

reassigning, by the configuration controller, the extension to an operational switch in response to the service request;

notifying the first switch of the reassignment; and

storing information about at least one other switch and at least one associated extension in a routing table,

wherein at least two of the networked switches each actively route calls and requests from different extensions.

2. The method of claim 1 , further comprising:

determining whether any one or more other extensions are assigned to the unavailable switch by scanning the routing table;

reassigning the one or more other extensions to one or more operational switches; and

notifying the first switch of each of the reassignments.

3. The method of claim 1 , wherein the extension is a SIP extension.

4. The method of claim 1 , further comprising waiting a predetermined amount of time before generating a failure signal after receiving an indication that the attempt to route the call has failed because of the detected unavailability.

5. The method of claim 1 , wherein notifying the first switch of the reassignment includes storing the reassignment of the extension to the operational switch in the routing table of the first switch.

6. The method of claim 1 , further comprising:

determining whether there is an additional extension associated with the unavailable switch;

sending by the first switch a respective service request for the additional extension to the configuration controller;

assigning the additional extension to the or another operational switch in response to the respective service request; and

notifying the first switch of the assignment to the or another operational switch.

7. The method of claim 1 , wherein

the configuration controller is a primary configuration controller coupled by signal lines for communication with and management of the first switch, the unavailable switch, and the operational switch, and wherein

a backup configuration controller, having a lower priority than the primary configuration controller and having a coupling to the first switch, the unavailable switch, and the operational switch, takes the place of the primary configuration controller based on failure of a server upon which the primary configuration controller operates.

8. A method for providing failover in an IP telephony system performed by one or more computing devices, the IP telephony system comprising a plurality of networked switches each assigned to route calls and requests from different extensions, the method comprising:

monitoring for failure in the IP telephony system to determining whether a switch failure has been detected;

based on a switch failure having been detected, sending by a first switch a service request to a configuration controller, the service request including information identifying an extension requiring reassignment and identifying a failed switch;

reassigning, by the configuration controller, the extension to an operational switch in response to the service request;

notifying the first switch of the reassignment; and

storing information about at least one other switch and at least one associated extension in a routing table,

wherein at least two of the networked switches each actively route calls and requests from different extensions.

9. The method of claim 8 , wherein the monitoring for failure comprises:

an active switch in the IP telephony system monitoring for failure by sending a heartbeat signal to other switches in the IP telephony system and monitoring for replies;

the active switch assessing any other switch does that not provide a reply to the heartbeat signal as having failed.

10. The method of claim 9 , further comprising waiting a predetermined amount of time after sending the heartbeat signal before generating a failure signal based on not receiving a reply to the heartbeat signal within the predetermined about of time.

11. The method of claim 8 , further comprising:

determining whether any one or more other extensions are assigned to the failed switch by scanning the routing table;

based on the determination as to whether any one or more other extensions are assigned to the failed switch, reassigning the one or more other extensions to the operational switch and/or one or more other operational switches; and

notifying the first switch of each of the reassignments.

12. The method of claim 8 , wherein the extension is a SIP extension.

13. The method of claim 8 , wherein notifying the first switch of the reassignment includes storing the reassignment of the extension to the operational switch in the routing table of the first switch.

14. The method of claim 8 , further comprising:

determining whether there is an additional extension associated with the failed switch;

sending by the first switch a respective service request for the additional extension to the configuration controller;

assigning the additional extension to the or another operational switch in response to the respective service request; and

notifying the first switch of the assignment to the or another operational switch.

15. The method of claim 8 , wherein

the configuration controller is a primary configuration controller coupled by signal lines for communication with and management of the first switch, the failed switch, and the operational switch, and wherein

a backup configuration controller, having a lower priority than the primary configuration controller and having a coupling to the first switch, the failed switch, and the operational switch, takes the place of the primary configuration controller based on failure of a server upon which the primary configuration controller operates.

Assignments (19)
SECURITY INTEREST Recorded Jun 30, 2025
From: MLN US HOLDCO LLC; MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: U.S. PCI SERVICES, LLC
Reel/Frame 071758/0843 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ACQUIOM AGENCY SERVICES LLC
To: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071730/0632 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071712/0821 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ANKURA TRUST COMPANY, LLC
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL CLOUD SERVICES, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071722/0721 →
SECURITY INTEREST Recorded Jun 20, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 071676/0815 →
SECURITY INTEREST Recorded Mar 12, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070689/0857 →
NOTICE OF SUCCESSION OF AGENCY - 4L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069896/0827 →
NOTICE OF SUCCCESSION OF AGENCY - 3L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 070006/0268 →
NOTICE OF SUCCCESSION OF AGENCY - PL Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069895/0755 →
NOTICE OF SUCCCESSION OF AGENCY - 2L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069896/0001 →
NOTICE OF SUCCESSION OF AGENCY - 5L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069897/0046 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0760 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0643 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0715 →
SECURITY INTEREST Recorded Dec 13, 2018
From: MITEL NETWORKS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047909/0814 →
SECURITY INTEREST Recorded Dec 13, 2018
From: MITEL NETWORKS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047988/0478 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 9, 2018
From: FRITZ, KENT
To: SHORETEL, INC.
Reel/Frame 046297/0990 →
CHANGE OF NAME Recorded Jul 9, 2018
From: SHORETEL, INC.
To: MITEL NETWORKS, INC.
Reel/Frame 046298/0147 →
MERGER AND CHANGE OF NAME Recorded Jul 9, 2018
From: SHORETEL, INC.; MITEL NETWORKS, INC.
To: SHORETEL, INC.
Reel/Frame 046298/0107 →