# US 2020/0404102 A1 · System and method for providing carrier-independent voip communication

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

- Number: US 2020/0404102 A1
- Document ID: US20200404102A1
- Status: Published application
- Kind: A1
- Application number: 17/013,483
- Filed: 2020-09-04
- Published: 2020-12-24
- Earliest claimed: 2007-08-10
- Assignees: Fonality, Inc.
- Applicants: Fonality, Inc.
- Inventors: Christopher M. Lyman
- Web page: https://patentgrep.com/patent/US20200404102A1

## CPC

- H04M 7/0057: {Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network}
- H04L 61/106: across networks, e.g. mapping telephone numbers to data network addresses
- H04L 65/1069: Session establishment or de-establishment
- H04L 67/104: Peer-to-peer [P2P] networks
- H04M 1/2535: {adapted for voice communication over an Internet Protocol [IP] network (Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16)}
- H04M 7/006: {Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer (H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42)}
- H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)}
- H04L 2101/33: containing protocol addresses or telephone numbers
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 52/288: {taking into account the usage mode, e.g. hands-free, data transmission or telephone}
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods for seamlessly providing carrier-independent VoIP calls initiated using an existing carrier-issued telephone number are provided. In exemplary embodiments, the existing carrier-issued telephone number to be called is received. Subsequently, a status regarding if the existing carrier-issued telephone number is a registered telephone number stored in a carrier-independent database is determined. If the existing carrier-issued telephone number comprises a registered telephone number in the carrier-independent database, a call is established via peer-to-peer connection using an address associated with the registered telephone number. However, if the existing carrier-issued telephone number is not a registered telephone number in the carrier-independent database, the call is placed via a standard route.

## Claims

### Claim 1

A method comprising:
serving, by a server, a graphical user interface (GUI) to a first client operated by a first user, wherein the GUI includes depicts a form having a set of user input elements configured for receiving a set of user inputs by the first user;
receiving, by the server, the set of user inputs from the first client;
formulating, by the server, a set of parameters for a communication, wherein the set of parameters is based on the set of user inputs;
causing, by the server, the communication to occur based on the set of parameters, wherein the communication is between the first client operated by the first user and a second client operated by a second user, wherein the communication occurs based on:
receiving, by the server, a first telephone number from the first client as input by the first user;
searching, by the server, a database for a second telephone number matching the first telephone number in value;
locating, by the server, the second telephone number in the database;
identifying, by the server, an electronic address corresponding to the second telephone number in the database;
causing, by the server, the communication to be placed from the first client to the second client based on the electronic address via a peer-to-peer connection between the first client and the second client via the server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the communication occurs further based on:
causing, by the server, the communication to be placed from the first client to the second client not via the peer-to-peer connection based on not locating, by the server, the second number in the database.

### Claim 3 (depends on 1)

The method of claim 1, wherein the set of parameters includes at least one of a dial string, a description, a type, or a primary route.

### Claim 4 (depends on 1)

The method of claim 1, wherein the set of parameters includes a preset number that the first user first dials to make the communication over the peer-to-peer connection.

### Claim 5 (depends on 1)

The method of claim 1, wherein the communication occurs further based on:
testing, by the server, the peer-to-peer connection such that a determination whether a user specification is acceptable occurs.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
causing, by the server, the communication to be placed from the first client to the second client not via the peer-to-peer connection based on the user specification being not acceptable.

### Claim 7 (depends on 1)

The method of claim of claim 1, wherein the peer-to-peer connection is a 3rd party VoIP connection.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first telephone number is a lookup key in the database.

### Claim 9 (depends on 1)

The method of claim 1, wherein the server is a iPBX server.

### Claim 10 (depends on 1)

The method of claim 1, wherein the database is a first database, wherein the first database is updateable off a second database remote to the server such that the first database contains a copy of the second database.

### Claim 11

A system comprising:
a server programmed to:
serve a graphical user interface (GUI) to a first client operated by a first user, wherein the GUI includes depicts a form having a set of user input elements configured for receiving a set of user inputs by the first user;
receive the set of user inputs from the first client;
formulate a set of parameters for a communication, wherein the set of parameters is based on the set of user inputs;
cause the communication to occur based on the set of parameters, wherein the communication is between the first client operated by the first user and a second client operated by a second user, wherein the communication occurs based on:
receive a first telephone number from the first client as input by the first user;
search a database for a second telephone number matching the first telephone number in value;
locate the second telephone number in the database;
identify an electronic address corresponding to the second telephone number in the database;
cause the communication to be placed from the first client to the second client based on the electronic address via a peer-to-peer connection between the first client and the second client via the server.

### Claim 12 (depends on 11)

The system of claim 11, wherein server is programmed for the communication to occur further based on:
causing the communication to be placed from the first client to the second client not via the peer-to-peer connection based on not locating the second number in the database.

### Claim 13 (depends on 11)

The system of claim 11, wherein the set of parameters includes at least one of a dial string, a description, a type, or a primary route.

### Claim 14 (depends on 11)

The system of claim 11, wherein the set of parameters includes a preset number that the first user first dials to make the communication over the peer-to-peer connection.

### Claim 15 (depends on 11)

The system of claim 11, wherein the server is programmed for the communication occurs further based on:
testing the peer-to-peer connection such that a determination whether a user specification is acceptable occurs.

### Claim 16 (depends on 15)

The system of claim 15, wherein the server is further programmed to:
cause the communication to be placed from the first client to the second client not via the peer-to-peer connection based on the user specification being not acceptable.

### Claim 17 (depends on 11)

The system of claim of claim 11, wherein the peer-to-peer connection is a 3rd party VoIP connection.

### Claim 18 (depends on 11)

The system of claim 11, wherein the first telephone number is a lookup key in the database.

### Claim 19 (depends on 11)

The system of claim 11, wherein the server is a iPBX server.

### Claim 20 (depends on 11)

The system of claim 11, wherein the database is a first database, wherein the first database is updateable off a second database remote to the server such that the first database contains a copy of the second database.