Call Control Engine Segments VoIP Routing Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementing and updating customized services for large clients with many telephone accounts and numbers on data-communications platforms is a significant undertaking, requiring efficient call routing and control solutions.
Innovation Solution
A data-communications server with call-routing logic and a call control engine that processes documents in a high-level programming language to generate routing instructions, allowing for customizable call flow control and integration with various data sources, providing scalable and flexible VoIP services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized services are implemented for large clients with many telephone accounts, then service customization capability is improved, but implementation and updating complexity increases significantly
Solution Approach 1:
The system segments call routing logic into modular components: call routing logic handles basic call routing, while a separate call control engine with XML-based scripting handles customized service logic. This segmentation allows independent development, deployment, and updating of customization features without affecting core routing functionality, thereby reducing overall implementation complexity while maintaining high adaptability.
Solution Approach 2:
An XML-based intermediary scripting language is introduced as a mediator between customer service requirements and system implementation. The call control engine parses and executes XML documents that define customized call flow, acting as an intermediary layer that translates high-level service customization needs into executable routing instructions without requiring direct modification of underlying system code.
2Adaptability or versatility
If manual configuration of call routing for each customer account is performed, then service customization is achieved, but time and resources required for implementation increase
Solution Approach 1:
The system implements preliminary action through pre-defined XML templates and schemas that encapsulate common call routing patterns and service logic. These templates are prepared in advance and can be quickly instantiated and customized for different customer accounts, eliminating the need to build routing logic from scratch for each new service configuration.
Solution Approach 2:
The system enables copying of existing call routing configurations and XML service definitions across multiple customer accounts. Once a customized call flow is defined and validated for one account, it can be replicated and adapted for similar accounts, dramatically reducing the time and effort required for implementation while maintaining service customization capability.
3Adaptability or versatility
If customers can directly modify VoIP server documents to configure call flow, then flexibility is improved, but system integrity and security are compromised
Solution Approach 1:
The XML-based call control engine serves as a secure intermediary that mediates between customer configuration needs and the underlying VoIP server system. Customers configure call flow through XML documents that are parsed and executed by the engine, which enforces validation rules and security constraints. This intermediary layer provides flexibility for customization while protecting system integrity by preventing direct modification of core server documents.
Solution Approach 2:
The system enables self-service configuration through XML templates and documentation that guide customers in defining their own call routing logic without requiring access to or knowledge of underlying server code. The call control engine automatically parses these XML configurations and translates them into executable routing instructions, allowing customers to maintain flexibility while the system preserves security and integrity through automated validation and isolation.
Data Source
AI summary
Aspects are directed toward use of data communications server(s) and a Platform as a Service (PaaS) interface to provide remote services for endpoint devices of a plurality disparate client entities. In one example, an apparatus includes a computing server to provide data communications for a plurality of endpoint devices respectively associated with a plurality of disparate client entities according to and responsive to client-specific sets of control data. The apparatus also includes a processing circuit configured to adjust routing of the communications by the computing server, in response to call event data generated by the computing server, by generating the client-specific sets of control data for each client entity according to a respective set of directives.