IP Library Granted Patent US 9,106,452
Granted Patent B2
US 9,106,452 · App. 12/980,847 · Granted Aug 11, 2015

Cloud VoIP system with bypass for IP media

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 9,106,452
App. No.
12/980,847
Granted
Aug 11, 2015
Kind
B2
Abstract

The cloud computing VoIP system includes a software as a service (SaaS) site and one or more additional sites. The SaaS site includes a gateway and a call manager and is coupled for communication across an IP network and the PSTN. The call manager includes a media monitoring module, a bypass module, a PSTN control module and a GUI module. The SaaS site handles and controls voice and video calls over the IP network and the PSTN for endpoints at the one or more additional sites. In another embodiment, the cloud computing VoIP system is also coupled to a cellular network and the endpoints include an associated cellular phone. The cloud computing VoIP system also includes a method for falling back to a secondary network, namely the cellular network, when there is insufficient quality on a primary network.

Claims (64)

1. A computer-implemented method comprising:

sending a first test signal to a first endpoint at a first site;

sending a second test signal to a second endpoint at a second site;

receiving quality of service data from the first endpoint;

receiving quality of service data from the second endpoint;

determining an issue with a connection based on the quality of service data received from the first endpoint and the second endpoint;

responsive to determining the issue, determining whether a connection to the first site is a source of congestion;

responsive to determining that the source of congestion is not the connection to the first site, determining whether a connection to the second site is the source of congestion; and

routing the connection based on the determination of the source of congestion.

2. The method of claim 1 , further comprising:

in response to determining that the source of congestion is the connection to the first site, routing the connection to a bypass path.

3. The method of claim 1 , further comprising:

in response to determining that the source of congestion is the connection to the second site, routing the connection to a bypass path.

4. The method of claim 1 , further comprising:

in response to determining that the source of congestion is not the connection to the second site, determining whether a connection to a third site is the source of congestion.

5. The method of claim 4 , further comprising:

in response to determining that the source of congestion is the connection to the third site, routing the connection to a bypass path.

6. The method of claim 4 , further comprising:

in response to determining that the source of congestion is not the connection to the third site, sending a subsequent test signal.

7. The method of claim 4 , wherein the third site is a shared site.

8. The method of claim 4 , wherein the third site is a Software as a Service (SaaS) site.

9. The method of claim 1 , wherein sending the first and second test signals is performed by a call manager.

10. The method of claim 9 , further comprising:

directing an initial test signal to be sent from the first endpoint at the first site to the second endpoint at the second site before sending, by the call manager, the first and second test signals.

11. The method of claim 9 , further comprising:

directing an initial test signal to be sent from the second endpoint at the second site to the first endpoint at the first site before sending, by the call manager, the first and second test signals.

12. The method of claim 1 , wherein the quality of service data is sent to a call manager.

13. A system comprising:

a processor, and;

a memory storing instructions that, when executed by the processor, cause the system to:

send a first test signal to a first endpoint at a first site;

send a second test signal to a second endpoint at a second site;

receive quality of service data from the first endpoint;

receive quality of service data from the second endpoint;

determine an issue with a connection based on the quality of service data received from the first endpoint and the second endpoint;

determine whether a connection to the first site is a source of congestion in response to determining the issue;

determine whether a connection to the second site is the source of congestion in response to determining that the source of congestion is not the connection to the first site and

route the connection based on the determination of the source of congestion.

14. The system of claim 13 , wherein the memory also stores instructions that, when executed, cause the system to:

route the connection to a bypass path in response to determining that the source of congestion is the connection to the first site.

15. The system of claim 13 , wherein the memory also stores instructions that, when executed, cause the system to:

route the connection to a bypass path in response to determining that the source of congestion is the connection to the second site.

16. The system of claim 13 , wherein the memory also stores instructions that, when executed, cause the system to:

determine whether a connection to a third site is the source of congestion in response to determining that the source of congestion is not the connection to the second site.

17. The system of claim 16 , wherein the memory also stores instructions that, when executed, cause the system to:

route the connection to a bypass path in response to determining that the source of congestion is the connection to the third site.

18. The system of claim 16 , wherein the memory also stores instructions that, when executed, cause the system to:

send a subsequent test signal in response to determining that the source of congestion is not the connection to the third site.

19. The system of claim 13 , wherein the quality of service data is sent to a call manager.

20. A non-transitory computer readable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

send a first test signal to a first endpoint at a first site;

send a second test signal to a second endpoint at a second site;

receive quality of service data from the first endpoint;

receive quality of service data from the second endpoint;

determine an issue with a connection based on the quality of service data received from the first endpoint and the second endpoint;

determine whether a connection to the first site is a source of congestion in response to determining the issue;

determine whether a connection to the second site is the source of congestion in response to determining that the source of congestion is not the connection to the first site; and

route the connection based on the determination of the source of congestion.

21. The computer readable medium of claim 20 , wherein the computer readable program when executed on a computer further causes the computer to:

determine the source of congestion includes determining whether a connection to a third site is the source of congestion; and

route the connection to a bypass path in response to determining that the source of congestion is the connection to the third site.

22. The computer readable medium of claim 20 , wherein the quality of service data is sent to a call manager.

23. The computer readable medium of claim 21 , wherein the third site is a shared site.

24. The computer readable medium of claim 21 , wherein the third site is a Software as a Service (SaaS) site.

Assignments (13)
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 Feb 14, 2023
From: RINGCENTRAL, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062973/0194 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 28, 2022
From: MITEL NETWORKS, INC.
To: RINGCENTRAL, INC.
Reel/Frame 059764/0372 →
RELEASE OF SECURITY INTEREST Recorded Jan 19, 2022
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: MITEL NETWORKS, INC.
Reel/Frame 058697/0693 →
RELEASE OF SECURITY INTEREST Recorded Jan 19, 2022
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
To: MITEL NETWORKS, INC.
Reel/Frame 058697/0751 →
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 →
RELEASE OF SECURITY INTEREST Recorded Dec 3, 2018
From: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
To: SHORETEL, INC.
Reel/Frame 047713/0843 →
MERGER AND CHANGE OF NAME Recorded Oct 15, 2018
From: MITEL NETWORKS, INC.; SHORETEL, INC.
To: SHORETEL, INC.
Reel/Frame 047239/0183 →
CHANGE OF NAME Recorded Oct 15, 2018
From: SHORETEL, INC.
To: MITEL NETWORKS, INC.
Reel/Frame 047239/0088 →
RELEASE OF SECURITY INTEREST Recorded Sep 25, 2017
From: SILICON VALLEY BANK
To: SHORETEL, INC.
Reel/Frame 043993/0430 →
SECURITY INTEREST Recorded Sep 25, 2017
From: SHORETEL, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 043829/0711 →
SECURITY INTEREST Recorded Oct 23, 2014
From: SHORETEL, INC.
To: SILICON VALLEY BANK
Reel/Frame 034038/0741 →