Call Router API for Web-Based Telephony Session Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telephony technologies require specialized skills and infrastructure for development and maintenance, making it difficult for web developers to create telephony applications without significant investment in new tools and methodologies.
Innovation Solution
A system and method that allows web developers to process telephony sessions using an application layer protocol, processing telephony instructions with a call router and creating call router resources through an API, leveraging familiar web development tools and techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional telephony infrastructure and specialized tools are used, then telephony services can be deployed with reliable functionality, but the device complexity and difficulty of operation increase significantly for web developers
Solution Approach 1:
The patent introduces a telephony gateway as an intermediary component that bridges web-based applications and traditional telephony infrastructure. This gateway handles protocol conversion, call routing, and integration logic, allowing web developers to interact with telephony services through familiar web technologies while the gateway manages the complexity of underlying telephony systems.
Solution Approach 2:
The system architecture is segmented into distinct layers: a web application layer using standard technologies, a telephony gateway layer handling protocol conversion and integration, and the underlying telephony infrastructure. This segmentation allows each layer to be developed and maintained independently, reducing overall system complexity for web developers.
2Ease of manufacture
If specialized telephony development tools and methodologies are adopted, then functional telephony applications can be created, but the ease of operation deteriorates due to new skill requirements
Solution Approach 1:
The telephony gateway provides universal interfaces that work with multiple telephony protocols and platforms through a single unified API. This allows web developers to use their existing web development skills and tools across different telephony systems without needing to learn protocol-specific implementations or specialized telephony development frameworks.
Solution Approach 2:
The system copies familiar web development patterns and interfaces into the telephony domain. By presenting telephony services through standard web APIs, RESTful interfaces, and familiar programming paradigms, developers can apply their existing web development knowledge directly to telephony application creation without requiring specialized telephony training.
3Adaptability or versatility
If comprehensive telephony infrastructure is deployed, then full telephony functionality is achieved, but loss of time increases due to ongoing collocation and maintenance requirements
Solution Approach 1:
The telephony gateway implements self-service capabilities including automatic call routing based on predefined rules, dynamic configuration through web interfaces, and self-diagnosis functions. This automation reduces the need for manual collocation and maintenance interventions, allowing the system to adapt to changing requirements without requiring ongoing specialized technical support.
Solution Approach 2:
The system employs dynamic configuration capabilities where call routing rules, service parameters, and integration settings can be modified in real-time through web-based interfaces without requiring system reconfiguration or physical hardware changes. This dynamic adaptability allows the telephony service to evolve with business needs while minimizing maintenance overhead.
Data Source
AI summary
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.