How It Works

This diagram describes how ENUMPlus acts as a hub for all major query sources. When a call is initiated - the PBX (in this case Asterisk) sends a secure HTTP request to the ENUMPlus API. The API then checks its local database for the associated route for the given phone number (DID). If the record is found the route is sent back to the PBX and a query success message is whispered to the caller before the call is terminated. If the record is not found in the ENUMPlus database, the API checks all top ENUM query sources (using DNS NAPTR records (traditional ENUM)) and returns the first record it finds. This record is stored locally for faster lookups in the future. If no record is found the API returns no result and the call proceeds as usual without notification. This entire process takes just milliseconds and is very reliable.

ENUMPlus Topology

Procedural Flowchart


ENUMPlus FlowChart

Terminology

If you are new to the concept of electronic number mapping - you might want to take a look at the following links.