IPBX Server Call Status Restoration via Pseudo-Event Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IPBX systems face challenges in efficiently routing calls and managing call statuses, particularly when switchboard interfaces are reset or reconnect, leading to loss or incorrect status updates of pending calls.
Innovation Solution
The implementation of a presence detection circuit within the IPBX server that receives activity data and event messages to determine user presence statuses and provide pseudo-event messages to restore call statuses when new subscriptions are initiated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If switchboard interfaces are reset or reconnect in existing IPBX systems, then the system can recover from interface failures, but call status information is lost or becomes incorrect
Solution Approach 1:
The server preserves call status information in memory before interface reset occurs, and proactively restores this information by sending pseudo-event messages when the interface reconnects, preventing information loss during the recovery process
Solution Approach 2:
Pseudo-event messages serve as an intermediary mechanism that bridges the gap between interface reset and reconnection, carrying preserved call status information from the server to the recovered switchboard interface
2Speed
If the IPBX server sends event messages to switchboard interfaces, then call status updates are provided in real-time, but the system cannot restore historical call status after interface reset
Solution Approach 1:
The server maintains historical call status information in memory before interface reset, allowing it to restore this information after reconnection by sending pseudo-event messages that replay historical status updates
Solution Approach 2:
The server creates pseudo-event messages that are copies of the original event messages, containing historical call status information that can be restored to the switchboard interface after reset without requiring real-time updates
3Loss of information
If the system maintains call status information continuously, then status restoration after reset is possible, but memory usage and system complexity increase
Solution Approach 1:
The patent extracts only the essential call status information that needs to be preserved into a separate data structure, rather than maintaining complete system state, reducing memory overhead while enabling restoration of critical information
Solution Approach 2:
The system changes the state representation of call information from full real-time monitoring to preserved key parameters that can be restored via pseudo-event messages, reducing complexity while maintaining restoration capability
Data Source
AI summary
Apparatus and methods concerning routing of calls in client-configured set of servers, such as a web-server configured to host a switchboard interface are disclosed. As an example, one apparatus includes such a hosting web-server configured to route VoIP calls for a plurality of end-users having respective VoIP-enabled devices communicatively coupled to the web-server via a network. A user-activity detection circuit is communicatively coupled to the web-server. The user-activity detection circuit is configured to receive activity data indicating activity of end-users in a virtual office environment and receive event messages indicating statuses of pending calls in the web-server. The user-activity detection circuit determines user-activity statuses of the end-users based on received activity data and event messages. A computing server is to provide a set of services for one or more of the plurality of users as a function of the determined user-activity statuses of the end-user.