How Number Portability and ENUM Evidence Resolve Routing Disputes

Four records to separate

• The authoritative allocation and permitted use of the number range
• The portability database record at the relevant time
• The ENUM or other routing lookup performed by the originating network
• The route, handoff and response actually observed in traffic records

Questions for reconstruction

• Was the number allocated, ported, reassigned or hosted?
• Which database response did the network receive?
• Was routing based on stale, missing or incorrectly interpreted data?
• Which system selected the route and which party controlled its configuration?
• Did accessibility differ across networks or traffic types?

Why chronology matters

Current portability data cannot simply be substituted for the record that existed when the disputed traffic occurred. Configuration changes, database updates and cached responses must be aligned to the precise event timeline.

How Leo can help

Leo’s experience includes numbering, portability, ENUM implementation, routing, carrier interconnection and formal disputes concerning number accessibility. He can reconstruct the authoritative record and explain each lookup and routing decision in a reproducible sequence.