DNS Service Record Mapping for Enterprise VoIP Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In VoIP and IP networks, enterprise customers using Private Numbering Plans cannot be directly reached by callers outside the network using extension numbers or usernames, as these are not associated with E.164 standard numbers, preventing direct dialing and requiring operator assistance.

Innovation Solution

A method and apparatus that create a DNS service record mapping a customer's domain name to a service provider's sub-domain, allowing calls to be routed through a public DNS server and forwarded to the customer's endpoint device using a combination of domain name, extension number, and username, enabling direct routing without ENUM queries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If enterprise customers use Private Numbering Plan with extension numbers, then internal communication efficiency is improved, but external callers cannot directly reach the enterprise endpoints

Engineering Contradiction:
Improveinternal communication efficiencyVSAvoidexternal call accessibility
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces a DNS server as an intermediary between external callers and enterprise endpoints. The DNS server stores and resolves mappings between E.164 numbers and enterprise extension numbers or usernames, enabling external callers to directly reach internal endpoints without operator assistance. This mediator bridges the gap between the private numbering system and public telecommunication standards.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If extension numbers are not associated with E.164 standard numbers, then enterprise can use simplified internal numbering, but ENUM queries cannot resolve such numbers for external routing

Engineering Contradiction:
Improvenumbering system complexityVSAvoidexternal call routing reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring DNS service records that map enterprise domain names and extension numbers to their corresponding E.164 numbers and routing information. This advance preparation ensures that when external callers attempt to reach an enterprise endpoint, the DNS server can immediately resolve the routing without requiring real-time ENUM queries, thereby ensuring reliable external call routing while maintaining simple internal numbering.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If callers must dial main number and ask operator for connection, then network security and control are improved, but call setup time and operational complexity increase

Engineering Contradiction:
Improvenetwork controlVSAvoidcall setup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables self-service by allowing external callers to directly dial enterprise endpoints using E.164 numbers that automatically resolve to internal extension numbers through DNS queries. This eliminates the need for operator intervention in call setup, reducing call setup time and operational complexity while maintaining network control through predefined DNS routing rules and service records.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8780738B2Method and apparatus for supporting enterprise addressing in networks
Publication Date: 2014.07.15 AT&T LABS INC
  • US8780738B2 patent drawing
  • US8780738B2 patent drawing
  • US8780738B2 patent drawing

AI summary

A method and apparatus for supporting enterprise addressing in networks are disclosed. For example, the method creates a Domain Name System (DNS) service record and loading said DNS service record in a public DNS server for a customer, wherein the DNS service record supports a mapping of a domain name of the customer to a sub-domain name of a service provider. The method receives a call destined to a customer endpoint device for the customer; and forwards the call to the customer in accordance with the DNS service record.