Call Application Server History Management Across Endpoints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IP telephony systems are limited in their ability to maintain and provide call history across multiple clients, as prior art systems only allow call history access on specific endpoints like IP phones and traditional phones, and do not support other devices such as mobile devices or web clients.
Innovation Solution
A system and method utilizing a call application server that maintains history records for users across multiple clients, including mobile devices and web clients, by using a history system and cache to provide universal access to call history information, regardless of the endpoint used, through a network of switches and various telephony devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If call history is stored locally at IP phones and traditional phones, then call history functionality is available on those specific endpoints, but call history is not accessible on other endpoints such as web clients or mobile devices
Solution Approach 1:
The call application server implements a universal history system that serves as a centralized repository accessible by all endpoint types (IP phones, traditional phones, web clients, mobile devices). The server provides multi-functional access points including history system for direct access, history cache for web clients, and integration with personal call managers, enabling any endpoint to retrieve call history regardless of its native capabilities
Solution Approach 2:
The call application server acts as an intermediary between the call processing system and various endpoints. It receives call records from the telephony system, maintains them in the history system and cache, and delivers them to requesting endpoints. This mediator architecture decouples the storage function from the access function, allowing diverse endpoints to access unified call history without requiring local storage capabilities
2Adaptability or versatility
If call history is stored at specific endpoints, then the storage requirement is minimal and simple, but the system cannot provide universal access across multiple client types
Solution Approach 1:
The history storage and access functionality is segmented into distinct modular components: the history system for centralized storage, the history cache for web client optimization, and multiple access interfaces (direct history access, personal call manager integration). This segmentation allows each component to be independently optimized while working together to provide comprehensive multi-client support
Solution Approach 2:
The system adds a new dimension to call history architecture by introducing a server-based centralized storage layer between the traditional endpoint-local storage model and the desired universal access model. This dimensional shift from distributed local storage to centralized cloud-based storage enables access from any endpoint without proportionally increasing endpoint complexity
3Loss of information
If a centralized history system is implemented on the call application server, then universal access to call history is enabled across all endpoints, but the system complexity and infrastructure requirements increase
Solution Approach 1:
The history cache pre-loads and stores call history data specifically for web clients before it is needed, reducing real-time retrieval complexity. The server proactively maintains the cache with relevant history information, so when web clients request history, the data is already prepared and readily available, reducing the computational burden during actual access operations
Data Source
AI summary
A system for providing enhanced history information across multiple clients comprises a call application server having a history system, a telephony system and a history cache. The call application server advantageously maintains a history records for each user of the system. The enhanced history system is particularly advantageous because regardless of the endpoint (e.g., phone, thin client, personal call manager or standalone IP phone) with which the user is interacting, the history information specifically for that user is delivered by the call application server to that endpoint. Furthermore, the call application server allows the user to access history information using end points which heretofore were unable to provide history functionality. Finally, the call application server makes the history records universal across all endpoints with which the user interacts, in contrast to prior art, which had limited call history information specific to a particular endpoint.