US-12627528-B2 - Cloud-based call routing

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.

Inventors

• Walter F. C. Anderson
• Benjamin Joseph DeStephen

Assignees

• ZOOM COMMUNICATIONS, INC.

Dates

Publication Date

20260512

Application Date

20231109

Claims (20)

1. 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. 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. 3 . The method of claim 1 , wherein the second device is a native device associated with the network.
4. 4 . The method of claim 1 , wherein the PBX is a cloud-based PBX.
5. 5 . The method of claim 1 , wherein the second device is a voice-over-internet protocol (VoIP) device.
6. 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. 7 . The system of claim 6 , wherein the PBX is a cloud-based PBX system.
8. 8 . The system of claim 6 , wherein the first device is a non-voice-over-internet protocol (VoIP) device.
9. 9 . The system of claim 6 , wherein the second device is a voice-over-internet protocol (VoIP) device.
10. 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. 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. 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. 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. 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. 15 . The non-transitory computer-readable medium of claim 14 , wherein the PBX is associated with a native network.
16. 16 . The non-transitory computer-readable medium of claim 14 , wherein the PBX is a cloud-based PBX.
17. 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. 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. 19 . The non-transitory computer-readable medium of claim 14 , wherein the first device is a voice-over-internet protocol (VoIP) device.
20. 20 . The non-transitory computer-readable medium of claim 14 , wherein the first device has a non-native carrier number.

Description

CROSS-REFERENCE TO RELATED APPLICATION(S) This application is a continuation of U.S. patent application Ser. No. 17/162,215, filed Jan. 29, 2021, the entire disclosure of which is hereby incorporated by reference. BACKGROUND Enterprise entities rely upon several modes of communication to support their operations, including telephone, email, internal messaging, and the like. These separate modes of communication have historically been implemented by service providers whose services are not integrated with one another. The disconnect between these services, in at least some cases, requires information to be manually passed by users from one service to the next. Furthermore, some services, such as telephony services, are traditionally delivered via on-premises solutions, meaning that remote workers and those who are generally increasingly mobile may be unable to rely upon them. One solution is by way of a unified communications as a service (UCaaS) platform, which includes several communications services integrated over a network, such as the Internet, to deliver a complete communication experience regardless of physical location. SUMMARY Disclosed herein are, inter alia, implementations of systems and techniques for cloud-based private branch exchanges (PBXs). One aspect of this disclosure is a UCaaS system. The UCaaS system may include a customer network and a telephony server. The customer network may be associated with an independent carrier (IC), a native carrier, or both. The customer network may include a call manager, a telephone gateway, an internet gateway, a first device associated with the IC, and a second device associated with the native carrier. The telephone gateway may be communicatively coupled to the call manager. The first device may be configured to communicate with the telephone gateway via the call manager. The second device may be configured to communicate with the internet gateway. The telephony server may be associated with the native carrier. The telephony server may be configured to support traffic from the first device and the second device. The telephony server may include a PBX and a session border controller (SBC). The SBC may be communicatively coupled to the PBX. The SBC may be configured to communicate with the telephone gateway via a session initiation protocol (SIP) trunk. Another aspect of this disclosure is a method for routing a call over a UCaaS system. The method may include initiating the call via a non-native device. The non-native device may be associated with a customer network. The method may include routing the call through a telephone gateway of the customer network. The method may include routing the call from the telephone gateway to an SBC of a telephony server associated with a native network via a SIP trunk. Another aspect of this disclosure is a method for routing a call over a UCaaS system. The method may include initiating a call via a native device. The native device may be associated with a customer network, a native network, or both. The method may include routing the call through an internet gateway of the customer network. The method may include routing the call from the internet gateway to an SBC of a telephony server associated with the native network. The method may include routing the call from the SBC to a telephone gateway associated with the customer network via a SIP trunk. BRIEF DESCRIPTION OF THE DRAWINGS This disclosure is best understood from the following detailed description when read in conjunction with the accompanying drawings. It is emphasized that, according to common practice, the various features of the drawings are not to-scale. On the contrary, the dimensions of the various features are arbitrarily expanded or reduced for clarity. FIG. 1 is a block diagram of an example of an electronic computing and communications system. FIG. 2 is a block diagram of an example internal configuration of a computing device of an electronic computing and communications system. FIG. 3 is a block diagram of an example of a software platform implemented by an electronic computing and communications system. FIG. 4A is a block diagram of an example of a native device hybrid system. FIG. 4B is a block diagram of another example of a native device hybrid system. FIG. 5 is a block diagram of an example of a native device hybrid system configured to route a call from a native device to another native device. FIG. 6 is a block diagram of an example of a native device hybrid system configured to route a call from a native device to an external device. FIG. 7 is a block diagram of an example of a native device hybrid system configured to route a call for a native device with a non-native carrier number. FIG. 8 is a block diagram of is a block diagram of an example of a native device hybrid system configured to route a call for non-native device. FIG. 9 is a flowchart of an example of a technique for routing a call for a non-native device over a native devi