Private Dialing Plan Call Routing via Internal Egress Path Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Challenges arise in routing calls to endpoints with numbers associated with private dialing plans, as the Dialed Number Identification Service (DNIS) does not have meaning across different carrier networks, leading to difficulties in directing calls to appropriate automatic call distributors (ACDs) in toll-free service provider call centers.
Innovation Solution
The method involves receiving an internal egress path identifier associated with the destination endpoint, routing the call over an identified egress path, and using a PDP call resolution service to select an internal egress path, which includes encoding the identifier in messages like Session Initiation Protocol (SIP), Signaling System 7 (SS7), or Primary Rate Interface (PRI), allowing the call to be routed correctly through a PDP-enabled trunk.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DNIS number is used for routing calls, then call routing can be established within the toll-free service provider network, but the DNIS does not have meaning to other carrier networks attempting to route the call
Solution Approach 1:
The patent introduces an intermediary translation mechanism between carrier networks that converts private dialing plan numbers into routable formats. This intermediary layer allows calls with PDP numbers to be routed across different carrier networks by translating the non-routable PDP number into a format that intermediate carrier networks can understand and route, thereby resolving the incompatibility between private numbering plans and public carrier network routing requirements
2Productivity
If internal egress path identifiers are used for routing, then calls can be efficiently routed to correct ACDs within the private dialing plan network, but the routing information must be translated across different network protocols
Solution Approach 1:
The patent implements a universal routing identifier system that can operate across multiple protocol domains (SS7, SIP, ISDN). The internal egress path identifier is designed to be protocol-agnostic, allowing the same routing logic to function across different carrier network protocols. This multi-functionality enables efficient call routing while reducing the complexity of protocol-specific translation by using a unified identifier format that can be mapped to various protocol requirements
Data Source
AI summary
A method for routing a call associated with a private dialing plan includes receiving a call directed to a destination endpoint associated with a private dialing plan (PDP), receiving an internal egress path identifier associated with the destination endpoint, and routing the call to an egress path identified by the egress path identifier. A system for routing a call including a destination number associated with a PDP including a routing engine operable to route the call to a PDP call resolution server, and a first switch operable to receive an egress path identifier and a PDP telephone number from the PDP call resolution server, the egress path identifier identifying an egress path for routing the call to a destination endpoint associated with the destination number, and the PDP telephone number identifying a selected PDP destination endpoint and a second switch operable to receive the call based on the egress path identifier and route the call to the selected PDP destination endpoint using the PDP telephone number.