# US 2019/0320070 A1 · Hybrid Cloud PBX

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0320070 A1
- Document ID: US20190320070A1
- Status: Published application
- Kind: A1
- Application number: 16/385,705
- Filed: 2019-04-16
- Published: 2019-10-17
- Earliest claimed: 2018-04-16
- Inventors: Barrett Adams; Michael Cramer
- Web page: https://patentgrep.com/patent/US20190320070A1

## CPC

- H04M 7/0084: {Network monitoring; Error detection; Error recovery; Network testing}
- H04L 65/1055: Single-site
- H04L 65/1069: Session establishment or de-establishment
- H04M 3/12: Marking faulty circuits "busy"; Enabling equipment to disengage itself from faulty circuits {; Using redundant circuits; Response of a circuit, apparatus or system to an error}
- H04M 3/241: {for stored program controlled exchanges}
- H04M 3/42314: {in private branch exchanges}
- H04M 3/4234: {Remote access to features of PBX or home telephone systems-teleworking in a PBX}
- H04M 7/009: {in systems involving PBX or KTS networks}
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed is a system for telephones by providing an improved and streamlined user experience and enhanced fail over mechanisms. A decentralized system managed through a web site which allows for continued operation even when the primary systems fail includes a mechanism for restoring the primary systems automatically when they become available again. Phones connect to two PBX systems at the same time, one local and one at a remote location. The two PBX systems synchronize configuration data and media files between them. The website can also be used to manage any number of systems allowing any size organization to manage every phone system in their organization from a single interface.

## Claims

### Claim 1

A hybrid PBX, comprising:
an onsite PBX;
a remote PBX; and
one or more extensions,
wherein each extension of the one or more extensions is connected to both the onsite PBX and the remote PBX, and
wherein the remote PBX is operative to facilitate calls made and received by the extensions when the onsite PBX is inoperative.

### Claim 2 (depends on 1)

The hybrid PBX as recited in claim 1, wherein the local PBX and the remote PBX are connected to a VoIP gateway.

### Claim 3 (depends on 2)

The hybrid PBX as recited in claim 2, wherein the local PBX is configured to route calls through a PSTN in the event of a failure of Internet service.

### Claim 4 (depends on 1)

The hybrid PBX as recited in claim 1, further comprising a website through which the onsite PBX and the remote PBX may be configured as a single system.

### Claim 5 (depends on 1)

The hybrid PBX as recited in claim 1, further comprising a proxy server which routes calls through the onsite PBX when the onsite PBX is operative, and through the remote PBX when the onsite PBX is inoperative.

### Claim 6 (depends on 1)

The hybrid PBX as recited in claim 1, further comprising a mesh network which routes calls through either the onsite PBX or the remote PBX based on availability and load balancing.

### Claim 7

A hybrid PBX, comprising:
at least two PBXs, each PBX having at least one connection to an external telephone service provider, each connection selected from the group consisting of:
a connection to a VoIP provider, and
a connection to a PSTN;
one or more extensions, each extension having:
a primary connection to a PBX of the at least two PBXs, and
a secondary connection to another PBX of the at least two PBXs; and
a website operable by a user to configure the at least two PBXs as a single system,
wherein the at least two PBXs are operative to route calls to and from the one or more extensions.

### Claim 8 (depends on 7)

The hybrid PBX as recited in claim 7, further comprising a mesh network wherein the at least two PBXs operate as nodes in the mesh network.

### Claim 9 (depends on 8)

The hybrid PBX as recited in claim 8, wherein mesh headers are used to route calls to and from the one or more extensions.

### Claim 10 (depends on 9)

The hybrid PBX as recited in claim 9, wherein SIP headers are used to implement the mesh headers.

### Claim 11 (depends on 9)

The hybrid PBX as recited in claim 9, wherein a PBX acting as a node attempts to route a call arriving for a number outside the mesh network through a connection of the at least one connection to an external telephone service provider.

### Claim 12 (depends on 11)

The hybrid PBX as recited in claim 11, wherein the PBX adds mesh headers to the call arriving for a number outside the mesh network and routes the call to a neighboring node when it is unable to route the call to a connection of the at least one connection to an external telephone service provider.

### Claim 13 (depends on 9)

The hybrid PBX as recited in claim 9,
wherein a PBX acting as a node adds or updates mesh headers for a call arriving for a number inside the mesh network,
wherein the PBX routes the call to an extension of the one or more extensions if the PBX is the destination node, and
wherein the PBX routes the call to the destination node if the PBX is not the destination node.

### Claim 14

A hybrid PBX comprising:
a mesh network having a plurality of nodes, each node consisting of a PBX; and
at least one extension, each extension connecting to at least two nodes,
wherein the nodes are configured to route calls to and from the extensions of the at least one extension.

### Claim 15 (depends on 14)

The hybrid PBX as recited in claim 14, wherein at least one node of the plurality of nodes has at least one connection to an external telephone service provider.

### Claim 16 (depends on 15)

The hybrid PBX as recited in claim 15, wherein each connection of the at least one connection is selected from the group consisting of a connection to a VoIP provider and a connection to a PSTN.

### Claim 17 (depends on 15)

The hybrid PBX as recited in claim 15, wherein a node attempts to route a call arriving for a number outside the mesh network through a connection of the at least one connection to an external telephone service provider.

### Claim 18 (depends on 17)

The hybrid PBX as recited in claim 17, wherein the node adds mesh headers to the call arriving for a number outside the mesh network and routes the call to a neighboring node when it is unable to route the call to a connection of the at least one connection to an external telephone service provider.

### Claim 19 (depends on 18)

The hybrid PBX as recited in claim 18,
wherein the node adds or updates mesh headers for a call arriving for a number inside the mesh network,
wherein the node routes the call to an extension of the one or more extensions if the node is the destination node, and
wherein the node attempts to route the call to the destination node if the node is not the destination node.

### Claim 20 (depends on 19)

The hybrid PBX as recited in claim 19, wherein the node calls a failover number if it is unable to route the call to the destination node.
