Seamless VoIP Call Transfer via Telephony Application Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current voice over IP (VOIP) call transfer methods interrupt communication by disconnecting and reconnecting the call path, taking several seconds and only allowing 'push' functionality, where the active device initiates the transfer without enabling 'pull' functionality for seamless call handover.
Innovation Solution
Implementing a system and method that allows seamless call transfer and connection between devices using a telephony application server (TAS) to facilitate communication sessions, enabling 'pull' functionality by sending a reinvitation request to the original device, allowing the call to be transferred without noticeable interruption, and supporting the connection of additional devices to existing sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional VOIP call transfer methods are used, then call transfer functionality is provided, but communication is interrupted and latency increases
Solution Approach 1:
The system performs preliminary actions by establishing the call connection between the third device and the second device before terminating the original connection. The telephony application server maintains the session state and prepares the connection path in advance, allowing seamless handover without interrupting the audio stream. This preliminary setup ensures that when the transfer occurs, there is no noticeable gap in communication.
Solution Approach 2:
The telephony application server acts as an intermediary that manages the call session between multiple devices. It coordinates the connection establishment, maintains session state, and orchestrates the seamless transfer by mediating between the first device, second device, and third device. The server's session management capabilities allow it to handle the transition without requiring the end devices to directly manage the complex handover logic.
2Adaptability or versatility
If push functionality is implemented for call transfer, then the active device can initiate transfer, but pull functionality is not available
Solution Approach 1:
The system implements universal call transfer functionality that supports both push and pull operations. The telephony application server provides a unified interface that can handle transfer requests regardless of whether the initiating device is currently active in the call. The session management mechanism is designed to accommodate multiple transfer scenarios (push, pull, seamless handover) through a single flexible architecture, enabling devices to both initiate transfers and receive transferred calls equally.
3Adaptability or versatility
If additional devices are connected to existing sessions, then communication versatility improves, but session management complexity increases
Solution Approach 1:
The telephony application server serves as a central intermediary that manages complex multi-device sessions. It maintains session state information for all participating devices, coordinates communication paths, and handles the logic for adding or removing devices from sessions. This centralized session management approach shields individual devices from the complexity of managing multiple concurrent connections, allowing versatile multi-device communication while keeping device-level complexity low.
Data Source
AI summary
Various embodiments relate to a portable user device including: a wireless transceiver; wherein the portable user device is configured to send a request, via the wireless transceiver, to replace a first user communication device in a communication session between the first user communication device and a second user communication device in response to receiving an indication of the communication session; and via the wireless transceiver, establishing a communication connection with the second user communication device in response to receiving, via the wireless transceiver, an agreement to the request.