IP Library Granted Patent US 12,627,528
Granted Patent B2
US 12,627,528 · App. 18/505,548 · Granted May 12, 2026

Cloud-based call routing

Inventors: Walter F. C. Anderson (Santa Cruz, CA); Benjamin Joseph DeStephen (Hilliard, OH)
Assignee: Zoom Communications, Inc.
H04L12/66H04L65/1104H04M9/002
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 12,627,528
App. No.
18/505,548
Granted
May 12, 2026
Kind
B2
Abstract

A system includes a network and a telephony server. The network is associated with an independent carrier (IC), a native carrier, or both. The network includes a telephone gateway, an internet gateway, a first device associated with the IC, and a second device associated with the native carrier. The first device communicates with the telephone gateway. The second device communicates with the internet gateway. The telephony server is associated with the native carrier. The telephony server supports traffic from the first device and the second device. The telephony server includes a PBX and a session border controller (SBC). The SBC communicates with the telephone gateway via a session initiation protocol (SIP) trunk.

Claims (38)

1 . A method comprising:

dynamically determining, at call setup, a routing path for a call based on a real-time synchronized unified directory that maps extensions and numbers across native devices and non-native devices, wherein the unified directory is updated in real-time as unified directory mappings change;

routing the call from a first device associated with a first carrier of a network through a private branch exchange (PBX) via an internet gateway configured to communicate directly with the first device;

routing the call from a session border controller (SBC) communicatively coupled to the PBX via a session initiation protocol (SIP) trunk based on the determined routing, wherein the SBC is an intermediary that dynamically routes calls between the native devices and the non-native devices based on the unified directory; and

routing the call to a second device associated with a second carrier of the network via a call manager associated with the second carrier.

2 . The method of claim 1 , further comprising:

routing the call from the SBC to a native public switched telephone network (PSTN) when the call is destined for an external device that is not associated with the network.

3 . The method of claim 1 , wherein the second device is a native device associated with the network.

4 . The method of claim 1 , wherein the PBX is a cloud-based PBX.

5 . The method of claim 1 , wherein the second device is a voice-over-internet protocol (VoIP) device.

6 . A system, comprising:

a network associated with a first carrier and a second carrier, the network comprising:

a first device associated with the first carrier and configured to communicate with a telephone gateway; and

a second device associated with the second carrier and configured to communicate directly with an internet gateway; and

a telephony server associated with the second carrier configured to dynamically determine, at call setup, a routing path for a call based on a real-time synchronized unified directory that maps extensions and numbers across native devices and non-native devices, wherein the unified directory is updated in real-time as unified directory mappings change, the telephony server comprising:

a private branch exchange (PBX) configured to route the call from the second device via the internet gateway;

a session border controller (SBC) communicatively coupled to the PBX and configured to route the call via a session initiation protocol (SIP) trunk based on the determined routing, wherein the SBC is an intermediary that dynamically routes calls between the native devices and the non-native devices based on the unified directory; and

a call manager configured to route the call to the first device.

7 . The system of claim 6 , wherein the PBX is a cloud-based PBX system.

8 . The system of claim 6 , wherein the first device is a non-voice-over-internet protocol (VoIP) device.

9 . The system of claim 6 , wherein the second device is a voice-over-internet protocol (VoIP) device.

10 . The system of claim 6 , wherein the network further comprises a first data store configured to store first device extensions of non-native devices associated with the network.

11 . The system of claim 10 , wherein the telephony server further comprises a second data store configured to store second device extensions of native devices associated with the network.

12 . The system of claim 11 , wherein the second data store is configured to synchronize data with the first data store to create the unified directory to manage the non-native devices and the native devices.

13 . The system of claim 12 , wherein the second data store is configured to map the first device extensions to respective external contact numbers.

14 . A non-transitory computer-readable medium comprising instructions that when executed by a processor, cause the processor to perform operations comprising:

dynamically determining, at call setup, a routing path for a call based on a real-time synchronized unified directory that maps extensions and numbers across native devices and non-native devices, wherein the unified directory is updated in real-time as unified directory mappings change;

routing the call from a first device associated with a first carrier of a network through a private branch exchange (PBX) via an internet gateway configured to communicate directly with the first device;

routing the call from a session border controller (SBC) communicatively coupled to the PBX via a session initiation protocol (SIP) trunk based on the determined routing, wherein the SBC is an intermediary that dynamically routes calls between the native devices and the non-native devices based on the unified directory; and

routing the call to a second device associated with a second carrier of the network via a call manager associated with the second carrier.

15 . The non-transitory computer-readable medium of claim 14 , wherein the PBX is associated with a native network.

16 . The non-transitory computer-readable medium of claim 14 , wherein the PBX is a cloud-based PBX.

17 . The non-transitory computer-readable medium of claim 14 , wherein the operations further comprise:

routing the call to an independent carrier (IC) public switched telephone network (PSTN) when the call is destined for an external device that is not associated with the network.

18 . The non-transitory computer-readable medium of claim 14 , wherein the operations further comprise:

routing the call to the call manager of the network when the call is destined for a native device associated with the network.

19 . The non-transitory computer-readable medium of claim 14 , wherein the first device is a voice-over-internet protocol (VoIP) device.

20 . The non-transitory computer-readable medium of claim 14 , wherein the first device has a non-native carrier number.

Assignments (2)
CHANGE OF NAME Recorded Jan 7, 2025
From: ZOOM VIDEO COMMUNICATIONS, INC.
To: ZOOM COMMUNICATIONS, INC.
Reel/Frame 069839/0593 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2023
From: ANDERSON, WALTER F. C.; DESTEPHEN, BENJAMIN JOSEPH
To: ZOOM VIDEO COMMUNICATIONS, INC.
Reel/Frame 065510/0317 →