1 / 6

Understanding ENUM 2.0: Navigating Call Routing and Numbering Challenges

ENUM 2.0 addresses complex issues in voice over IP (VoIP) routing, particularly for call routing across varied numeral systems. This framework explores the need for flexible numbering plans, the significance of calling and called numbers, and the critical role of databases in ensuring seamless communication. By highlighting the limitations of source-based results and the distinct paths calls may take based on their origins, ENUM 2.0 aims to provide clarity and efficiency in call management. This evolution permits better integration of private and public databases for optimized routing.

bjorn
Download Presentation

Understanding ENUM 2.0: Navigating Call Routing and Numbering Challenges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. E2MD (ENUM-to-Doctor) I see the problem… he’s infected by the IETF!

  2. What we need • Calling-name • Key = calling number • SPID/SPN • Key = called or calling number • Send-N • Key = called number (only?) • Unused • Key = either • Source-based results • Key = called number, but “filtered” by source data (or arguably key = called + source)

  3. Requirements • Has to support variable-length/open numbering plans • Has to be in private database: all use-cases • Has to be in public database: all use-cases?

  4. Source-URI • Today, source-uri is done in private contexts only • Used for VoIP routing • Example-1: NANP local vs. long-distance calls, in North America • Example-2: transit peering arrangements

  5. Source-URI Problem • Call from A to C may need different path than from B to C, and different from A to D Database Proxy-1 Proxy-2 A B C D

  6. A Horse of a different color What if we just say “fine, it’s not The DNS”, it’s ENUM 2.0

More Related