Cloud PBX Call Routing for Native and Legacy Carrier Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise customers upgrading to cloud PBX systems face compatibility issues and differences in call quality between native and non-native devices due to the lack of support for legacy phone number assignments and carrier support in conventional cloud PBX systems, leading to separate processing and routing requirements.
Innovation Solution
A hybrid system is implemented that routes calls between various combinations of native and non-native devices using a cloud-based PBX, incorporating a telephony server with a session border controller (SBC) and SIP trunk communication, enabling seamless integration and management of both types of devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional cloud PBX system is implemented, then modern communication services are provided, but legacy phone number assignments and carrier support are not compatible
Solution Approach 1:
A session border controller (SBC) is introduced as an intermediary component between the cloud PBX system and legacy telephony networks. The SBC translates and mediates communication protocols, enabling seamless interaction between modern VoIP devices and traditional PSTN devices without requiring changes to the core cloud PBX architecture.
Solution Approach 2:
The system is segmented into distinct functional components: a cloud PBX core for modern VoIP services, an SBC layer for protocol translation and carrier interfacing, and separate support pathways for native and non-native devices. This segmentation allows each component to specialize in specific functions while maintaining overall system compatibility.
2Reliability
If separate processing and routing is implemented for native and non-native devices, then carrier compatibility is maintained, but call routing complexity increases
Solution Approach 1:
The session border controller is designed as a universal intermediary that handles multiple device types (native and non-native) through a single unified interface. It performs multiple functions including protocol translation, carrier routing, and device registration, eliminating the need for separate processing systems while maintaining carrier compatibility.
Solution Approach 2:
The SBC acts as a smart mediator that automatically determines the appropriate routing path for each call based on device type and carrier requirements, abstracting away the routing complexity from end users and simplifying the overall system operation.
3Adaptability or versatility
If on-premises telephony solutions are used, then legacy system support is maintained, but remote workers and mobile users cannot access services
Solution Approach 1:
The patent replaces the mechanical on-premises PBX hardware system with a cloud-based virtualized PBX system delivered over IP networks. This substitution enables access from any location with internet connectivity while maintaining all traditional telephony functions, effectively eliminating the geographical constraints of on-premises systems.
Solution Approach 2:
The system transitions from a location-bound physical infrastructure to a network-delivered service model, adding the dimension of remote accessibility. Users can now access telephony services from any device anywhere in the world, transforming the service from a fixed-location utility to a mobile, cloud-based platform.
Data Source
AI summary
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.