# US 11,444,985 B2 · System and method for processing telephony sessions

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

- Number: US 11,444,985 B2
- Document ID: US11444985B2
- Status: Granted
- Kind: B2
- Application number: 17/061,307
- Filed: 2020-10-01
- Published: 2021-01-21
- Granted: 2022-09-13
- Earliest claimed: 2008-04-02
- Assignees: Twilio Inc.
- Applicants: Twilio Inc.
- Inventors: Jeff Lawson; John Wolthuis; Evan Cooke
- Web page: https://patentgrep.com/patent/US11444985B2

## CPC

- H04L 65/1069: Session establishment or de-establishment
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/3247: {involving digital signatures}
- H04L 65/1013: {Network architectures, gateways, control or user entities}
- H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP]
- H04L 65/1104: Session initiation protocol [SIP]
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 69/329: in the application layer [OSI layer 7]
- H04M 1/2473: {Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) (details of API H04M7/0021)}
- H04M 7/0021: {Details of Application Programming Interfaces}
- H04M 7/003: {Click to dial services}
- H04M 7/0075: {Details of addressing, directories or routing tables}
- H04L 65/1101: Session protocols
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

## Claims

### Claim 1

A method comprising:
sending, from a device, using a uniform resource locator (URL), a request to an application, the request comprising parameters including account information and phone number information of a telephony session;
receiving, at the device and from the application, a response to the request, the response including at least one telephony instruction; and
executing, based on the at least one telephony instruction, a telephony action for the telephony session.

### Claim 2 (depends on 1)

The method of claim 1, wherein the parameters further comprise state information of the telephony session.

### Claim 3 (depends on 1)

The method of claim 1, wherein the parameters further comprise an indication of dual tone multi frequency (DTMF) digits received in the telephony session.

### Claim 4 (depends on 1)

The method of claim 1, wherein the parameters further comprise second phone number information of the telephony session.

### Claim 5 (depends on 1)

The method of claim 1, wherein the parameters further comprise a unique identifier of the telephony session.

### Claim 6 (depends on 1)

The method of claim 1, wherein the parameters further comprise a status of the telephony session.

### Claim 7 (depends on 1)

The method of claim 1, wherein the parameters further comprise a representation of a sound recording.

### Claim 8 (depends on 1)

The method of claim 1, wherein the parameters further comprise a result of a second telephony action.

### Claim 9 (depends on 1)

The method of claim 1, wherein the parameters further comprise geographic data regarding a participant in the telephony session.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
associating the URL with an endpoint.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
initiating the telephony session with the endpoint.

### Claim 12 (depends on 1)

The method of claim 1, wherein the telephony session is a voice session.

### Claim 13 (depends on 1)

The method of claim 1, wherein the telephony session is a short messaging service (SMS) session.

### Claim 14 (depends on 1)

The method of claim 1, wherein the telephony session is a multimedia messaging service (MMS) session.

### Claim 15

A call router system configured to perform operations comprising:
sending, using a uniform resource locator (URL), a request to an application, the request comprising parameters including account information and phone number information of a telephony session;
receiving, from the application, a response to the request, the request including at least one telephony instruction; and
executing, based on the at least one telephony instruction, a telephony action for the telephony session.

### Claim 16 (depends on 15)

The call router system of claim 15, wherein the parameters further comprise state information of the telephony session.

### Claim 17 (depends on 15)

The call router system of claim 15, wherein the parameters further comprise an indication of dual tone multi frequency (DTMF) digits received in the telephony session.

### Claim 18 (depends on 15)

The call router system of claim 15, wherein the parameters further comprise second phone number information of the telephony session.

### Claim 19 (depends on 15)

The call router system of claim 15, wherein the parameters further comprise a unique identifier of the telephony session.

### Claim 20 (depends on 15)

The call router system of claim 15, wherein the parameters further comprise a status of the telephony session.