nanog mailing list archives
Re: phone fun, was GeoIP database issues and the real world consequences
From: "John Levine" <johnl () iecc com>
Date: 13 Apr 2016 21:52:23 -0000
Is there the equivalent of BGP for number portability where every telco has the full table of who owns each prefix as well as individual routes for ported numbers ?
Not really. There's a switch database used for routing calls, but that's different from LNP which is a layer sort of above that.
Or is there a central database that is consulted before a dialed number starts to be connected so originating telco knows to send call ?
Often, if the switch can't tell that the number hasn't been ported.
Or does the originating telco route the call to the original onwer of the prefix and lets that original owner figure out how to terminate the call ?
That's called Onward Routing. They do it some places but not in North America. See RFC 3482 for a well written overview of number portability.
From a long distance billing point of view, if Bell Canada connects to a number originally onwed by AT&T but ported to Verizon, with whom would Bell share long distance revenues ?
They pay whatever long distance company they use, and that company pays the owner of the switch to which it's delivered. The long distance company also pays a very small amount to Telcordia which runs the LNP database to tell whether the number's been ported and if so to which switch. R's, John
Current thread:
- Re: phone fun, was GeoIP database issues and the real world consequences, (continued)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences John R. Levine (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Larry Sheldon (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 14)
- Message not available
- Message not available
- Message not available
- Message not available
- Re: phone fun, was GeoIP database issues and the real world consequences Jonathan Smith (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Peter Beckman (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Matthew Kaufman (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Larry Sheldon (Apr 13)
- Re: GeoIP database issues and the real world consequences Carlos M. Martinez (Apr 13)
- Re: GeoIP database issues and the real world consequences Steve Atkins (Apr 11)
- Re: GeoIP database issues and the real world consequences John Levine (Apr 11)
- Re: GeoIP database issues and the real world consequences Laszlo Hanyecz (Apr 11)
- Re: GeoIP database issues and the real world consequences Sean Donelan (Apr 11)
- Re: GeoIP database issues and the real world consequences Leo Bicknell (Apr 12)
- Re: GeoIP database issues and the real world consequences Larry Sheldon (Apr 12)