Gateway Transfer System for Failed Call Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Voice portals often fail to handle transferred calls between different networks, leading to significant delays and dropped calls due to the lack of mechanisms for routing failed transfers back to the originating network, especially between circuit switched and VoIP networks.
Innovation Solution
A gateway transfer system that utilizes DNIS information and other call attributes to map failed calls to alternate destinations, prioritizing based on distance, time, and utilization, and includes modules for monitoring, mapping, and transferring calls to manage failed transfers and prioritize call routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a gateway transfers a call to a voice portal in a second network, then the call can be handled by specialized services, but the call may experience significant delays or be dropped if the voice portal is unavailable
Solution Approach 1:
The system performs preliminary actions by monitoring the availability status of voice portals before transferring calls. The gateway maintains knowledge of which voice portals are currently available through proactive status checking, allowing it to make informed transfer decisions and avoid transferring calls to unavailable destinations, thereby preventing delays and dropped calls.
Solution Approach 2:
The system implements feedback mechanisms where the gateway receives status information about voice portal availability and uses this feedback to dynamically adjust its call transfer decisions. When a voice portal becomes unavailable, the gateway receives feedback about this status and can redirect calls to alternative destinations or maintain them on the originating network, ensuring reliable call delivery without unnecessary delays.
2Adaptability or versatility
If a gateway lacks a mechanism to handle failed transfer calls, then the gateway structure remains simple, but failed calls cannot be routed back to the originating network
Solution Approach 1:
The gateway is designed with multi-functionality to handle both successful and failed call transfers using a single device. The same gateway infrastructure that performs call transfers also monitors transfer outcomes and executes fallback routing decisions. This universal approach allows the gateway to provide failed call handling capabilities without requiring separate specialized equipment, thus increasing adaptability while controlling complexity.
Solution Approach 2:
The gateway implements self-service capabilities by autonomously monitoring its own transfer call status and automatically making routing decisions when transfers fail. The system uses its existing resources and information to detect failed transfers and redirect calls back to the originating network without requiring external intervention or complex additional mechanisms, thereby achieving failed call handling with minimal added complexity.
Data Source
AI summary
Techniques for providing a gateway transfer mechanism are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method, comprising identifying, at a gateway, a call to be routed to a first location, determining whether to transfer the call to a second location, in the event the call is to be transferred to the second location, transferring the call, wherein transferring the call comprises ending a process to route the call to the first location, generating transfer information for the second location, and transferring the call to the second location using the generated transfer information.